You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org> on 2005/01/21 20:44:21 UTC
[jira] Reopened: (AXIS-1776) Client configuration '.wsdd' files not found when packaged in an ejb-jar file.
[ http://issues.apache.org/jira/browse/AXIS-1776?page=history ]
Davanum Srinivas reopened AXIS-1776:
------------------------------------
Andrei,
had to back out the entry for *EJB in EngineConfigurationFactoryFinder...please run "ant clean all-tests" and submit "cvs diff -u" against latest axis.
> Client configuration '.wsdd' files not found when packaged in an ejb-jar file.
> ------------------------------------------------------------------------------
>
> Key: AXIS-1776
> URL: http://issues.apache.org/jira/browse/AXIS-1776
> Project: Axis
> Type: Bug
> Components: Deployment / Registries
> Versions: current (nightly)
> Environment: An EJB 2.0 compliant EJB container.
> Reporter: Andrei Iltchenko
> Attachments: 1776.jar
>
> When run from within an EJB container, Axis cannot find a client configuration '.wsdd' file when the latter is packaged as part of an ejb-jar file and the Application server uses distinct class loaders per ejb-jar of a J2EE application. As a result the default client configuration file from 'org/apache/axis/client/client-config.wsdd' gets picked up, which doesn't necessarily contain the configuration needed.
> The problem is essentially caused by us not having an 'EngineConfigurationFactory' that is capable of finding resources through the context class loader. The patch that I am going to supply addresses the problem and has been tested on WebLogic 8.x and Jboss 3.x.x.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira