Re: [ebxml-msg] Multiple handlers

[Duane Nickull <dnickull@adobe.com>]

Jacques, Dale Matt:

Thanks for the responses.  This was exactly what I needed to confirm.

Duane

Jacques Durand wrote:

> Duane:
>
> There is nothing explicit one way or the other in the ebMS spec,
> so that would mean you may but don't have to support several listeners...
> Nothing in the message header requires mention of the actual endpoint 
> value ,
> so the way endpoints are handled (as well as CPA) by an MSH is 
> implementation specific.
> (e.g. how to specify the URL to send your messages to, or where to 
> listen.)
>
> Now I wouldn't qualify as misalignment the fact taht ebMS spec does 
> not explicitly
> require an MSH to support several Transport elements associated with a 
> Party in CPP
> (or that CPP allows for more than what ebMS requires).
> You could say that CPP also describes deployment conditions, beyond 
> ebMS scope.
>
> Jacques
>
> -----Original Message-----
> From: Duane Nickull [mailto:dnickull@adobe.com]
> Sent: Friday, January 23, 2004 4:23 PM
> To: ebxml-msg@lists.oasis-open.org
> Subject: [ebxml-msg] Multiple handlers
>
>
> Question:
>
> I reviewed the specification and did not find an answer to this question.
>
> Is there anything in the ebXML MS spec that says a MS implementation
> MUST be capable of supporting multiple HTTP listeners? CPA allows there
> to be multiple listeners/transport endpoints listed for MSH's that may
> have more than 1 endpoint.  Does this seem logical or is it a potential
> misalignment of the specifications.
>
> Thanks
>
> Duane
>
> -- 
> Senior Standards Strategist
> Adobe Systems, Inc.
> http://www.adobe.com
>
>
>
> To unsubscribe from this mailing list (and be removed from the roster 
> of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/members/leave_workgroup.php.
>

-- 
Senior Standards Strategist
Adobe Systems, Inc.
http://www.adobe.com