Hi,
I found the problem, a referenced class was missing.
Fortunately a InvocationTargetException contains a lot of useful
information...
Sorry for bothering you.
Best regards,
Patrick Schmidt
Patrick Schmidt schrieb:
Hello Martin,
thank you for the quick answer.
Actually I already took a look at the server-config.wsdd
The entry for my service is
<service name="ArchiSoft" provider="java:MSG" style="document"
use="literal">
<requestFlow>
<handler type="soapmonitor"/>
</requestFlow>
<responseFlow>
<handler type="soapmonitor"/>
</responseFlow>
<parameter name="allowedMethods"
value="processTASPRequest"/>
<parameter name="scope" value="application"/>
<parameter name="className"
value="fraunhofer.sit.archisoft.server.webservice.ServiceEndpoint"/>
</service>
If I put the class "ServiceEndpoint" under
%TOMCAT_HOME%/webapps/axis/WEB-INF/classes/fraunhofer/sit/archisoft/server/webservice
everything works fine.
However if I put the class in a lib with the directory structure
fraunhofer/sit/archisoft/server/webservice
and put that lib under
%TOMCAT_HOME%/webapps/axis/WEB-INF/lib
I get the InvocationTargetException.
Best regards,
Patrick Schmidt
Martin Gainty schrieb:
-------------------- Start SpamAssassin results ----------------------
This mail is probably spam. The original message has been attached
to this so you can view it (if it isn't spam) or block
similar unwanted mail in future.
lokale Anpassung aus /usr/local/spamassassin/etc/mail/spamassassin/local.cf
Content analysis details: (5.1 hits, 5.0 required)
1.1 MIME_BASE64_LATIN RAW: Latin alphabet text using base64 encoding
1.1 MIME_BASE64_TEXT RAW: Message text disguised using base64 encoding
0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
[65.54.246.168 listed in dnsbl.sorbs.net]
0.8 MSGID_FROM_MTA_HEADER Message-Id was added by a relay
2.0 AWL AWL: Auto-whitelist adjustment
-------------------- End of SpamAssassin results ---------------------
Good Morning Patrick-
Take a look at /axis/server-config.wsdd notice the entry for your service
Here is an example
<service name="AdminService" provider="java:MSG">
<parameter name="allowedMethods" value="AdminService"/>
<parameter name="enableRemoteAdmin" value="false"/>
<parameter name="className" value="org.apache.axis.utils.Admin"/>
<namespace>http://xml.apache.org/axis/wsdd/</namespace>
<namespace>http://xml.apache.org/axis/wsdd/</namespace>
</service>
In this situation Admin.class must be in %TOMCAT_HOME%/webapps/axis/WEB-INF/classes/org/apache/axis/utils/Admin
OR if wrapped in a jar could be located here
%TOMCAT_HOME%/webapps/axis/WEB-INF/lib
HTH,
Martin --
*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message -----
From: "Patrick Schmidt" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, July 17, 2006 7:46 AM
Subject: Re: InvocationTargetException when putting the web service classes in a jar file under lib
A little appendix:
I am using Axis 1.4
Patrick Schmidt schrieb:
Hi there,
I have following problem with axis. I already searched the mailing
list, but found nothing so far. Therefore any help would be greatly
appreciated.
When I am putting the classes of my web service in a jar file under
the webapps/axis/lib directory on my tomcat, I get an
InvocationTargetException, when trying to invoke the web service.
However, if I am extracting the web service class (only the class
specified in the param className in the server-config.wsdd, the other
associated classes are still only in the jar) in the
webapps/axis/classes folder everything works fine.
I am sure that the directory structure in the jar equals the directory
structure under /axis/classes.
Thanks for any answer.
Best regards,
Patrick Schmidt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
|
