Bugs item #1038708, was opened at 2004-10-01 20:44
Message generated for change (Settings changed) made by tdiesler
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1038708&group_id=22866
Category: None
Group: v4.0
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: sevk (yaaarrrgg)
Assigned to: Thomas Diesler (tdiesler)
Summary: Error: No engine configuration file - aborting!
Initial Comment:
-----------------------
JBOSS/AXIS BUG???
-----------------------
Problem: Web service client will not run at all.
Error message: org.apache.axis.ConfigurationException:
org.apache.axis.ConfigurationException: No engine
configuration file - aborting! ...
I'm Running: JBoss 4.0.0, running on Win XP Pro SP2.
JDK 1.4.2. I'm also using the generated classes from
WSDL2Java.
Diagnosis: JBoss is apparently not finding the config file
axis-client-config.xml, and crashes.
C:\jboss-4.0.0\server\standard\deploy\jboss-
ws4ee.sar\META-INF\axis-client-config.xml ???
Possible naming problem. Seems to want a .wsdd
-----------------------
A QUICK AND DIRTY FIX
-----------------------
1. get the config file. I just used the config file from
the WSDL2Java plugin from myspotter.com.
If you have the eclipse plugin, axis.jar is at:
<eclipsehome>\plugins\com.myspotter.wsdl2java_1.1.0
\axis.jar
...or you can also download Axis1.1 and look
in /lib/axis.jar
a. Find and rename axis.jar to axis.zip
b. navigate to org/apache/axis/client/
c. you should find a file called client-config.wsdd.
copy this to desktop
d. rename axis.zip back to axis.jar
2. JBoss apparently calls this by two names...
a. copy file client-config.wsdd
b. rename copy to axis-client-config.wsdd
3. the file to update is at:
<jbosshome>\server\standard\deploy\jboss-
ws4ee.sar\axis-ws4ee.jar
a. rename axis-ws4ee.jar to axis-ws4ee.zip
b. navigate to org/apache/axis/client/
c. copy BOTH files here (axis-client-config.wsdd,
client-config.wsdd)
d. rename axis-ws4ee.zip back to axis-ws4ee.jar
4. restarting server should fix the problem.
(I use the standard server: <jbosshome>/bin/run.bat -c
standard)
Note: there is a similar file at <jbosshome>\client\axis-
ws4ee.jar, but this seems to work as is.
-ks
----------------------------------------------------------------------
Comment By: Thomas Diesler (tdiesler)
Date: 2004-10-13 05:57
Message:
Logged In: YES
user_id=423364
With JBossWS you cannot use wsdl2java. It generates non
portable client stubs. Use jwsdp-1.4 wscompile to generate
POJOs as paramteter and return types.
Don't mix axis.jar & axis-ws4ee.jar.
Please attach a test that isolates the issue.
----------------------------------------------------------------------
Comment By: sevk (yaaarrrgg)
Date: 2004-10-07 21:05
Message:
Logged In: YES
user_id=1131661
Yes, this is just a hack, not a solution. I've actually tried
adding the file to the classpath, but that does not work. I
just can't get the JBoss xml config file to work with the
generated wsdl2java code.
Of course, the downside to this hack is J2EE compliance, and
it might cause other problems down the road (although I have
not had any *yet*). The plus side: the web services work.
It is possible the problem is in wsdl2java plugin or Axis. The
generated code might rely on the real axis.jar, not the JBoss
version. I'm still investigating this. Although, it is suspicious
that this works better in older versions of JBoss than newer:
---------------
Testing different platforms, I've found that:
JBoss 3.2.5 - Worked on first launch, but NullPointerException
if redeployed (which could be a classloader issue.)
JBoss 4.0.0 DR3 - Worked without any problems
JBoss 4.0.0 RC1 - Error: No engine configuration file -
aborting!
JBoss 4.0.0 - Error: No engine configuration file - aborting!
---------------
If you like, I can upload a zip file of a project that fails.
----------------------------------------------------------------------
Comment By: Thomas Diesler (tdiesler)
Date: 2004-10-04 20:29
Message:
Logged In: YES
user_id=423364
The axis-client-config.xml lives in $JBOSS_HOME/client/jboss-
ws4ee-client.xml which must be on your classpath.
Your fix is nonsense cause it replaces the jboss axis
implementation with axis-1.1, which is by not J2EE compatible.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1038708&group_id=22866
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
