You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Frank Starsinic <fs...@apengines.com> on 2001/01/09 18:48:54 UTC
SOAP architecture question
The application where we use soap is basically
an adapter that formats and passes messages (xml)
to and from our workflow system and our customers'
systems.
SOAP
WF <-------> Adapter <-------> Customer
<xml> <xml>
We are always passing XML between
our workflow system and our customers external
applications, never turning xml into objects, or
objects into xml (in that layer).
It seems that the apache SOAP API is meant more for creating
a Call() object, and creating parameters from object
properties. Then it gets back a Response() object and
does the same thing in reverse to get back to an object.
It seems that we could totally skip this step and
somehow just use XSLT to transform the original XML
into something that the SOAP server can understand.
Then for the response, just take the raw SOAP packet,
transform it using XSLT and send it back to workflow.
Is there some other way that is typically used for
this? Are there any things we should be concerned about
such as encoding or anything else? Should we use a servlet instead?
straight HTTP Posts?
I'm wrinting this because, even though we've had success
using the apache-soap api, it seems like we're adding
work for ourselves by taking xml, turning it into a call()
object, which basically creates XML again in a different
format, and back again, blah blah blah.
Thanks for any architectural input.
frank