-
Bug
-
Resolution: Done
-
Major
-
jbossws-1.0.2
-
None
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.
- is related to
-
JBWS-1328 Security configuration not correctly loaded when deployed as ear to JBoss 5.0.x
- Closed