Hi,
I am running an Microsoft soap listener (ASP)on IIS and calling
the service from Java client.
I am getting the following error when calling the soap service.
I verified the parameters...they are all fine.
Caught SOAPException (SOAP-ENV:Client): Parsing error, response wa
With the following code (I'm a using JAXM-Simple example), how might I fail
this nicely if the message doesn't go through within say 15 seconds. I mean,
I can figure out how to throw the exception after 15 seconds, but assuming I
do this is the message still queued (and would it be delivered if a
Hi Gus,
Try adding WEB-INF/ to weblogic's classpath
"Gus Delgado"
I've deployed a web service in weblogic6.1 using soap2.2, I'm trying to make
my underlying object to read as an input stream an .rc file this is how I'm
doing it.
InputStream is = getClass().getResourceAsStream("soap.rc");
The object lives in a jar file which is part of a war that looks like thi
Hi,
Have you looked at Sun's JAXM specification? Basically, it's a
standardised SOAP API for Java.
We're currently developing an implementation of the JAXM Version 1.0
specification which should be available soon. We allow SOAP messages to
be transported over HTTP or JMS.
JAXM uses MessageFa
Try it this way:
---
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
Documentdoc = db.newDocument();
Element methodCall = doc.createElement("ns1:methodToCall");
methodCall.setAttribute("xmlns:ns1", "u
Are you on about
forming the xml body part or the SOAP header?
-Original Message-From: Shashi Anand
[mailto:[EMAIL PROTECTED]]Sent: 08 March 2002
10:14To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]Subject: soap messaging XML
???
Hi,
One strange thing
Hi,
One strange thing I
noticed is that all the tutorials explaining the SOAP messaging assume whole
SOAP message to be readilly available in XML file, where as this is not the
case. None of tutorials explain how to form this SOAP message given the XML
which is only part of message body.
D
I have had these problems with SOAP2.2...I think that it is to do with the
way the message is parsed in memory...To get round the problem we moved to
using Axis which has all of the functionality that we are using in the Alpha
version.
-Original Message-
From: Juan Gargiulo [mailto:[EMAIL
