You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2005/09/23 18:35:28 UTC

[jira] Commented: (AXIS2-239) Cannot load service specific classes by external modules

    [ http://issues.apache.org/jira/browse/AXIS2-239?page=comments#action_12330294 ] 

Deepal Jayasinghe commented on AXIS2-239:
-----------------------------------------

As I know in first F2F we had in Colombo we decided to introduce the concept of service isolation. That is why we are creating a classloader for each services in the system , by giving CL as its parent , I am -1 on if we are going to change axis2 architecture in order to support WS-Security.

Why can not you use service.getClassloader as your class loader ? , if WSS4J does not have a method to take custom class loader we have to fix that not axis2, as far as security module is concern it is just an extension module.


> Cannot load service specific classes by external modules
> --------------------------------------------------------
>
>          Key: AXIS2-239
>          URL: http://issues.apache.org/jira/browse/AXIS2-239
>      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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira