[ http://jira.jboss.com/jira/browse/JBWS-1328?page=all ] Thomas Diesler updated JBWS-1328: --------------------------------- Fix Version/s: jbossws-2.0.0.CR1 (was: jbossws-1.0.3) Affects Version/s: (was: jbossws-1.0.2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1328?page=all ] Jason T. Greene updated JBWS-1328: ---------------------------------- Fix Version/s: jbossws-2.0.0.CR3 (was: jbossws-2.0.0.CR2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBWS-1328?page=all ] Darran Lofthouse updated JBWS-1328: ----------------------------------- Summary: Security configuration not correctly loaded when deployed as ear to JBoss 5.0.x (was: Client security configuration not loaded when client deployed with issolated classloader.) Environment: When deployed to JBoss 5.0.x Description: The security configuration not correctly loaded when deployed as ear to JBoss 5.0.x, this is causing the test case for JBWS-1121 to fail as it is packaged as an ear to test scoped classloading. (was: When a client is deployed using an issolated classloader the security configuration of the client is not loaded as the wrong classloader is used to load the resource. This results in a warning being logged and the client sending messages that are not signed / encrypted.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira