Forget about the abstract getters/setters for now, that is a horrible implementation of laziness anyway.
A good implementation would be to have proxies for the components which actually create the underlying component instance when first invoked. Seam could do that. But it seems to me that the EJB container could do it just as easily, since it already has a proxy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947405#3947405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947405 ------------------------------------------------------- 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 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
