cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Diephouse <dan.diepho...@mulesource.com>
Subject Re: WS-Addressing Issues
Date Fri, 07 Sep 2007 17:02:07 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
#3 still hasn't been discussed though. I'd still like hear to from
others on how to best support decoupled endpoints over ESB transports
(JBI, Mule, and the like). <br>
<br>
- Dan<br>
<br>
Daniel Kulp wrote:
<blockquote cite="mid:200709071237.36504.dkulp@apache.org" type="cite">
  <pre wrap="">
The quick executive summary is:
1) It's not a problem.  The implementation is OK to do this.   It's not 
optimal, but OK.  Issue created:
  <a class="moz-txt-link-freetext" href="https://issues.apache.org/jira/browse/CXF-981">https://issues.apache.org/jira/browse/CXF-981</a>

That was the point of the discussion.  We were trying to figure out if 
the issue is enough to warrant delaying 2.0.2.   The answer is no.


2) For code first cases (no wsdl policy extensors) adding the 
feature/interceptors should be enough to enable WS-A.   (Usability 
issue)   However, the user then takes on the responsibility of making 
sure the server will actually be OK with WS-A.     Any more thoughts on 
this?

Dan


On Friday 07 September 2007, Glynn, Eoghan wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">FYI sorted out on IRC, see <a class="moz-txt-link-freetext" href="http://dev.rectang.com/logs/codehaus/%23cxf">http://dev.rectang.com/logs/codehaus/%23cxf</a>

Cheers,
Eoghan

    </pre>
    <blockquote type="cite">
      <pre wrap="">-----Original Message-----
From: Dan Diephouse [<a class="moz-txt-link-freetext" href="mailto:dan.diephouse@mulesource.com">mailto:dan.diephouse@mulesource.com</a>]
Sent: 06 September 2007 16:56
To: <a class="moz-txt-link-abbreviated" href="mailto:cxf-dev@incubator.apache.org">cxf-dev@incubator.apache.org</a>
Subject: WS-Addressing Issues

I'm having some issues getting WS-A to work for me.

First, it seems that adding the WSAddressingFeature isn't
enough to get WS-A to be turned on. You have to set the
"usingAddressingAdvisory"
property which is cryptic at best. Why isn't adding the
interceptors to the client enough for it to start sending
WS-A headers? Why would we want it turned off by default?

Second, I'm running the WS-A sample and it appears to be
sending two soap messages to the client - one partial
response and one decoupled message. From the logs:

INFO: Outbound Message
--------------------------------------
&lt;<a class="moz-txt-link-freetext" href="soap:Envelope">soap:Envelope</a>
xmlns:soap=<a class="moz-txt-link-rfc2396E" href="http://schemas.xmlsoap.org/soap/envelope/">"http://schemas.xmlsoap.org/soap/envelope/"</a>&gt;<a
class="moz-txt-link-rfc2396E" href="soap:Header">&lt;soap:H
eader&gt;</a>&lt;MessageID
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;urn:uuid:9bd2e4c4
-cca0-478d-bc81-a57e92b9c1c4&lt;/MessageID&gt;&lt;To
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;<a
class="moz-txt-link-freetext" href="http://localhost:">http://localhost:</a>
9000/SoapContext/SoapPort&lt;/To&gt;&lt;ReplyTo
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;&lt;Address&gt;<a
class="moz-txt-link-freetext" href="http://l">http://l</a>
ocalhost:9990/decoupled_endpoint&lt;/Address&gt;&lt;/ReplyTo&gt;&lt;FaultTo
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;&lt;Address&gt;<a
class="moz-txt-link-freetext" href="http://l">http://l</a>
ocalhost:9990/decoupled_endpoint&lt;/Address&gt;&lt;/FaultTo&gt;&lt;/<a
class="moz-txt-link-freetext" href="soap:Hea">soap:Hea</a>
der&gt;<a class="moz-txt-link-rfc2396E" href="soap:Body">&lt;soap:Body&gt;</a>&lt;sayHi
xmlns=<a class="moz-txt-link-rfc2396E" href="http://apache.org/hello_world_soap_http/types">"http://apache.org/hello_world_soap_http/types"</a>/&gt;&lt;/soap:
Body&gt;&lt;/<a class="moz-txt-link-freetext" href="soap:Envelope">soap:Envelope</a>&gt;
--------------------------------------
...
INFO: Inbound Message
--------------------------------------
Headers: {null=[HTTP/1.1 202 Accepted], connection=[close],
SOAPAction=[""], Server=[Jetty(6.1.5)],
content-type=[text/xml; charset=utf-8]}
Message:
&lt;<a class="moz-txt-link-freetext" href="soap:Envelope">soap:Envelope</a>
xmlns:soap=<a class="moz-txt-link-rfc2396E" href="http://schemas.xmlsoap.org/soap/envelope/">"http://schemas.xmlsoap.org/soap/envelope/"</a>&gt;<a
class="moz-txt-link-rfc2396E" href="soap:Header">&lt;soap:H
eader&gt;</a>&lt;MessageID
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;urn:uuid:d15fa093
-3951-47f5-86ac-bd616f8d57d7&lt;/MessageID&gt;&lt;To
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;<a
class="moz-txt-link-freetext" href="http://www.w3.org">http://www.w3.org</a>
/2005/08/addressing/anonymous&lt;/To&gt;&lt;ReplyTo
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;&lt;Address&gt;<a
class="moz-txt-link-freetext" href="http://w">http://w</a>
ww.w3.org/2005/08/addressing/none&lt;/Address&gt;&lt;/ReplyTo&gt;&lt;/<a
class="moz-txt-link-freetext" href="soap:He">soap:He</a>
ader&gt;<a class="moz-txt-link-rfc2396E" href="soap:Body/">&lt;soap:Body /&gt;</a>&lt;/<a
class="moz-txt-link-freetext" href="soap:Envelope">soap:Envelope</a>&gt;
--------------------------------------
...Eoghan  
      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: Dan Diephouse [<a class="moz-txt-link-freetext" href="mailto:dan.diephouse@mulesource.com">mailto:dan.diephouse@mulesource.com</a>]

