Re: [ebxml-msg] Standard API for ebXML Messaging

[Matthew MacKenzie <matt@yellowdragonsoft.com>]

Dale,

It may make sense to undertake this activity under the umbrella of a new 
TC, as this may also be applicable to the WS-* stuff, especially since 
WS is moving toward having features similar to ebMS.

-matt

Dale Moberg wrote:

>Hi Matt,
>
>I think this is a good project, and it seems to be 
>defining the legendary MSI! 
>
>Is this a Messaging subteam effort or a new (short-lived) TC?
>
>In addition to the uses you mention, MSI was to define interfaces for 
>message status inquiry and maybe MSH-ping/pong (at least that is what I
>recall).
>
>Dale
>
>-----Original Message-----
>From: Matthew MacKenzie [mailto:matt@yellowdragonsoft.com] 
>Sent: Thursday, July 10, 2003 7:38 AM
>To: ebxml-msg@lists.oasis-open.org; ebxml-dev@lists.ebxml.org
>Subject: [ebxml-msg] Standard API for ebXML Messaging
>Importance: Low
>
>
>A reoccuring issue for those who are new to ebXML Messaging is the lack 
>of a standardized API into the backend of the messaging system.  By 
>'backend', I'm referring to the application binding side of the server.
>
>The API that an application such as an EJB or perl module would need to 
>use in order to register itself with the messaging service, forward 
>outbound messages to the MSH for delivery to, and receive inbound 
>messages from the MSH.
>
>We at Yellow Dragon have created our own proprietary API for integrating
>
>MSH services into business logic, and I am sure all of the other vendors
>
>(there are at least 12 of you) have done the same. 
>
>Is there any interest among vendors and other parties to start work on a
>
>standardized API?
>
>  
>

-- 
Matthew MacKenzie
Yellow Dragon Software Corporation
http://www.yellowdragonsoft.com/
m: +1 506.869.0175