We have planned to look at this issue because we also want to use a pure EJB3 implementation. But there are some other issues with the EJB3 specification that makes it almost useless for production applications:
- it does not have a simple solution for value converters, so converting for instance a DB char to a Java boolean cannot be done out of the box. - the EJBQL language does not even implement the complete SQL99 standard. One of the important things it misses is a join on sub queries. The solution to this issue might be to use an extended persistence context. Somewhere you must be able to set the PersistenceContextType to EXTENDED. In that case the Entity Beans are not detached when the transaction is closed. You should read chaper 3.3 and chapter 5.7 of the 'Enterprise JavaBeans 3.0, Final Release specification' for more information. I don't have any experience with it so I'm not sure if it has some drawbacks that makes it useless in a Wicket world. -- View this message in context: http://www.nabble.com/EJB3+Lazy+Loading+%28was+%22Seam-like+solution+for+Wicket+%2B+EJB3-%22%29-t1715549.html#a4659930 Sent from the Wicket - User forum at Nabble.com. ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
