Re: [ebxml-msg] Multiple handlers

[mattm@adobe.com]

Duane,

I think CPA was meant to be flexible enough to allow vendors to support potentially strange configurations of the messaging layer.  I don't think there is really a misalignment.  If the CPA team defined a narrow set of options, then they would run the risk of being called "ebXML Messaging Configuration Format" :-)

Besides...if you look closely at the ebMS spec, you don't really need CPA support in an MSH.  A CPAId is really only a configuration identifier.  Some vendors use property files instead of CPAs.  

-Matt

----- Original Message -----
From: Duane Nickull <dnickull@adobe.com>
Date: Friday, January 23, 2004 8:22 pm
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.
> 
>