In fact, I did declare a security domain in login-config.xml:
<application-policy name = "soja">
| <authentication>
| <login-module code =
"org.jboss.security.auth.spi.UsersRolesLoginModule"
| flag = "required" />
| </authentication>
| </application-policy>
And I used @SecurityDomain("soja") for the base class of the session bean, but
I got the mentioned exception.
Anyways, thanks a lot for the information about jboss.xml. I've tried this
before but nothing happened. I'm glad to hear it will be working in next weeks
release.
regards, milan wölke
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918063#3918063
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918063
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
