PERFUME PROPOSAL: SOAP FOR COCOON
For the web application project I'm orchestrating, we
wish to add commercial quality support for SOAP
messaging: both act as a client and as a server.
I have examined the existing soap client package,
and new soap package, but I'm uncomfortable with
them because the former is xsp based, and the later
is implemented only as a reader.
It is my opinion that Cocoon needs components that can
play well together, and can be mixed and matched.
Therefore, I'd like to propose a package I call
"PERFUME."
PERFUME:
1) The implementation of Perfume shall result
in three distinct Cocoon components:
a) A generator that can receive a soap
message and turn it into an xml sax
stream.
b) A serializer that can convert an xml
stream into a return soap message.
c) A transformer that can act as a soap
client. Incoming xml is transmitted
as a soap message, the pipe is blocked
until return or time out, and then the
received message is returned into the xml
sax stream.
2) The intended usage is:
a) If one wishes to implement a soap service,
a pipeline beginning with the generator
and ending with the serializer is
constructed.
b) If one wishes to implement a soap client,
a pipeline with the transformer is constructed.
3) Construction:
It seems to me there are really two fundamental
modules to this effort: a module that converts
a sax stream to HTTP-SOAP, and a module that
convert HTTP-SOAP to an xml sax stream. Both
modules are used twice in the overall project,
both being used in the transformer component.
4) Issues:
a) First, how does this proposal sound to you?
Is this the type of soap implementation you
would like to see?
b) Are any of the existing cocoon soap related
software suitably reusable and appropriate
here.
c) Is apache soap/axis suitable for use here?
My preliminary examination of these packages
are they overlap too much with existing
cocoon to be easily integrated.
d) It seems like the generator and serializer need
potentially an out-of-pipeline connection with
each other. Or that some method of the generator
conveying forward a soap related error to the
serializer is needed.
e) Should WSDL be incorporate into this proposal?
Please someone correct me if I'm wrong, but
don't WSDL and XmlSchema do almost the same
thing? It seems like most of WSDL was a early
solution before XmlSchema became ready. I think
ebXml also makes no reference to WSDL.
f) Should the soap-client transformer be able to
execute multiple soap request to different
services and not just one action? Probably so.
SHORT-CIRCUIT: NEEEEED INPUT!
Steven P. Punte
Candlelight Software
[EMAIL PROTECTED]
http://www.candlelightsoftware.com
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
