What I did as a solution is to create a separate jar for the SEAM action EJB's which
are accessed only via local interfaces. There is no security constraints specified for
this jar file and therefore, won't trigger the exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110020#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...