Ok, I found where I got this idea from. http://www.javaworld.com/javaworld/jw-08-2004/jw-0809-ejb.html
On the first page it says: "In the EJB 3.0 world, all kinds of enterprise beans are just plain old Java objects (POJO) with appropriate annotations... you don't necessarily have to implement a business interface (the container can generate it for you)." And on the second page: "If it does not implement any business interfaces, a business interface will be generated using all the public methods. If only certain methods should be exposed in the business interface, all of those methods can be marked with the @BusinessMethod annotation." Of course I'm just noticing that this article is almost a year and a half old, so things may have changed quite a bit since then. If it has changed, does anyone know where in the spec drafts it changed? I'd be interested in the rationale behind this. I think it would be really great to eliminate the redundant (from a conceptual point of view) interface for each bean. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917151#3917151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917151 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
