SOAPelem.getAsDOM();
The DOM response is Element elemResp.
The attachments received from the server are DataHandler[] dhTab[].
-----Message d'origine-
De : Steve Pruitt [mailto:[EMAIL PROTECTED]
Envoyé : lundi 9 février 2004 17:00
À : [EMAIL PROTECTED]
Objet : JAX-RPC with attachments ques
.class);
I am not sure how to qualify my return type.
Also, after looking at other example code, do I need:
call.addParameter(..);
Not sure how to define this for Element.
-Steve Pruitt
When I generate a wsdl using Axis's http://localhost:8080/axis/services/Component?wsdl
query parm, I get a truncated wsdl. I am missing the abstract parts and operations.
If I use java2wsdl, the complete WSDL is generated. Has anyone seen this problem
before?
http://schemas.xmlsoap.o
I
think I understand. Are the both strings returned as attachments? If
so, I was hoping to return the xml as my soap body, if this is even
possible. I will look at the holders package.
Thanks,
Steve
Pruitt
-Original Message-From: Pathuru, Kiran
[mailto:[EMAIL PROTECTED
someone point me to a good example, I can't find one.
Thanks,
-Steve
Pruitt
This is
frustrating. My service sends an attachment along with some body
content. Can someone spot where I am going wrong?
Thanks much in
advance.
The code to create
the soap response is:
SOAPMessage reply = mf.createMessage(); //mf is
javax.xml.soap.MessageFactory
SOAPPart sp =
The axis documentation says it follows the xml-rpc specification for data typing
guidelines. The specifications states xsd:time and xsd:date map to java.util.Calendar.
When I try to send an soap argument like:
09:33:16
I receive:
Exception in thread "main" java.io.IOException: org.xml.sax.S
All,
I have a service with an argument declared as java.util.Date. When I use axis' wsdl
generating tool, the resulting wsdl declares the part as xsd:dateTime. Shouldn't this
be xsd:date? How do I get the right xsd type generated?
-Steve Pruitt
All,
There are several questions, some based on my confusion surrounding message-style
services. Sorry for overloading a single post.
The axis user's guide states there are four valid signatures for message style
services:
public Element [] method(Element [] bodies);
public SOAPBodyElement []
mcat-4.1.24\c
ommon\lib\soap.jar org.apache.axis.client.AdminClient deploy.wsdd
The last entry in my class path is the soap.jar. The class should be found in it.
-Steve Pruitt
No, it's not. Navigate to the exact directory path in your classpath
and you'll find you are
e soap.jar. The class should be found in it.
-Steve Pruitt
No, it's not. Navigate to the exact directory path in your classpath
and you'll find you are missing the WEB-INF dir.
-Original Message-
From: Steve Pruitt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003
axis.jar;C:\jakarta-tomcat-4.1.24\
webapps\axis\lib\commons-discovery.jar;C:\jakarta-tomcat-4.1.24\webapps\axis\lib\commons-l
ogging.jar;C:\jakarta-tomcat-4.1.24\webapps\axis\lib\log4j-1.2.8.jar;C:\jakarta-tomcat-4.1
.24\webapps\axis\lib\xml-apis.jar
The axis.jar is in the directory, so I am miffed
Can I use the java2WSDL tool with Apache SOAP?
-Steve Pruitt
iated.
-Steve Pruitt
In Tomcat console, I get the stack trace:
at org.apache.axis.Message.setup(Message.java:325)
at org.apache.axis.Message.(Message.java:234)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:810)
at javax.servlet.http.HttpServlet.service(HttpServlet
ectly. Or, something. Nothing showed in Tomcat
console, so I was just poking around for something and discovered the package
name mismatch.
-Steve
Pruitt
All,
I am having major axis admin
problems.
I undeployed my service using one of the sample undeploy
script / undeploy.ws
Services
The rest of the page is
blank.
Apparently, I have lost the Admin Service and Version
services as well. I tried deploying the
server-config.wsdd file I found in the axis/WEB-INF,
but to no avail. I have tried restarting Tomcat, but no
success.
I am stuck.
Thanks,
Steve Pruitt
.
If the soap body has something like how do I
resolve this in my actual web service method? I must be missing something obvious.
Thanks,
Steve Pruitt
17 matches
Mail list logo