Very basic Soap vs HTTP Post

[Jerry Murray <Jm...@Ironplanet.com>]

I have an application in which I need to pass an XML document from one
system to another.  Point to Point and both systems are under our control.
The requirement is to simply pass the XML file and no object needs to be
passed back.

I can pass use a Java app to simply "post" the file to the URL of the
server.  Would using SOAP add anything?  
 


Jerry Murray
jmurray@ironplanet.com
925-225-8746

Re: Very basic Soap vs HTTP Post

[chuck clark <cc...@ziclix.com>]

Following on what Cory said...I've basically got the same requirements as you
Jerry...I have a String of XML which I need to send to the server...I found the
overhead of parsing the String with the DOM and then constructing the Call was
quite a bit of overhead....so instead I use the HTTPUtil.Post utility to write
the envelope myself...but then on the server side my method expects a
w3c.dom.Element...since in my envelope i set the encoding to Literal XML the
SOAP framework automatically parses the string and calls the method on my
object which takes and Element as a parameter...

originally i didn't need anything to be returned either but now i'm changing it
so i can receive some XML in response...so this change has been very easy

plus all error handling comes to me for free....the apache classes worry about
opening connections and finding the server and such and provide me with a very
clean interface

chuck

Cory Isaacson wrote:

> Jerry,
>
> The advantages of SOAP (while not major in this case) are:
>
> 1) SOAP can take the document as a DOM, and your Java code on the remote
> side can receive it as a DOM, so if that's your end target its a bit easier.
> This is using the LiteralXML encoding.
>
> 2) SOAP also has a nice error processing capability, to return any errors.
>
> Later, if you want to run a method using the XML SOAP would have much
> stronger advantages, but with what you want to do now this is what occurs to
> me.
>
> Cory
> ----- Original Message -----
> From: "Jerry Murray" <Jm...@Ironplanet.com>
> To: <so...@xml.apache.org>
> Sent: Monday, November 06, 2000 5:10 PM
> Subject: Very basic Soap vs HTTP Post
>
> >
> > I have an application in which I need to pass an XML document from one
> > system to another.  Point to Point and both systems are under our control.
> > The requirement is to simply pass the XML file and no object needs to be
> > passed back.
> >
> > I can pass use a Java app to simply "post" the file to the URL of the
> > server.  Would using SOAP add anything?
> >
> >
> >
> > Jerry Murray
> > jmurray@ironplanet.com
> > 925-225-8746
> >

Re: Very basic Soap vs HTTP Post

[chuck clark <cc...@ziclix.com>]

Following on what Cory said...I've basically got the same requirements as you
Jerry...I have a String of XML which I need to send to the server...I found the
overhead of parsing the String with the DOM and then constructing the Call was
quite a bit of overhead....so instead I use the HTTPUtil.Post utility to write
the envelope myself...but then on the server side my method expects a
w3c.dom.Element...since in my envelope i set the encoding to Literal XML the
SOAP framework automatically parses the string and calls the method on my
object which takes and Element as a parameter...

originally i didn't need anything to be returned either but now i'm changing it
so i can receive some XML in response...so this change has been very easy

plus all error handling comes to me for free....the apache classes worry about
opening connections and finding the server and such and provide me with a very
clean interface

chuck

Cory Isaacson wrote:

> Jerry,
>
> The advantages of SOAP (while not major in this case) are:
>
> 1) SOAP can take the document as a DOM, and your Java code on the remote
> side can receive it as a DOM, so if that's your end target its a bit easier.
> This is using the LiteralXML encoding.
>
> 2) SOAP also has a nice error processing capability, to return any errors.
>
> Later, if you want to run a method using the XML SOAP would have much
> stronger advantages, but with what you want to do now this is what occurs to
> me.
>
> Cory
> ----- Original Message -----
> From: "Jerry Murray" <Jm...@Ironplanet.com>
> To: <so...@xml.apache.org>
> Sent: Monday, November 06, 2000 5:10 PM
> Subject: Very basic Soap vs HTTP Post
>
> >
> > I have an application in which I need to pass an XML document from one
> > system to another.  Point to Point and both systems are under our control.
> > The requirement is to simply pass the XML file and no object needs to be
> > passed back.
> >
> > I can pass use a Java app to simply "post" the file to the URL of the
> > server.  Would using SOAP add anything?
> >
> >
> >
> > Jerry Murray
> > jmurray@ironplanet.com
> > 925-225-8746
> >

Re: Very basic Soap vs HTTP Post

[Cory Isaacson <ci...@capita2.com>]

Jerry,

The advantages of SOAP (while not major in this case) are:

1) SOAP can take the document as a DOM, and your Java code on the remote
side can receive it as a DOM, so if that's your end target its a bit easier.
This is using the LiteralXML encoding.

2) SOAP also has a nice error processing capability, to return any errors.

Later, if you want to run a method using the XML SOAP would have much
stronger advantages, but with what you want to do now this is what occurs to
me.

Cory
----- Original Message -----
From: "Jerry Murray" <Jm...@Ironplanet.com>
To: <so...@xml.apache.org>
Sent: Monday, November 06, 2000 5:10 PM
Subject: Very basic Soap vs HTTP Post


>
> I have an application in which I need to pass an XML document from one
> system to another.  Point to Point and both systems are under our control.
> The requirement is to simply pass the XML file and no object needs to be
> passed back.
>
> I can pass use a Java app to simply "post" the file to the URL of the
> server.  Would using SOAP add anything?
>
>
>
> Jerry Murray
> jmurray@ironplanet.com
> 925-225-8746
>

Re: Very basic Soap vs HTTP Post

[Cory Isaacson <ci...@capita2.com>]

Jerry,

The advantages of SOAP (while not major in this case) are:

1) SOAP can take the document as a DOM, and your Java code on the remote
side can receive it as a DOM, so if that's your end target its a bit easier.
This is using the LiteralXML encoding.

2) SOAP also has a nice error processing capability, to return any errors.

Later, if you want to run a method using the XML SOAP would have much
stronger advantages, but with what you want to do now this is what occurs to
me.

Cory
----- Original Message -----
From: "Jerry Murray" <Jm...@Ironplanet.com>
To: <so...@xml.apache.org>
Sent: Monday, November 06, 2000 5:10 PM
Subject: Very basic Soap vs HTTP Post


>
> I have an application in which I need to pass an XML document from one
> system to another.  Point to Point and both systems are under our control.
> The requirement is to simply pass the XML file and no object needs to be
> passed back.
>
> I can pass use a Java app to simply "post" the file to the URL of the
> server.  Would using SOAP add anything?
>
>
>
> Jerry Murray
> jmurray@ironplanet.com
> 925-225-8746
>