[wsas-java-dev] [jira] Resolved: (WSAS-433) Classloader issues.

[Afkham Azeez (JIRA)]

     [ http://wso2.org/jira/browse/WSAS-433?page=all ]

Afkham Azeez resolved WSAS-433.
-------------------------------

    Resolution: Fixed

> Classloader issues.
> -------------------
>
>                 Key: WSAS-433
>                 URL: http://wso2.org/jira/browse/WSAS-433
>             Project: WSO2 WSAS
>          Issue Type: Bug
>         Environment: Standalone WSAS version 2.0 Release version. Windows XP or Linux, JDK 1.5.
>            Reporter: Jeff Uchitjil
>         Assigned To: Afkham Azeez
>
> I have a web service that has been deployed in axis 1.2 in tomcat and running fine. It uses hibernate 3.2.4sp1 to connect to a postgres database. I tried to deploy the existing aar file to WSAS standalone version 2.0 full release. I appears that a classloader issue exists. Upon accessing the service an error is thrown that the hibernate.cfg.xml cannot be found. It is located in the root of the aar with the hibernate jars in the lib directory in the aar. I tried adding a ServiceTCCL parameter of composite and then it finds the hibernate.cfg.xml and then errors with JDBC exception no suitable driver indicating that it cannot find the JDBC driver which is in the lib directory in the aar. It appears that the WSAS setup is interfering with the axis classloader as this service works fine in a normal axis2 deployment running in tomcat.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira