Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 3.1, 4.0.0
-
Component/s: Classloader
-
Security Level: Public
-
- Environment:
- -
Activity
| Fix Version/s | 3.1.1 [ 10107 ] | |
| Fix Version/s | 3.2 [ 10108 ] |
| Summary | Components may use kernel classloader JARs in place of component class loader JARS | Classloader isolation uncomplete |
| Priority | Major [ 3 ] | Blocker [ 1 ] |
| Link |
This issue blocks |
| Link | This issue blocks SPFTELROSE-1 [ SPFTELROSE-1 ] |
| Link | This issue blocks SPFTELROSE-1 [ SPFTELROSE-1 ] |
| Link | This issue blocks SPFTELROSE-2 [ SPFTELROSE-2 ] |
| Fix Version/s | 3.0.6 [ 10147 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|

No, the classloader isolation is needed. It seem's that your problem is a problem about the classloader isolation. Have you looking for why the EasyWSDL version used is the one provided by the container instead of the one provided by the component ?