dev@jax-ws.java.net

Re: content types

From: Paul Sandoz <Paul.Sandoz_at_sun.com>
Date: Tue, 30 May 2006 17:37:43 +0200

Oleksiy Stashok wrote:
> Hi,
>
> i have a task in tcp transport during handshaking encode possible
> binding's content types (including parameters) as integer values.
> For instance:
> text/xml : 0
> |application/fastinfoset : 1
> ...
>
> |But first need to get a list of binding supported content types. What
> is the best (or single) way to do that?
>

There are some fixed assumptions.

For the SOAP 1.1 binding there will be "text/xml" and for the SOAP 1.2
binding there will be "application/soap+xml". In both cases soapAction
would be a parameter.

For everthing else things could be negotiated on connection initiation,
including FI and MTOM.

For MTOM i think these are the required MIME types [1].

So we could for now:

- assume SOAP 1.1 for connection negotiation messages:

SOAP 1.1 static MIME type: text/xml
SOAP 1.1 parameters: soapAction

- negotiate the following MIME types for SOAP 1.1:

MTOM static MIME type:
Multipart/Related; start-info="text/xml"; type="application/xop+xml"

MTOM parameters: boundary, soapAction

FI static MIME type: application/fastinfoset
FI parameters: soapAction

Paul.

[1] https://jax-ws.dev.java.net/jax-ws-ea3/docs/mtom-swaref.html

-- 
| ? + ? = To question
----------------\
    Paul Sandoz
         x38109
+33-4-76188109