You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Andrew Vardeman <an...@iastate.edu> on 2002/05/31 16:53:57 UTC
RE: AW: How do you pass an XML document between Axis and .Net
Cl ient?
Ack!
Maybe this shouldn't bug me since the whole point of Axis is you're not
supposed to care what's on the wire--but the notion of XML-encoding an
entire XML document so it can be passed as a string via RPC, when instead
you could just insert the literal document as the SOAP Body, makes no sense
to me.
You could have this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<my_xml_document><blah/><blah/></my_xml_document>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
or you could have this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:someParameter xmlns:ns1 = "urn:some_namespace"
xsi:type="xsd:string"><my_xml_document><blah/><blah/></my_xml_document></someParameter>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The longer your XML document, and the more entities that need to be
escaped, the more convoluted the second version gets. Like I say, maybe I
just shouldn't care--but what is doc style for if not situations like this?
Sorry if I've overlooked something obvious here. I'm new to all this, and
maybe I've misunderstood the problem or the proposed solution. Anyway, if
you want an example messaging service, check out the message/ directory in
the samples that came with Axis. You can see it creating SOAPBodyElements
from DOM Elements, which is what you want to do. Your messaging client
would need to grab the document element from your DOM (with the
Document.getDocumentElement() call) and pass that to the SOAPBodyElement
constructor. Pass this single SOAPBodyElement to your service, and what
the service will get is a SOAP Envelope with your XML document for the body.
Andrew
At 08:29 AM 5/31/2002 -0500, you wrote:
>You should be able to put the XML doc in a simple string and pass that
>string back and forth.
>
>Jim Stickley
>Birch Telecom
>(816) 300-6743
>jstickley@birch.com
>
>
>-----Original Message-----
>From: Robert Evans [mailto:axis@webdev.apl.jhu.edu]
>Sent: Friday, May 31, 2002 6:41 AM
>To: axis-user@xml.apache.org
>Subject: Re: AW: How do you pass an XML document between Axis and .Net
>Client?
>
>The issue isn't about passing a simple number, what I'd like to figure
>out how to do is to pass a large XML document from/to axis to/from the
>client. If anybody has a straightforward way to do this (RPC or
>Messaging) I would really appreciate the example being shown. I'm sure
>this isn't difficult, I just haven't been able to figure out how to do it.
>
>Bob Evans
>
>Andrew Vardeman wrote:
>
> > But I guess what I'm confused about is why you don't just write a
> > messaging client that manually adds this element to the request:
> >
> > <someNumber xsi:type="xsd:int">8</someNumber>
> >
> > and then sucks the returned XML out of the SOAP Body? Seems so much
> > more straightforward...
> >
> > Andrew
> >
> > At 05:25 PM 5/30/2002 +0200, you wrote:
> >
> >> Hi,
> >>
> >> I have some methods which need an in-parameter (in most cases a
> >> primitive
> >> type like int) and return a XML document.
> >>
> >> Sadly, I haven´t found a way to tell Axis to use RPC mode for the
> >> request
> >> and don´t apply any deserializers on the response, so that I can
> >> extract the
> >> XML document from the response.
> >>
> >> So, I have to return the XML document as a string.
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Andrew Vardeman [mailto:andrewv@iastate.edu]
> >> Gesendet am: Donnerstag, 30. Mai 2002 17:17
> >> An: axis-user@xml.apache.org
> >> Betreff: RE: How do you pass an XML document between Axis and .Net
> >> Client?
> >>
> >> I have limited programming experience, and I don't know what sorts of
> >> things people are using SOAP for out there. One thing I wonder
> >> (possibly
> >> because I just haven't needed to do it yet) is why so many people
> >> want to
> >> write an RPC client that passes an XML document as a parameter. What is
> >> the advantage of this over document-style messaging? Are you passing
> >> other
> >> objects along with the document that you don't want to manually
> >> deserialize, or is it just to avoid making a couple DOM calls to extract
> >> the document from the SOAP Body?
> >>
> >> Just curious,
> >>
> >> Andrew
> >>
> >> At 05:01 PM 5/30/2002 +0200, you wrote:
> >> >Bob,
> >> >
> >> > - use the system.xml.xmldocument to create a XMLDocument (DOM) object
> >> > - use the loadxml method to load a string into it
> >> >
> >> >the precise syntax depends on which .net dialect you use
> >> >
> >> >greetings,
> >> >Gertjan
> >> >
> >> >
> >> >-----Original Message-----
> >> >From: Robert Evans [mailto:bob@beartoothmountain.com]
> >> >Sent: donderdag 30 mei 2002 15:06
> >> >To: axis-user@xml.apache.org
> >> >Subject: How do you pass an XML document between Axis and .Net Client?
> >> >
> >> >
> >> >Greetings,
> >> >
> >> >I have been trying to figure out how to pass an XML document to/from an
> >> >axis web server from/to a .Net client.
> >> >
> >> >As near as I can tell, on the Java side I need to convert the XML
> >> >document to/from a string (no problem). The part I can't figure out is
> >> >how to convert the Xml String to a .Net XML document.
> >> >
> >> >I realize this isn't exactly an Axis issue, but I figured this mailing
> >> >list would have somebody who has done something like this already.
> >> >
> >> >Any hints would be appreciated.
> >> >
> >> >Bob Evans
> >
> >
> >
> >
> >
> >
Re: AW: How do you pass an XML document between Axis and .Net Cl ient?
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Andrew Vardeman" <an...@iastate.edu>
To: <ax...@xml.apache.org>
Sent: Friday, May 31, 2002 10:57 AM
Subject: Re: AW: How do you pass an XML document between Axis and .Net Cl
ient?
> comments inline
>
>
> At 09:58 AM 5/31/2002 -0700, you wrote:
>
> >----- Original Message -----
> >From: "Andrew Vardeman" <an...@iastate.edu>
> >To: <ax...@xml.apache.org>
> >Sent: Friday, May 31, 2002 7:53 AM
> >Subject: RE: AW: How do you pass an XML document between Axis and .Net Cl
> >ient?
> >
> >
> >Ack!
> >
> > >Maybe this shouldn't bug me since the whole point of Axis is you're not
> > >supposed to care what's on the wire--but the notion of XML-encoding an
> > >entire XML document so it can be passed as a string via RPC, when
instead
> > >you could just insert the literal document as the SOAP Body, makes no
sense
> > >to me.
> > >
> >
> >well, imagine you are using a standard XML doc format, like say the 300+
> >page Job description format for printing (http://www.cip4.org/). And
imagine
> >that two years from now you might have to support the next version.
> >
> >if your endpoint has a method like submit(JDF descriptor) your runtime
can
> >handle future versions of the format in the same endpoint, by looking at
the
> >schema version of the payload and running with it.
>
> sure, but couldn't you get the same effect by dropping the XML document
> down a level in the SOAP Body, say, under an "<JDF>" label? You could
> define a request format like this:
>
> <docSubmission>
> <descriptor>some descriptor</descriptor>
> <JDF>
> <blah_blah_blah />
> </JDF>
> </docSubmission>
>
> I understand your point, which is that RPC is good for passing typed
> parameters and you'll often want to pass some parameters along with an XML
> document. But RPC certainly isn't *necessary* for this. I suppose the
> argument would be that agreeing on a standard way of passing these
> parameters is better than defining your own request schema for every web
> service you write.
I am with you in preferring doc/lit over RPC; I dont think RPC works well
over high-latency low-reliability networks.
> I guess I'm thinking of things at the SOAP spec level rather than the
> specific implementation level, which is probably silly. Theoretically,
> couldn't a SOAP toolkit could give you SAX events from the SOAP Body just
> as easily as a complete DOM? I presume no toolkit actually does
> this. When I first looked into SOAP and didn't know about Axis, .NET,
> etc., I thought I would have to be constructing and disassembling SOAP
> Envelopes manually, so I'm still kind of stuck on what *could* be done
> according to the spec, as opposed to what is currently being done by
> specific implementations.
There is a lot to be said for SAX model or Pull model processing of inbound
stuff. We have used it to start validating (and base-64 deconverting)
content as it comes in; gives you a boost over long-haul connections, which
helps meet those pesky SLA process time requriements. That certainly doesnt
work well with RPC bound to methods implementation model, at least not in
Java or C#, neither of which let you curry a function by calling it a
parameter at a time.
Re: AW: How do you pass an XML document between Axis and .Net
Cl ient?
Posted by Andrew Vardeman <an...@iastate.edu>.
comments inline
At 09:58 AM 5/31/2002 -0700, you wrote:
>----- Original Message -----
>From: "Andrew Vardeman" <an...@iastate.edu>
>To: <ax...@xml.apache.org>
>Sent: Friday, May 31, 2002 7:53 AM
>Subject: RE: AW: How do you pass an XML document between Axis and .Net Cl
>ient?
>
>
>Ack!
>
> >Maybe this shouldn't bug me since the whole point of Axis is you're not
> >supposed to care what's on the wire--but the notion of XML-encoding an
> >entire XML document so it can be passed as a string via RPC, when instead
> >you could just insert the literal document as the SOAP Body, makes no sense
> >to me.
> >
>
>well, imagine you are using a standard XML doc format, like say the 300+
>page Job description format for printing (http://www.cip4.org/). And imagine
>that two years from now you might have to support the next version.
>
>if your endpoint has a method like submit(JDF descriptor) your runtime can
>handle future versions of the format in the same endpoint, by looking at the
>schema version of the payload and running with it.
sure, but couldn't you get the same effect by dropping the XML document
down a level in the SOAP Body, say, under an "<JDF>" label? You could
define a request format like this:
<docSubmission>
<descriptor>some descriptor</descriptor>
<JDF>
<blah_blah_blah />
</JDF>
</docSubmission>
I understand your point, which is that RPC is good for passing typed
parameters and you'll often want to pass some parameters along with an XML
document. But RPC certainly isn't *necessary* for this. I suppose the
argument would be that agreeing on a standard way of passing these
parameters is better than defining your own request schema for every web
service you write.
> Also, with a 300 page
>spec, you may want to handle it as SAX events, rather than in a DOM.
I guess I'm thinking of things at the SOAP spec level rather than the
specific implementation level, which is probably silly. Theoretically,
couldn't a SOAP toolkit could give you SAX events from the SOAP Body just
as easily as a complete DOM? I presume no toolkit actually does
this. When I first looked into SOAP and didn't know about Axis, .NET,
etc., I thought I would have to be constructing and disassembling SOAP
Envelopes manually, so I'm still kind of stuck on what *could* be done
according to the spec, as opposed to what is currently being done by
specific implementations.
>I have done this kind of thing with SVG files, because the rendering of the
>SVG is handled by something that takes a file containing the SVG XML; our
>methods were things like print(SVG,dpi,output-format); combining a large XML
>parameter with a couple of primitive types.
>
>-steve
Re: AW: How do you pass an XML document between Axis and .Net Cl ient?
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Andrew Vardeman" <an...@iastate.edu>
To: <ax...@xml.apache.org>
Sent: Friday, May 31, 2002 7:53 AM
Subject: RE: AW: How do you pass an XML document between Axis and .Net Cl
ient?
Ack!
>Maybe this shouldn't bug me since the whole point of Axis is you're not
>supposed to care what's on the wire--but the notion of XML-encoding an
>entire XML document so it can be passed as a string via RPC, when instead
>you could just insert the literal document as the SOAP Body, makes no sense
>to me.
>
well, imagine you are using a standard XML doc format, like say the 300+
page Job description format for printing (http://www.cip4.org/). And imagine
that two years from now you might have to support the next version.
if your endpoint has a method like submit(JDF descriptor) your runtime can
handle future versions of the format in the same endpoint, by looking at the
schema version of the payload and running with it. Also, with a 300 page
spec, you may want to handle it as SAX events, rather than in a DOM.
I have done this kind of thing with SVG files, because the rendering of the
SVG is handled by something that takes a file containing the SVG XML; our
methods were things like print(SVG,dpi,output-format); combining a large XML
parameter with a couple of primitive types.
-steve
Re: RES: AW: How do you pass an XML document between Axis and .Net Cl ient?
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Andrew Vardeman" <an...@iastate.edu>
To: <ax...@xml.apache.org>
Sent: Friday, May 31, 2002 8:44 AM
Subject: Re: RES: AW: How do you pass an XML document between Axis and .Net
Cl ient?
> Well, following the model folks are suggesting for sending XML documents
> via RPC, you could XML-encode the .VRML and send it as a string. If you
> really wanted to, you could Base64-encode the JPG and do the same
> thing. That would be kinda silly though, since the SOAP spec allows MIME
> attachments to be sent following the SOAP Envelope. Inside the SOAP
> Envelope, you reference the file that's included as a MIME
> attachment. According to the User's Guide, Axis has preliminary support
> for SOAP With Attachments. See the attachments/ directory in the Axis
samples.
>
Trouble with SwA is that not all other implementations handle it,
specifically .NET, so if you want true interop its our friend base-64,
making XML based protocols even less efficient than they are already.
Re: RES: AW: How do you pass an XML document between Axis and
.Net Cl ient?
Posted by Andrew Vardeman <an...@iastate.edu>.
Well, following the model folks are suggesting for sending XML documents
via RPC, you could XML-encode the .VRML and send it as a string. If you
really wanted to, you could Base64-encode the JPG and do the same
thing. That would be kinda silly though, since the SOAP spec allows MIME
attachments to be sent following the SOAP Envelope. Inside the SOAP
Envelope, you reference the file that's included as a MIME
attachment. According to the User's Guide, Axis has preliminary support
for SOAP With Attachments. See the attachments/ directory in the Axis samples.
Andrew
At 12:04 PM 5/31/2002 -0300, you wrote:
>Hi Everybody!
>
>I'd like to know if it's possible to pass a .VRML or .JPG documents too.
>Have you had this experience!?
>
>Thank's a lot,
>
>____________________
>Cilas de Freitas
>From: Curitiba - Pr - Brazil
RE: How do you pass .vrml .jpg info
Posted by Chris Haddad <ch...@cobia.net>.
Cilas -
As defined by Jax-RPC, you should probably be using xsd:base64Binary (or
xsd:hexBinary depending upon encoding preferences) that maps to a byte[]
parameter.
Or, use attachments.
/Chris
-----Original Message-----
From: Cilas de Freitas [mailto:cilas@brturbo.com]
Sent: Friday, May 31, 2002 11:04 AM
To: axis-user@xml.apache.org
Subject: RES: AW: How do you pass an XML document between Axis and .Net
Cl ient?
Hi Everybody!
I'd like to know if it's possible to pass a .VRML or .JPG documents too.
Have you had this experience!?
Thank's a lot,
____________________
Cilas de Freitas
From: Curitiba - Pr - Brazil
-----Mensagem original-----
De: Andrew Vardeman [mailto:andrewv@iastate.edu]
Enviada em: sexta-feira, 31 de maio de 2002 11:54
Para: axis-user@xml.apache.org
Assunto: RE: AW: How do you pass an XML document between Axis and .Net
Cl ient?
Ack!
Maybe this shouldn't bug me since the whole point of Axis is you're not
supposed to care what's on the wire--but the notion of XML-encoding an
entire XML document so it can be passed as a string via RPC, when
instead
you could just insert the literal document as the SOAP Body, makes no
sense
to me.
You could have this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<my_xml_document><blah/><blah/></my_xml_document>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
or you could have this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:someParameter xmlns:ns1 = "urn:some_namespace"
xsi:type="xsd:string"><my_xml_document><blah/><blah/></my_xm
l_document></someParameter>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The longer your XML document, and the more entities that need to be
escaped, the more convoluted the second version gets. Like I say, maybe
I
just shouldn't care--but what is doc style for if not situations like
this?
Sorry if I've overlooked something obvious here. I'm new to all this,
and
maybe I've misunderstood the problem or the proposed solution. Anyway,
if
you want an example messaging service, check out the message/ directory
in
the samples that came with Axis. You can see it creating
SOAPBodyElements
from DOM Elements, which is what you want to do. Your messaging client
would need to grab the document element from your DOM (with the
Document.getDocumentElement() call) and pass that to the SOAPBodyElement
constructor. Pass this single SOAPBodyElement to your service, and what
the service will get is a SOAP Envelope with your XML document for the
body.
Andrew
At 08:29 AM 5/31/2002 -0500, you wrote:
>You should be able to put the XML doc in a simple string and pass that
>string back and forth.
>
>Jim Stickley
>Birch Telecom
>(816) 300-6743
>jstickley@birch.com
>
>
>-----Original Message-----
>From: Robert Evans [mailto:axis@webdev.apl.jhu.edu]
>Sent: Friday, May 31, 2002 6:41 AM
>To: axis-user@xml.apache.org
>Subject: Re: AW: How do you pass an XML document between Axis and .Net
>Client?
>
>The issue isn't about passing a simple number, what I'd like to figure
>out how to do is to pass a large XML document from/to axis to/from the
>client. If anybody has a straightforward way to do this (RPC or
>Messaging) I would really appreciate the example being shown. I'm sure
>this isn't difficult, I just haven't been able to figure out how to do
it.
>
>Bob Evans
>
>Andrew Vardeman wrote:
>
> > But I guess what I'm confused about is why you don't just write a
> > messaging client that manually adds this element to the request:
> >
> > <someNumber xsi:type="xsd:int">8</someNumber>
> >
> > and then sucks the returned XML out of the SOAP Body? Seems so much
> > more straightforward...
> >
> > Andrew
> >
> > At 05:25 PM 5/30/2002 +0200, you wrote:
> >
> >> Hi,
> >>
> >> I have some methods which need an in-parameter (in most cases a
> >> primitive
> >> type like int) and return a XML document.
> >>
> >> Sadly, I haven´t found a way to tell Axis to use RPC mode for the
> >> request
> >> and don´t apply any deserializers on the response, so that I can
> >> extract the
> >> XML document from the response.
> >>
> >> So, I have to return the XML document as a string.
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Andrew Vardeman [mailto:andrewv@iastate.edu]
> >> Gesendet am: Donnerstag, 30. Mai 2002 17:17
> >> An: axis-user@xml.apache.org
> >> Betreff: RE: How do you pass an XML document between Axis and .Net
> >> Client?
> >>
> >> I have limited programming experience, and I don't know what sorts
of
> >> things people are using SOAP for out there. One thing I wonder
> >> (possibly
> >> because I just haven't needed to do it yet) is why so many people
> >> want to
> >> write an RPC client that passes an XML document as a parameter.
What is
> >> the advantage of this over document-style messaging? Are you
passing
> >> other
> >> objects along with the document that you don't want to manually
> >> deserialize, or is it just to avoid making a couple DOM calls to
extract
> >> the document from the SOAP Body?
> >>
> >> Just curious,
> >>
> >> Andrew
> >>
> >> At 05:01 PM 5/30/2002 +0200, you wrote:
> >> >Bob,
> >> >
> >> > - use the system.xml.xmldocument to create a XMLDocument (DOM)
object
> >> > - use the loadxml method to load a string into it
> >> >
> >> >the precise syntax depends on which .net dialect you use
> >> >
> >> >greetings,
> >> >Gertjan
> >> >
> >> >
> >> >-----Original Message-----
> >> >From: Robert Evans [mailto:bob@beartoothmountain.com]
> >> >Sent: donderdag 30 mei 2002 15:06
> >> >To: axis-user@xml.apache.org
> >> >Subject: How do you pass an XML document between Axis and .Net
Client?
> >> >
> >> >
> >> >Greetings,
> >> >
> >> >I have been trying to figure out how to pass an XML document
to/from an
> >> >axis web server from/to a .Net client.
> >> >
> >> >As near as I can tell, on the Java side I need to convert the XML
> >> >document to/from a string (no problem). The part I can't figure
out is
> >> >how to convert the Xml String to a .Net XML document.
> >> >
> >> >I realize this isn't exactly an Axis issue, but I figured this
mailing
> >> >list would have somebody who has done something like this already.
> >> >
> >> >Any hints would be appreciated.
> >> >
> >> >Bob Evans
> >
> >
> >
> >
> >
> >
RES: AW: How do you pass an XML document between Axis and .Net Cl ient?
Posted by Cilas de Freitas <ci...@brturbo.com>.
Hi Everybody!
I'd like to know if it's possible to pass a .VRML or .JPG documents too.
Have you had this experience!?
Thank's a lot,
____________________
Cilas de Freitas
From: Curitiba - Pr - Brazil
-----Mensagem original-----
De: Andrew Vardeman [mailto:andrewv@iastate.edu]
Enviada em: sexta-feira, 31 de maio de 2002 11:54
Para: axis-user@xml.apache.org
Assunto: RE: AW: How do you pass an XML document between Axis and .Net
Cl ient?
Ack!
Maybe this shouldn't bug me since the whole point of Axis is you're not
supposed to care what's on the wire--but the notion of XML-encoding an
entire XML document so it can be passed as a string via RPC, when
instead
you could just insert the literal document as the SOAP Body, makes no
sense
to me.
You could have this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<my_xml_document><blah/><blah/></my_xml_document>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
or you could have this:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:someParameter xmlns:ns1 = "urn:some_namespace"
xsi:type="xsd:string"><my_xml_document><blah/><blah/></my_xm
l_document></someParameter>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The longer your XML document, and the more entities that need to be
escaped, the more convoluted the second version gets. Like I say, maybe
I
just shouldn't care--but what is doc style for if not situations like
this?
Sorry if I've overlooked something obvious here. I'm new to all this,
and
maybe I've misunderstood the problem or the proposed solution. Anyway,
if
you want an example messaging service, check out the message/ directory
in
the samples that came with Axis. You can see it creating
SOAPBodyElements
from DOM Elements, which is what you want to do. Your messaging client
would need to grab the document element from your DOM (with the
Document.getDocumentElement() call) and pass that to the SOAPBodyElement
constructor. Pass this single SOAPBodyElement to your service, and what
the service will get is a SOAP Envelope with your XML document for the
body.
Andrew
At 08:29 AM 5/31/2002 -0500, you wrote:
>You should be able to put the XML doc in a simple string and pass that
>string back and forth.
>
>Jim Stickley
>Birch Telecom
>(816) 300-6743
>jstickley@birch.com
>
>
>-----Original Message-----
>From: Robert Evans [mailto:axis@webdev.apl.jhu.edu]
>Sent: Friday, May 31, 2002 6:41 AM
>To: axis-user@xml.apache.org
>Subject: Re: AW: How do you pass an XML document between Axis and .Net
>Client?
>
>The issue isn't about passing a simple number, what I'd like to figure
>out how to do is to pass a large XML document from/to axis to/from the
>client. If anybody has a straightforward way to do this (RPC or
>Messaging) I would really appreciate the example being shown. I'm sure
>this isn't difficult, I just haven't been able to figure out how to do
it.
>
>Bob Evans
>
>Andrew Vardeman wrote:
>
> > But I guess what I'm confused about is why you don't just write a
> > messaging client that manually adds this element to the request:
> >
> > <someNumber xsi:type="xsd:int">8</someNumber>
> >
> > and then sucks the returned XML out of the SOAP Body? Seems so much
> > more straightforward...
> >
> > Andrew
> >
> > At 05:25 PM 5/30/2002 +0200, you wrote:
> >
> >> Hi,
> >>
> >> I have some methods which need an in-parameter (in most cases a
> >> primitive
> >> type like int) and return a XML document.
> >>
> >> Sadly, I haven´t found a way to tell Axis to use RPC mode for the
> >> request
> >> and don´t apply any deserializers on the response, so that I can
> >> extract the
> >> XML document from the response.
> >>
> >> So, I have to return the XML document as a string.
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Andrew Vardeman [mailto:andrewv@iastate.edu]
> >> Gesendet am: Donnerstag, 30. Mai 2002 17:17
> >> An: axis-user@xml.apache.org
> >> Betreff: RE: How do you pass an XML document between Axis and .Net
> >> Client?
> >>
> >> I have limited programming experience, and I don't know what sorts
of
> >> things people are using SOAP for out there. One thing I wonder
> >> (possibly
> >> because I just haven't needed to do it yet) is why so many people
> >> want to
> >> write an RPC client that passes an XML document as a parameter.
What is
> >> the advantage of this over document-style messaging? Are you
passing
> >> other
> >> objects along with the document that you don't want to manually
> >> deserialize, or is it just to avoid making a couple DOM calls to
extract
> >> the document from the SOAP Body?
> >>
> >> Just curious,
> >>
> >> Andrew
> >>
> >> At 05:01 PM 5/30/2002 +0200, you wrote:
> >> >Bob,
> >> >
> >> > - use the system.xml.xmldocument to create a XMLDocument (DOM)
object
> >> > - use the loadxml method to load a string into it
> >> >
> >> >the precise syntax depends on which .net dialect you use
> >> >
> >> >greetings,
> >> >Gertjan
> >> >
> >> >
> >> >-----Original Message-----
> >> >From: Robert Evans [mailto:bob@beartoothmountain.com]
> >> >Sent: donderdag 30 mei 2002 15:06
> >> >To: axis-user@xml.apache.org
> >> >Subject: How do you pass an XML document between Axis and .Net
Client?
> >> >
> >> >
> >> >Greetings,
> >> >
> >> >I have been trying to figure out how to pass an XML document
to/from an
> >> >axis web server from/to a .Net client.
> >> >
> >> >As near as I can tell, on the Java side I need to convert the XML
> >> >document to/from a string (no problem). The part I can't figure
out is
> >> >how to convert the Xml String to a .Net XML document.
> >> >
> >> >I realize this isn't exactly an Axis issue, but I figured this
mailing
> >> >list would have somebody who has done something like this already.
> >> >
> >> >Any hints would be appreciated.
> >> >
> >> >Bob Evans
> >
> >
> >
> >
> >
> >