Sent: 06 September 2007 16:56
To: <a class="moz-txt-link-abbreviated" href="mailto:cxf-dev@incubator.apache.org">cxf-dev@incubator.apache.org</a>
Subject: WS-Addressing Issues

I'm having some issues getting WS-A to work for me.

    </pre>
    <blockquote type="cite">
      <pre wrap="">INFO: Inbound Message
--------------------------------------
Encoding: UTF-8
Headers: {Host=[localhost:9990], User-Agent=[Java/1.5.0_10],
connection=[keep-alive], SOAPAction=[""],
transfer-encoding=[chunked], Pragma=[no-cache],
content-type=[text/xml; charset=UTF-8],
Cache-Control=[no-cache], Accept=[*]}
Message:
&lt;<a class="moz-txt-link-freetext" href="soap:Envelope">soap:Envelope</a>
xmlns:soap=<a class="moz-txt-link-rfc2396E" href="http://schemas.xmlsoap.org/soap/envelope/">"http://schemas.xmlsoap.org/soap/envelope/"</a>&gt;<a
class="moz-txt-link-rfc2396E" href="soap:Header">&lt;soap:H
eader&gt;</a>&lt;MessageID
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;urn:uuid:9e2a0281
-dcea-42b5-b5a9-a89e265d40de&lt;/MessageID&gt;&lt;To
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;<a
class="moz-txt-link-freetext" href="http://localhost:">http://localhost:</a>
9990/decoupled_endpoint&lt;/To&gt;&lt;RelatesTo
xmlns=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2005/08/addressing">"http://www.w3.org/2005/08/addressing"</a>&gt;urn:uuid:9bd2e4c4
-cca0-478d-bc81-a57e92b9c1c4&lt;/RelatesTo&gt;&lt;/<a class="moz-txt-link-freetext"
href="soap:Header">soap:Header</a>&gt;<a class="moz-txt-link-rfc2396E" href="soap:Body">&lt;soap:Bo
dy&gt;</a>&lt;sayHiResponse
xmlns=<a class="moz-txt-link-rfc2396E" href="http://apache.org/hello_world_soap_http/types">"http://apache.org/hello_world_soap_http/types"</a>&gt;&lt;respons
eType&gt;Bonjour&lt;/responseType&gt;&lt;/sayHiResponse&gt;&lt;/<a
class="moz-txt-link-freetext" href="soap:Body">soap:Body</a>&gt;&lt;/soap

:Envelope&gt;

--------------------------------------


Is this correct? I thought the first http response should be
empty and
we should only be sending the second message.

Last, I'm trying to write a different HTTP conduit and
destination. I.e.
one that uses Mule. I think this issue applies to our JBI
transport as
well. In both the JBI &amp; Mule cases (or any other ESB), you
want to send
messages to the bus instead of to our transport layer. The
bus can then
send out the messages via it's transport layer. The issue is
this - our
decoupled endpoint stuff is baked into the transport, which
it needs to
be rebaked into the Mule/JBI transports as well. Its not
exactly trivial
to do either, I'm still struggling to figure it out. But to expand
my previous points on why decoupling in the transport is a BAD thing
here
are some other reasons:
- Setting up a decoupled endpoint for CXF will be completely
different
depending on whether or not your in an ESB environment or not. In
one case I have to use <a class="moz-txt-link-rfc2396E" href="http:conduit">&lt;http:conduit&gt;</a>
to set the DecoupledEndpoint,
in another &lt;mule:conduit&gt;, in another &lt;jbi:conduit&gt; (which
doesn't support
decoupled interactions right now), etc. It'd be much much
better to have
this configuration associated with the client.
- Now any ESB transport needs to take care of setting the
appropriate HTTP statuses on the messages.
- I have to copy the InteroposedMessageObserver &amp; decoupled
Destination
logic to my conduit
- I'm probably going to end up with a bunch of if(http) logic in my
transport to handle back channel stuff.
Am I missing something here? This seems way harder than it
should be...
Have any of the servicemix people looked at this yet?

Regards,
- Dan

--
Dan Diephouse
MuleSource
<a class="moz-txt-link-freetext" href="http://mulesource.com">http://mulesource.com</a>
| <a class="moz-txt-link-freetext" href="http://netzooid.com/blog">http://netzooid.com/blog</a>
      </pre>
    </blockquote>
    <pre wrap="">----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
Ireland
    </pre>
  </blockquote>
  <pre wrap=""><!---->


  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
Dan Diephouse
MuleSource
<a class="moz-txt-link-freetext" href="http://mulesource.com">http://mulesource.com</a>
| <a class="moz-txt-link-freetext" href="http://netzooid.com/blog">http://netzooid.com/blog</a></pre>
</body>
</html>

Mime
View raw message