Hi, Mike,
I have fixed the DOM transformation issue (TUSCANY-2321) under r656747.
Thanks,
Raymond
--------------------------------------------------
From: "Mike Edwards" <[EMAIL PROTECTED]>
Sent: Wednesday, May 14, 2008 2:07 PM
To: <tuscany-dev@ws.apache.org>
Subject: Re: [jira] Commented: (TUSCANY-2316) Axis2 Binding Provider does
not handle services & references with WSDL interfaces correctly
Scott Kurz wrote:
Oh, I see what I was confused about.
The WebServiceBindingImpl object is not going to have an IC in your case
in
which you simply declare an empty element:
<binding.ws/>
It is in fact, going to set the IC from the component ref/srvc IC. For
some reason I had it in my had that things worked differently, but
now I see why the clone is needed.
Thanks for talking me through that...
Scott
Sorry, Scott, I should have made it clear that when that code executes,
the wsBinding has a null IC - Luciano has explained this clearly now. The
code did not deal with the null IC correctly and this caused the initial
problem here.
As Luciano explained in another thread, there were then 2 other problems
in the data path from the Axis binding to the BPEL process. Luciano fixed
those to enable BPEL over WS-* to work, but I think there are deeper
issues to look at for both those fixes - eg why does the databinding code
generate different DOM trees depending on the path through the code?
Yours, Mike.