Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <1662869262.1103060218229.JavaMail.apache@nagoya>
Date: Tue, 14 Dec 2004 13:36:58 -0800 (PST)
From: "Davanum Srinivas (JIRA)" <axis-dev@ws.apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS-1722) MethodCache does not consider the
 classloader in the cache key
In-Reply-To: <980991135.1103053618018.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://nagoya.apache.org/jira/browse/AXIS-1722?page=history ]
     
Davanum Srinivas resolved AXIS-1722:
------------------------------------

    Resolution: Fixed

Applied.

thanks,
dims


> MethodCache does not consider the classloader in the cache key
> --------------------------------------------------------------
>
>          Key: AXIS-1722
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1722
>      Project: Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.2RC2
>  Environment: Any
>     Reporter: Eric Norman
>  Attachments: MethodCache.java
>
> If you load a class with the same name in different classloaders, the method cache only uses the first one.  This is a problem because our server loads components into their own classloaders, so if two components contain the same classname, the MethodCache will often return a Method from the wrong class, eventually causing a problem serializing and/or deserializing the SOAP message into their java objects.  Suggest using the class object as the key in the HashMap instead of the classname.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira