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


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

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

Subject: Re: [sca-bindings] Action item: Note about TextMessage from SOAP/JMSworking group

Eric Johnson wrote:
> Hi Anish,
> Anish Karmarkar wrote:
>>>       Since the message is already in text format the "encoding"
>>>       attribute in the XML header must be ignored.
>> Perhaps not the best place to discuss this, but why is the encoding
>> attribute in the XML preamble ignored?
> Ah, perhaps we really do need similar text in our JMS binding
> specification, then?  If this isn't immediately obvious, then perhaps it
> deserves restating.  I'll raise an issue to that effect.
> The "encoding" header in the XML stream is there to tell you how to
> interpret a stream of *bytes*.  By the time you're looking at a JMS
> TextMessage, you're already looking at *characters*.

This may be simple case of misunderstanding (on my part).

I'm assuming that we are talking about the xml preamble attribute 
'encoding'. e.g. <?xml version="1.0" encoding="utf-8"?>

Since this is SOAP over JMS, the web services binding layer would use 
the JMS apis to send/receive the SOAP infoset/xml. The SOAP infoset/xml 
is transported over JMS as a text message. The web services layer either 
uses the SOAP infoset (which is abstract and encoding attribute is not 
present) or deals with the serialized XML. The encoding attribute comes 
into play only when dealing with serialized XML. If serialized xml is 
used (anywhere), one can't ignore the encoding attribute. No?


> -Eric.
>> -Anish
>> -- 
>> Eric Johnson wrote:
>>> As per my action item from this last conference call, here's a link
>>> to the text which we just added around using TextMessage with JMS.
>>> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#textmessage-considerations
>>> Since this is a reference into a working document CVS, I'm pasting
>>> the text below as well:
>>> ------------------------------------------------------------------------
>>>         2.4.1 Considerations For Using TextMessage
>>> While the use of |TextMessage| may be attractive in some scenarios,
>>> there are some considerations that go along with it.
>>>     *
>>>       Since the message is already in text format the "encoding"
>>>       attribute in the XML header must be ignored.

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