Shay Shmeltzer's Weblog

Hi
does oracle let the other users to download and see the stuff from your worlshop ?
for example PDFs , video podcasts.... ?

thanks

We usually publish the scripts for the hands-on labs part. The scripts for this run of the Oracle Developer Days will be published probably next month.
All the rest of the material can be found on the various pages of OTN.
Try: http://otn.oracle.com/jsf or /ejb3 or /bpel

Great presentation in Montreal, I thoroughly enjoyed it though it was very concentrated which is why I choose to state my questions here, for others to see as well:

- Is the JavaOneRickClientApp available as a demo or preview anywhere, and is this what your internally refer to as Faces .next?

- How is master-detail relationships done in EJB3, since it can not rely on ViewLinks as in the ADF BC framework?

- The JPA query mechanism through annotations is inherently as type unsafe as embedding raw SQL in Java JDBC code. Why not try to provide type safety and IDE-intellect the same way it is done in Microsofts Linq technology?

- You could make it a bit more obvious in the JSF part of the workshop, that there is no relationship to the first exercises (JPA and annotations). People who worked with ADF BC before would recognize this fact, but I think many Forms/4GL people were left with the impression that they witnessed a full stack in action. Why hang on the the complex databinding of ADF (JSR-227) when there are simpler approaches (hooking a backing-bean to a session-bean) as proven and implemented by JBoss Seam?

Thanks again for a fun day,
Casper

Casper,
Glad you enjoyed the day.
To answer your questions:
1. Since the Javaone demo was written the components have evolved, but they are still not in a state where we can release them to the public - we are working on this.

2. Master detail relationship in JPA is done through annotations that you use for collections.
To see it in action just create two EJBs on dept/emp in JDeveloper and you'll see how the relationship is defined in the code.

3. That's a good idea for a JDeveloper enhancment in the future.

4. As to the question of why use JSR-227 and not something like seam - Seam is just for the specific case of EJB3 and JSF while JSR-227 and the ADF implementation gives you much more freedom in choosing both the view and the business service layer.
In addition - JSR-227/ADF keeps all the binding information outside of your code in XML files - so modifications and customizations don't require a recompile of your code.
ADF also offers you more then just binding in the Model layer - you can add declarative validation, security and even UI information to your data-controls (EJB as well as ADF BC) and again this is kept in the meta-data layer.
And of course there is the development exeprience which is visual with ADF and code centric with Seam.

Hi, I have question. If EJB provides all the mechanism and feature to create webservices, how do decide when to use BPEL to build process and webservices vs EJB?

You can very easily create web service interfaces for your EJB 3.0 session bean methods (JDeveloper has a wizard for it and also annotation support for creating these).
Then you can invoke this business logic from a BPEL process.
In general BPEL is for the process and EJB is for the business logic.