RE: SOAP implementation for Vienna?

[Krishna Sankar <ksankar@cisco.com>]

Jacq et al,

	From what I know, there are at least three choices.

	1.	User Apache/SOAP and capture the XML document via a facade pattern and
then process it as you wish.
	2.	With Axis, one can register handlers and then the handlers will get the
document and a context.
	3.	Process the XML document from an HTTP POST

	Options 2 and 3 are more flexible, but #1 might be faster. I don't know if
anyone has done #1 with an ebXML TRP 0.98  document yet. I am working on #2
and #3 ;-0. As the Axis project is still in it's infancy, #3 gives us some
flexibility.

	I saw an ebXML prototype at Sun's booth in NY. Do you know how whose SOAP
implementation they are using ?

	On a related note, do you plan to show reliable messaging as well as some
security ? If so, #3 looks like a good choice. You need to validate the XML
Payload and get the required elements from the DOM.

	cheers

> -----Original Message-----
> From: jacques durand [mailto:jacques@savvion.com]
> Sent: Tuesday, April 10, 2001 7:45 PM
> To: ebxml-poc@lists.ebxml.org
> Subject: SOAP implementation for Vienna?
>
>
> Hi all involved in Vienna:
>
> We need to agree on which SOAP implementation option for Vienna
> and unless I missed something, we still have to decide between:
>
> 1. Reusing an existing SOAP implementation, that hides the transport
> protocol to
> the MSH layer (e.g. Apache SOAP/HTTP)
> 2. Upgrade ebXML message handlers stacks  developed for previous demos
> so that they handle SOAP envelope. (These  need  serious upgrade to >=
> 0.98.)
>
> Given the short time, we probably cannot afford the overhead of
> experimenting with
> too diverse connectivity.... I would favor (1).
> Sid: could we add this to the next telecon agenda?
>
> Regards,
>
> Jacques
>
>
>
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-poc-request@lists.ebxml.org
>