[ 
https://issues.apache.org/jira/browse/AXIS2-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joerg Spiegel updated AXIS2-4833:
---------------------------------

    Affects Version/s: 1.5.1
                           (was: 1.4.1)
          Environment: JDK 1.6.0_14, Oracle WebLogic Application Server 10.3, 
Solaris SunOS 5.10  (was: JDK 5 , WebSphere application server 6.1)
          Description: 
I've tried to loading the logging-module from the classpath which did not work 
on a BEA Weblogic 10.3 (causing a NullPointerException in RepositoryListener, 
Method loadClassPathModules().
The problem is similar to AXIS2-4258 (Fix for the WebSphere AppServer) because 
the BEA container uses a different protocol, too.

In my case the logging module (named axis2-log-module.jar) is included within 
EAR-File and the returned URL from the ClassLoader to this resource:
zip:/projects/projectname/weblogic10.3/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/_appsdir_AppName_ear/jpclyk/axis2-log-module.jar!/META-INF/module.xml

I'm not sure if this might be a problem of the BEA ClassLoader but the Scheme 
is null, which causes a NullPointerException when checking if scheme is not 
"file".
Code line: if (!moduleURI.getScheme().equals("file"))

Regards,
Joerg



  was:
I tried to deploy the axis2  ver 1.4.1 in websphere 6.1 with jdk 1.5 and wanted 
to load the modules from the classpath., which did not work. In websphere a jar 
URL will be starting with "wsjar" instead of  "jar" for eg.  the addressing 
module xml file came up like 
wsjar:file:/opt/IBM/WebSphere/xyz/xyz.ear/addressing-1.4.1.jar!/META-NNF/module.xml.

To overcome this issue in the class 
org.apache.axis2.deployment.RepositoryListener, method name 
"loadClassPathModules()", i changed its implementation to also look for "wsjar" 
instead of  just "jar"  and "file". Also since the "wsjar" is not actually an 
instance of  "java.net.JarURLConnection", we can't use directly this way of 
getting the URL of the jar
((java.net.JarURLConnection)url.openConnection()).getJarFileURL();

One more "else if" clause was added for "wsjar" and its file name was fetched 
directly by doing

else if (fileName.startsWith("wsjar")) {
    fileName =fileName.substring("wsjar:".length());
    fileName =fileName.substring(0, 
fileName.lastIndexOf("!/META-INF/module.xml"));
}

Thanks
Vijay



        Fix Version/s:     (was: 1.5)

> Modules not getting loaded from classpath in Oracle WebLogic 10.x
> -----------------------------------------------------------------
>
>                 Key: AXIS2-4833
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4833
>             Project: Axis2
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.5.1
>         Environment: JDK 1.6.0_14, Oracle WebLogic Application Server 10.3, 
> Solaris SunOS 5.10
>            Reporter: Joerg Spiegel
>            Assignee: Andreas Veithen
>
> I've tried to loading the logging-module from the classpath which did not 
> work on a BEA Weblogic 10.3 (causing a NullPointerException in 
> RepositoryListener, Method loadClassPathModules().
> The problem is similar to AXIS2-4258 (Fix for the WebSphere AppServer) 
> because the BEA container uses a different protocol, too.
> In my case the logging module (named axis2-log-module.jar) is included within 
> EAR-File and the returned URL from the ClassLoader to this resource:
> zip:/projects/projectname/weblogic10.3/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/_appsdir_AppName_ear/jpclyk/axis2-log-module.jar!/META-INF/module.xml
> I'm not sure if this might be a problem of the BEA ClassLoader but the Scheme 
> is null, which causes a NullPointerException when checking if scheme is not 
> "file".
> Code line: if (!moduleURI.getScheme().equals("file"))
> Regards,
> Joerg

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to