[
https://jira.jboss.org/jira/browse/JBESB-2376?page=com.atlassian.jira.plu...
]
Kevin Conner reopened JBESB-2376:
---------------------------------
The codebase uses the classloader of the gateway class itself, which is not the one which
represents the deployment.
There are a number of issues with this
- scoped resources will be associated with the wrong classloader (that of the gateway
class)
- the gateway may not have access to all/correct classes.
One example should be a composer class contained within a scoped deployment.
Check classloader configuration in the http gateway
---------------------------------------------------
Key: JBESB-2376
URL:
https://jira.jboss.org/jira/browse/JBESB-2376
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.5
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.4 FP1, 4.6
Looks like it is deliberately ignoring the context class loader, need to make sure this
is correct.
My gut feeling is that it is wrong as it would appear to allow configuration of a
composer class but, obviously, would not necessarily have access to it.
Too late for 4.5.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira