axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-4833) Modules not getting loaded from classpath in Oracle WebLogic 10.x
Date Sat, 27 Nov 2010 13:43:14 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964360#action_12964360
] 

Andreas Veithen commented on AXIS2-4833:
----------------------------------------

Joerg,

Since you correctly identified the root cause of the issue, do you think that you could do
the required modifications to make it work on Weblogic and submit a patch?

> 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
>         Attachments: bug_4833_pic1.jpg, bug_4833_pic2.jpg
>
>
> 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 is:
> 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 (weblogic.utils.classloader.ChangeAwareClassloader)
but the returned Scheme is null, which causes a NullPointerException when checking the scheme
is not "file".
> Code line 137: 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message