If the session is not secured then what exception are you getting in the absence of the JAAS login? Show the stack traces that are occurring.
-- xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Meyer-Willner, Bernhard wrote:
Hi,
this is the setup (please don't comment on design issues, the design is screwed, I know;): The ejb-jar with the session bean in question is not secured, i.e. jboss.xml doesn't include a security-domain tag. The session bean calls a class (same VM), which in turn calls this session bean again. In order to be able to acquire the interface (call create()) we need to do a JAAS login. If we don't, we get an exception.
I don't understand why the JAAS login is necessary, as the ejb-jar with the session bean is not secured with a security-domain tag. Also this in-VM login seems to cause problems later on, resulting in LoginExceptions (javax.security...).
Please help anybody, cause I'm at a total loss.
Regards, Bernie
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
