I have the potential to send XML files in excess of 400MB via SOAP. I
noticed that java.io.InputStream can be used as a parameter for my method.
If I do not specify literalxml encoding in the envelope, can I bring the XML
in through as a stream, and have my method start chomping on the data befor
I followed the example I found at
http://www.onjava.com/pub/a/onjava/2002/02/27/tomcat.html?page=1 to the
letter, but am having a slight problem. When I install the deployed class
as /webapps/soap/WEB-INF/classes/onjava/CalcService.class I
get this error from the client:
$ java onjava.Calc
Use
Literal Encoding and Send the XML as a DOM Element. Much
easier.
Call
call = new Call();call.setTargetObjectURI( URI );call.setMethodName(
Mtds );call.setEncodingStyleURI( Constants.NS_URI_LITERAL_XML
); Vector params = new
Vector();params.addElement( new Parameter( "Param01",
I'm finding some trouble on sending a request via XML.
Can I encode my xml request as a String which will be in turn encoded in a
SOAP envelope and then parse it on the server side? If so what API's are there
to parse my xml string-like request?
Look forward to hear from you.
The xml string w
I've found that the exception message string is not XML encoded. However
it is XML decoded in the client!?!?! This sounds like a bug to me...
Anyway, change
throw new Exception("");
to
throw new Exception(org.apache.soap.Utils.cleanString(""));
and all is well.
You don't have to X
Hi to
all SOAP Developers!
I want
to know if it is possible to submit a request with a XML format encoded in a
SOAP envelope.
The question: I want to allow a
client to invoke a service with a generic format, like variable number and
type of input parameters, (which I suppose it could be i
I have a method that returns an object (a bean).
The server is configured to serialize this object using the BeanSerializer. The
returned XML is a Struct?
--
GRIDSYSTEMS
Francisco Jose Avila BermejoParc Bit - Son
Espanyol Responsable Área
Desarrollo07120 Palma de
> Hi,
>
> This is a more or less well known problem or feature in Soap2.2 a
> specialized class will be serialized as the superclass which your server
> code returns and not as the spesialized class which it was constructed as.
> To get around this you'll either have to change to bean serializer
-Original Message-
From: dovle [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 21, 2002 1:48 PM
To: '[EMAIL PROTECTED]'
Subject: Simple question
Hi all,
My situation
Class A (bean)
Class B (bean too) extends A
A method( params )
{
return new B() ;
}
The encoding is for the
Hi,
This is a more or less well known problem or feature in Soap2.2 a
specialized class will be serialized as the superclass which your server
code returns and not as the spesialized class which it was constructed as.
To get around this you'll either have to change to bean serializer code or
pos
Answer inline :
> Hi,
>
> Isn't this a question for a Beans forum, like the one on
> http://forum.java.sun.com/forum.jsp?forum=39
nope. Why do you think this ?
My 'problem' is that I really return a B object but the apache soap sees it
as a A class (only an A object) because of the method sig
Hi all,
My situation
Class A (bean)
Class B (bean too) extends A
A method( params )
{
return new B() ;
}
The encoding is for the A class. Is this thing correct ? Why ? (supposing I
have registered also the B class)
thanks
dovle
Hi,
Isn't this a question for a Beans forum, like the one on
http://forum.java.sun.com/forum.jsp?forum=39
Michel
-Original Message-
From: dovle [mailto:[EMAIL PROTECTED]]
Sent: donderdag 21 maart 2002 13:48
To: '[EMAIL PROTECTED]'
Subject: Simple question
Hi all,
My situation
Class
Hi TIA,
I think this is a classpath problem, you should
place the jar file contining your service classes into the TOMCAT\lib
directory.
I hope, it helps much,
Csilla
Hi!
Here is a link where you can study an exemple about
SOAP attachments:
http://www-106.ibm.com/developerworks/webservices/library/ws-soapatt/
Good luck,
Csilla
15 matches
Mail list logo
