The security context is a property if the thread and call context. Its not possible to pass it around and use it in another arbitrary context. Within the scope of the thread calling the ejb its use should be fine. The log indicates that interaction with a datasource using a different security policy is affecting the ejb context. I would need to see an example of what is being done to say if this is a bug in the handling of the security context.
Create a bug report in jira with a sample of what is producing this behavior so I can look into it. http://jira.jboss.com/jira/browse/JBAS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864248#3864248 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864248 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
