+1.
Current implementation is dependent on packaging, which, while ensuring namespace-based
unique values, immediately breaks all applications once JAR names change, are placed into
an EAR, etc.
Bean providers must currently override default names using their own homebaked solution;
I'd heavily made use of LocalBinding/RemoteBinding on every EJB just for this purpose.
Pluggable policy would address this in one fell swoop.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101486#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...