I actually reported this 2 months ago; see
http://jira.jboss.com/jira/browse/JBSEAM-1766
:/. Hopefully now that someone besides me is bothered by this they'll fix it soon...
The workaround I've been using in the meantime is to call
org.jboss.seam.security.Identity.setSecurityEnabled(false);
at the start of every conversation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091106#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...