I do not have a similar problem. What XML parser are you using (name and version)?
Scott Nichol
Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
- Original Message -
From: "OR623" <[EMAIL PROTECTED]>
To: <[EMAIL PRO
Technically, the "literal" encoding of Apache SOAP is *not* the same as the literal
encoding as specified by, say, WSDL 1.1. The Apache SOAP payloads will specify an
encodingStyle of http://xml.apache.org/xml-soap/literalxml. To my knowledge, Apache
SOAP is the only SOAP implementation that un
snip
This works just fine. Thanks again but, my (SOAP) clients are sending me (the SOAP
server) an xml file wrapped in an SOAP envelope as follows. How do I know what service
they are requesting? And, what params they have sent?
http://schemas.xmlsoap.org/soap/envelope/";>
htt
Well, I must say THANK YOU! for getting me going on this...
I do have another question though.
> I have to ask: why do you need to work directly with sockets?
> Do you have some requirement that you cannot use a SOAP library?
I guess, I could use the library. I was given some sample programs th
I have developed a
service which contains a number of methods which return a
org.w3c.dom.Element. I Use WSAD to develop the services and it defaulted
to RPC/Literal encoding. This works great for me, however I developed it
to communicate with a .NET application which cannot use it because
I have to ask: why do you need to work directly with sockets? Do you have some
requirement that you cannot use a SOAP library?
To answer your questions, the targetObjectURI is the namespace for the service, which
effectively means it is the namespace of the method element. That gets to your se
Hello,
I have a question and I hope I'll be able to get some help from the list.
Most of the SOAP examples that I have seen and worked with so far use RPC to connect
to SOAP server as:
---start - RPC---
import org.apache.soap.rpc.*;
URL url = new URL("http://genx
Apache SOAP has intrinsic support for [de-]serialization of byte[] and String[]. You
do not need to add any type mappings to get these to work. SOAPMappingRegistry maps
byte[] to Base64Serializer, while String[] is handled by ArraySerializer working with
the built-in serialization of String.
Hi folks,
I am struggling with my first web service project on WSAD 5.01.
(J2EE1.2)
I can create a web service from java bean and ejb without any problem,
if I don't use any method taking byte[] or String[] type parameter. I
couldn't understand why byte[] and String[] type arrays are unsupported
