axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Resolved] (AXIS-693) Provider Lookup Fails within EAR
Date Sun, 07 Oct 2012 21:02:02 GMT


Andreas Veithen resolved AXIS-693.

    Resolution: Incomplete
> Provider Lookup Fails within EAR
> --------------------------------
>                 Key: AXIS-693
>                 URL:
>             Project: Axis
>          Issue Type: Bug
>          Components: Deployment / Registries
>    Affects Versions: 1.1RC1
>         Environment: Operating System: MacOS X
> Platform: Macintosh
>            Reporter: Jens Schumann
> Deploying the axis web archive as part of an zipped EAR will prevent proper custom 
> WSDD provider lookup. No custom providers will be found (or better 
> org.apache.axis.deployment.wsdd.Provider lookup fails). I did not take a look at 
> common-discovery classes, but I believe the current Classloader lookup does not work

> on several application servers (such as Bea WLS in my case). Everything works as 
> expected using the exploded war.
> Since cross app server resource loading is quite difficult to achive I would love to
> some fall back mechanism:
> One org.apache.axis.deployment.wsdd.Provider location could be WAR-ARCHIVE/
> META-INF/services/org.apache.axis.deployment.wsdd. The file should be loaded via 
> servletContext.getResourceAsStream(). This works on all plattforms I have tested so far

> (tomcat,jboss,bea,orionserver/oracle,pramatiserver,jrun,resin).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message