Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <1030870873.1106347037916.JavaMail.jira@ajax.apache.org>
Date: Fri, 21 Jan 2005 23:37:17 +0100 (CET)
From: "Andrei Iltchenko (JIRA)" <axis-dev@ws.apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Updated: (AXIS-1776) Client configuration '.wsdd' files not
 found when packaged in an ejb-jar file.
In-Reply-To: <1531892570.1106322317049.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/AXIS-1776?page=history ]

Andrei Iltchenko updated AXIS-1776:
-----------------------------------

    Attachment: 1776.txt

Did as requested, here come the differences for 'EngineConfigurationFactoryFinder.java' obtained against the latest cvs.

> 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, 1776.txt
>
> 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