-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
It is currently possible for user code to "see" some JBossWS integration classes & dependencies during the execution of static blocks of user handlers declared through webservices.xml descriptors or management model. That happens because such code is executed at deployment time when the JBossWS integration classloader is set as thread context classloader. We should prevent this from happening.
This is not a problem, of course, at runtime, when the deployment is completely isolated from the integration classloader.
- causes
-
JBEAP-15236 [GSS](7.1.z) TCCL not set for JBoss WS deployment
- Closed
- clones
-
JBWS-3986 Improve isolation between integration code and user code
- Closed
- is incorporated by
-
JBEAP-5271 (7.0.z) Upgrade JBossWS from 5.1.3.SP1 to 5.1.5.Final
- Verified