"jaikiran" wrote : Right, but the current behaviour just silently ignores the
2nd EJB and does not bind it.
There's no exception thrown when binding to an already bound address?
"jaikiran" wrote : So if we have the information that we have already bound
bean1 to the same name then maybe we could log a WARN message to highlight this issue so
that the user opts for the workaround.
Better to fail the whole deployment w/ a descriptive exception.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183995#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...