"[EMAIL PROTECTED]" wrote : Yell at Gavin King if you like the old way [EMAIL PROTECTED] and hate the new way. I miss the old way too. | | There were some problems with the old way specifically: | | 1) If you deployed multiple EJBs with the same interface. | 2) I fyou deployed a bean class with multiple remote/local interfaces | 3) If you deployed multiple versions of the same EJB in different scoped EARs | | Bill
I think the default naming strategy should reflect the common case. There is always @LocalBinding in case you want to do something different. Sensible defaults over configuration. In this case the defaults simply don't make sense for most applications. I scanned the EJB3 JSR for clues but it looks like the naming scheme will be container specific. This is really sad, since it will make it very hard for people trying to integrate EJB3 annotations in existing frameworks. (For example, I'm working on adding @EJB to Stripes and Wicket and now I have to figure out at runtime in which container the code is deployed in and then use different naming scheme for lookups. Very lame.) Can I open a JIRA issue for this? S. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944026#3944026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944026 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
