Davanum,
Right, and that's precisely how I implemented it in the last attachment.
1. I first see if I can get the resource from the file system, if available,
we are done;
2. If the resource is found through the thread context classloader, we are
finished too;
3. If a client configuration resource is not found through the thread
context classloader, I delegate to
'EngineConfigurationFactoryDefault.getClientEngineConfig()', which
instantiates a 'FileProvider' object with the name of the desired
configuration file (most likely 'client-config.wsdd' if we got as far as
this). When subsequently the 'FileProvider.configureEngine' method is
called, it will eventually end up trying to find the resource with our
'ClassUtils.getResourceAsStream' utility method
} catch (Exception e) {
if (searchClasspath)
setInputStream(ClassUtils.getResourceAsStream(engine.getClass(), filename));
}
Which will first search for the configuration file through the defining
class loader of the 'AxisEngine' class, thus giving us what we want --
default wsdd in axis jar..
Regards,
Andrei.
-----Original Message-----
From: Davanum Srinivas (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 25, 2005 16:24
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (AXIS-1776) Client configuration '.wsdd' files
not found when packaged in an ejb-jar file.
[
http://issues.apache.org/jira/browse/AXIS-1776?page=comments#action_58042 ]
Davanum Srinivas commented on AXIS-1776:
----------------------------------------
hmmm...we need to look deeper to fix this right...order of looking u need is
- file
- thread context classloader
- default wsdd in axis jar.
right?
thanks,
dims
> 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, 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
--
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
