axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17347] New: - Provider Lookup Fails within EAR
Date Mon, 24 Feb 2003 19:47:10 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17347>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17347

Provider Lookup Fails within EAR

           Summary: Provider Lookup Fails within EAR
           Product: Axis
           Version: 1.1RC1
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: jens@void.fm


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 see 
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).

Mime
View raw message