Saminda
I just noticed in your example:
The X-Service-Path header would not be a MIME Header but an SMTP
header. Only the Content-Description would be in the MIME headers. We
would ignore the X-Service-Path in the SMTP message.
I have updated the doc to show this properly in the example.
Paul
+1 Saminda
Paul
On 12/7/06, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
Hi All,
In addition to this, we have to consider the Part disposition as well. With
the Paul's proposal we have two Parts in message body
1. Empty in line part with "text/plain"
2. Attachment part with "application/soap
Hi All,
In addition to this, we have to consider the Part disposition as well. With
the Paul's proposal we have two Parts in message body
1. Empty in line part with "text/plain"
2. Attachment part with "application/soap+xml"
Thus, we need to include disposition to separate one from other. Thus
David
I agree addressing is a good way to support this, and in general
should be used. However, if we want to have something at the SOAP
binding layer then this should deal with the fact that not every SOAP
message has WS-Addressing headers.
In addition it is more efficient to do routing at the
+1
Saminda
On 12/6/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Oh I forgot to mention. I'd like us to implement this in Axis2. I
guess we need a property to define whether we use the SOAP1.2 email
binding or this binding.
Paul
On 12/6/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Hi
>
>
Sorry, I have to ask... why not ws-addressing?
You could embed an EPR with a refparam identifying the service in the
WSDL which should then be copied to the SOAP Header. Or even just use
the fact that the ?X-Service-Path would be automatically copied into a
wsa:To element.
Per Basic Profile 1.1
Oh I forgot to mention. I'd like us to implement this in Axis2. I
guess we need a property to define whether we use the SOAP1.2 email
binding or this binding.
Paul
On 12/6/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Hi
I've been working with a consortium who want to be able to use smtp
mail
Hi
I've been working with a consortium who want to be able to use smtp
mail for SOAP1.2. The current SOAP 1.2 binding for email has a concern
that the message is the main body of the email, and might be corrupted
by spam or anti-virus filters that add text into the message.
So the proposal that
