On Sunday, September 22, 2002, at 08:54 PM, Steven Punte wrote:
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
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.
Why not use an
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
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.
Why not use an
Hi Steven,
Interesting proposal - it reminds me of what I was thinking about a
month ago :-) Comments are below:
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
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
On Saturday, September 21, 2002, at 05:37 PM, Steven Punte wrote:
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
