Deploying Webservice

[Nitesh Garg]

I am using WAS 4.0, and IBM's HTTP server. I have created a small web
service using the tutorial with wstk3.2 But i ma facing problem with
the .wsdd file whicle deploying the service.

AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: org.xml.sax.SAXParseException: Premature end of file.
faultActor: null
faultDetail:
stackTrace: org.xml.sax.SAXParseException: Premature end of
file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.j
ava:1172)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at org.apache.axis.encoding.DeserializationContextImpl.parse(Deserializa
tionContextImpl.java:213)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:457)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:362)
at org.apache.axis.client.Call.invokeEngine(Call.java:2047)
at org.apache.axis.client.Call.invoke(Call.java:2017)
at org.apache.axis.client.Call.invoke(Call.java:1233)
at org.apache.axis.client.AdminClient.process(AdminClient.java:316)
at org.apache.axis.client.AdminClient.process(AdminClient.java:295)
at org.apache.axis.client.AdminClient.process(AdminClient.java:302)
at org.apache.axis.client.AdminClient.process(AdminClient.java:253)
at org.apache.axis.client.AdminClient.main(AdminClient.java:338)

org.xml.sax.SAXParseException: Premature end of file.
at org.apache.axis.AxisFault.makeFault(AxisFault.java:117)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:462)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:362)
at org.apache.axis.client.Call.invokeEngine(Call.java:2047)
at org.apache.axis.client.Call.invoke(Call.java:2017)
at org.apache.axis.client.Call.invoke(Call.java:1233)
at org.apache.axis.client.AdminClient.process(AdminClient.java:316)
at org.apache.axis.client.AdminClient.process(AdminClient.java:295)
at org.apache.axis.client.AdminClient.process(AdminClient.java:302)
at org.apache.axis.client.AdminClient.process(AdminClient.java:253)
at org.apache.axis.client.AdminClient.main(AdminClient.java:338)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.j
ava:1172)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at org.apache.axis.encoding.DeserializationContextImpl.parse(Deserializa
tionContextImpl.java:213)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:457)
... 9 more

my file is

<deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">

<service name="data" provider="java:RPC">
<parameter value="TestService" name="className"/>
<parameter value="getData" name="allowedMethods"/>
</service>

<beanMapping
xmlns:nq="http://ipaddress/TestService-types"
languageSpecificType="java:TestServ"
qname="nq:TestServ"/>

</deployment>

Can u suggest whats the possible problem with this.

Thanx Nitesh

[Matthias Böhringer]

Hallo,
you must read the installation up to step 5. The wsdd file ,ust be
deployed with the URL of the service
z. B.
-lhttp://localhost:8080/axis/services/AdminService deploy.wsdd

siehe auch
The various classes and jars you have just set up contain a number of
interfaces. What remains to be done is to tell the soap and axis
servlets how these are to be combined and what is to be exposed.
There are a number of ways to do this, for now I'll simply describe
one way that is suitable for automation.

Add axis.jar, commons-discovery.jar, commons-logging.jar, jaxrpc.jar,
saaj.jar, log4j-1.2.4.jar (or whatever is appropriate for your chosen
logging implementation), and the XML parser jar file or files (e.g.,
xerces.jar) to your classpath. Locate the deployment descriptor for
your service and execute the following command:
java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/axis/services/AdminService deploy.wsdd
Note: You may need to replace localhost with your host name, and 8080
with the port number used by your web server.

oder
Die verschiedenen einzurichtenden Klassen und jars enthalten ein Reihe
von Interfaces. Was jetzt noch zu tun bleibt, ist, SOAP und den Axis
Servlets zu sagen, wie Sie zusammengesetzt sind und wie Sie
veröffentlicht werden sollen. Hier gibt es verschiedene Möglichkeiten;
wir beschreiben jetzt eine der einfacheren, die auch automatisiert
werden kann.

Erweitern Sie Ihren CLASSPATH um die Pfade zu axis.jar,
commons-logging.jar, log4j-core.jar, tt-bytecode.jar und die
XML-Parser jars (beispielsweise xerces.jar). Lokalisieren Sie den
Deployment Descriptor Ihres Service und führen Sie den folgenden
Befehl in der Komandozeile aus:

java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/axis/services/AdminService deploy.wsdd

Achtung: Hier muss natürlich der Name Ihres Servers und die von diesem
verwendete Portnummer eingesetzt werden.

Greetings,
Matthias Böhringer

info2...@yahoo.com (Nitesh Garg) wrote in message news:<90564358.02110...@posting.google.com>...