axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Commented: (AXIS2-239) Cannot load service specific classes by external modules
Date Sun, 25 Sep 2005 15:54:48 GMT
    [ ] 

Davanum Srinivas commented on AXIS2-239:

We can add a hook in wss4j to set the classloader to be used for loading the classes....would
that work?

> Cannot load service specific classes by external modules
> --------------------------------------------------------
>          Key: AXIS2-239
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: deployment
>     Reporter: Ruchith Udayanga Fernando

> Right now we cannot load classes available in the service archive (.aar file) by modules
that are configured to be engaged for that service.
> We experience this when we try to use the security module where the security module (WSS4J)
will have to load the password callback class to get the password information from the developers.
Intuitively this password callback class should be packaged with the service archive. 
> Currently Axis2 uses a specific class loader to load the classes that belong to a service
form it archive. And the service archives are not in the scope the context class loader. But
IMHO since WSS4J uses the context class loader to pickup the password callback class it will
not pickup the class that is available in the service archive.
> Should we change Axis2 to support the above behaviour where the external module can load
classes available in the service archive?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message