Actually, I believe I've fixed it, and found what I believe to be the error in the
EJB3 package....
org.jboss.ejb3.Ejb3AnnotationHandler.getContainers goes through all ejbNames and calls
container.setDefaultClientBinding(deployment.getDefaultClientBinding());
...where appropriate, setting the default client binding of the SessionContainer's
ProxyDeployer to the proper address I've overridden via the Service Binding Manager.
This line is missing from the method if (ejbType == EJB_TYPE.SERVICE).
I added locally, rebuilt - now my client can properly access my Service Bean as it obtains
an InvokerLocator with proper binding address.
Can you please confirm and provide instructions for my submitting code or a patch?
Thanks!
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968474#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...