Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <119301282.1127491768034.JavaMail.jira@ajax.apache.org>
Date: Fri, 23 Sep 2005 18:09:28 +0200 (CEST)
From: "Ruchith Udayanga Fernando (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Created: (AXIS2-239) Cannot load service specific classes by
 external modules
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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