OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: issue from 20 July con-call

Regarding the following issue raised in the con-call:

Issue: Can we architect TRP so that if/when SOAP is approved 
as a standard, we can just drop it in and use?

This all depends upon whether you consider SOAP as a
packaging solution or as a message (payload). A SOAP
message as payload is currently supported in the TR&P


Content-Type: multipart/related; type=application/vnd.ebxml; version=0.1;
Content-Length: nnnn

Content-ID: UUID
Content-Length: nnnn
Content-Type: application/vnd.ebxml

<?xml version="1.0" encoding="UTF-8"?>
<ebXMLHeader xmlns="http://www.ebxml.org/ebXMLStds/MessageHeader"
			<DocumentLabel>SOAP THINGY</DocumentLabel>
... <!-- yadda yadda yadda -->
Content-ID: UUID-2
Content-Length: nnnn
Content-Type: text/xml

		<m:GetLastTradePriceResponse xmlns:m="Some-URI">

If, on the other hand, you consider SOAP as the packaging
solution, the answer is no for the very same reasons that
BizTalk has chosen to use MIME packaging and more as outlined
in the TR&P Message Envelope Specification.



    _/_/_/_/ _/    _/ _/    _/ Christopher Ferris - Enterprise Architect
   _/       _/    _/ _/_/  _/  Phone: 781-442-3063 or x23063
  _/_/_/_/ _/    _/ _/ _/ _/   Email: chris.ferris@East.Sun.COM
       _/ _/    _/ _/  _/_/    Sun Microsystems,  Mailstop: UBUR03-313
_/_/_/_/  _/_/_/  _/    _/     1 Network Drive Burlington, MA 01803-0903

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC