Thanks for stepping in, Andy.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4204125#4204125
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4204125
___
jboss-user mailing list
https://jira.jboss.org/jira/browse/JBAS-6392
patches and a convenient binary patch jar included
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4202695#4202695
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4202695
Further explanation: http://www.osintegrators.com/node/24
Suggestion to the industrious: https://jira.jboss.org/jira/browse/JBAS-6393
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4202718#4202718
Reply to the post :
Actually this has nothing to do really with remoting or EJB3. It is that JBoss
does not by default support setting the jndi username and password except if
you use the special
./security/src/main/org/jboss/security/jndi/LoginInitialContextFactory.java
which doesn't do you any good if you want
Hi Robert,
Although the log message comes from Remoting's ServletServerInvoker, the
problem arises after Remoting passes the call off to the EJB3 code, so I'm
going to suggest posing the question on the EJB 3.0 forum:
http://www.jboss.com/index.html?module=bbop=viewforumf=221. If you come
