View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263427#4263427
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4263427
___
jboss-user mailing list
jboss-user@lists.jboss.org
lvonk2000 wrote : We are experiencing the same thing. Have you found an
answer?
No, my work around is to propagate a second level call to a local unsecured
EJB.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263434#4263434
Reply to the post :
Created issue https://jira.jboss.org/jira/browse/EJBTHREE-1945
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263436#4263436
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4263436
Seeing same behaviour in an implementation. Looks like a bug in JBoss5, bacause
I cannot see the idea behind this behaviour. Can anyone do a bug report?
Regards,
Michael
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4260013#4260013
Reply to the post :
We are experiencing the same thing. Have you found an answer?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4258422#4258422
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4258422
