Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.3.2, 2.4
-
Fix Version/s: 2.4
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
The petals-se-xslt was able to load the XSL using a custom classloader. This feature has been removed.
Please, restore it. |
The petals-se-xslt 2.0 was able to load the XSL using a custom classloader. This feature has been removed.
Please, restore it. |
| Priority | Blocker [ 1 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Blocker [ 1 ] | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Closed [ 10005 ] |
| Fix Version/s | 2.4 [ 10087 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|

I've checked the tag for the version 2.0 of the component.
I don't see anything new with respect to the trunk version.
Currently, if the SU embeds JAR files which contain class files, the XSL style sheet and the JAR files are loaded in a custom class loader.
Would you have a SU for which this mechanism does not work?