You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by John Kaputin <KA...@uk.ibm.com> on 2007/01/16 15:27:19 UTC
Impact of WODEN-120 API change on Axis2 & WSO2
Keith/Dims,
I want to implement WODEN-120 this week but as this involves a change to
the Woden WSDLReader API I want to make sure any dependencies in Axis2 on
Woden SVN trunk are changed at the same time. I notice Axis2 has some
Woden snapshot jars dated in December, but I'm not sure if Axis2 is
dependent on these or on the Woden trunk.
If you are not yet familiar with WODEN-120 you can see the details,
rationale and previous discussion in the JIRA itself, but in short this
JIRA will change the readWSDL methods so that they return a Description
component rather than a DescriptionElement. Note that a deprecation
strategy will not work here as it's only the return type that is changing.
Please let me know whether Axis2 is dependent on Woden trunk and if so, if
we can agree a date to make this change in both Woden and Axis2. I am
proposing Thursday 18th January.
http://issues.apache.org/jira/browse/WODEN-120
thanks,
John Kaputin
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Impact of WODEN-120 API change on Axis2 & WSO2
Posted by Jeremy Hughes <hu...@apache.org>.
On 16/01/07, Davanum Srinivas <da...@gmail.com> wrote:
> John,
>
> Yes, Axis2 trunk works off of woden snapshot. You can go ahead and do
> it at your convenience, no need to wait for Thu. Thanks for the heads
> up. We will fix Axis2 as soon as we see the build break. This would be
> a good test for the automatic notifications that David has set up :)
>
AFAICS it looks like Axis2 is using this Woden snapshot:
http://people.apache.org/repo/m1-snapshot-repository/incubator-woden/jars/
which is dated 12th December. Has the process that updates it
automatically stopped? As things stand I don't think we'll see an
Axis2 build break.
Cheers,
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Impact of WODEN-120 API change on Axis2 & WSO2
Posted by John Kaputin <KA...@uk.ibm.com>.
I have now implemented the API change described in WODEN-120.
Keith,
if your code for the interop testing is dependent on Woden trunk, you will
need to make the simple change described in WODEN-120 to your Woden client
code now. The calls to readWSDL will now return Description instead of
DescriptionElement. Your existing code probably just calls .toComponent()
on the DescriptionElement object straight away to get the Description
component. In this case, you will now get the Description directly from the
readWSDL call. If you do need the Element API, just call .toElement() on
the Description component or any other nested WSDL components.
regards,
John Kaputin
"Davanum
Srinivas"
<davanum@gmail.co To
m> John Kaputin/UK/IBM@IBMGB
cc
16/01/2007 17:05 woden-dev@ws.apache.org,
keithgchapman@gmail.com
Subject
Please respond to Re: Impact of WODEN-120 API change
dims@apache.org on Axis2 & WSO2
John,
Yes, Axis2 trunk works off of woden snapshot. You can go ahead and do
it at your convenience, no need to wait for Thu. Thanks for the heads
up. We will fix Axis2 as soon as we see the build break. This would be
a good test for the automatic notifications that David has set up :)
thanks,
dims
On 1/16/07, John Kaputin <KA...@uk.ibm.com> wrote:
>
> Keith/Dims,
> I want to implement WODEN-120 this week but as this involves a change to
> the Woden WSDLReader API I want to make sure any dependencies in Axis2 on
> Woden SVN trunk are changed at the same time. I notice Axis2 has some
> Woden snapshot jars dated in December, but I'm not sure if Axis2 is
> dependent on these or on the Woden trunk.
>
> If you are not yet familiar with WODEN-120 you can see the details,
> rationale and previous discussion in the JIRA itself, but in short this
> JIRA will change the readWSDL methods so that they return a Description
> component rather than a DescriptionElement. Note that a deprecation
> strategy will not work here as it's only the return type that is
changing.
>
> Please let me know whether Axis2 is dependent on Woden trunk and if so,
if
> we can agree a date to make this change in both Woden and Axis2. I am
> proposing Thursday 18th January.
>
> http://issues.apache.org/jira/browse/WODEN-120
>
> thanks,
> John Kaputin
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Impact of WODEN-120 API change on Axis2 & WSO2
Posted by Davanum Srinivas <da...@gmail.com>.
John,
Yes, Axis2 trunk works off of woden snapshot. You can go ahead and do
it at your convenience, no need to wait for Thu. Thanks for the heads
up. We will fix Axis2 as soon as we see the build break. This would be
a good test for the automatic notifications that David has set up :)
thanks,
dims
On 1/16/07, John Kaputin <KA...@uk.ibm.com> wrote:
>
> Keith/Dims,
> I want to implement WODEN-120 this week but as this involves a change to
> the Woden WSDLReader API I want to make sure any dependencies in Axis2 on
> Woden SVN trunk are changed at the same time. I notice Axis2 has some
> Woden snapshot jars dated in December, but I'm not sure if Axis2 is
> dependent on these or on the Woden trunk.
>
> If you are not yet familiar with WODEN-120 you can see the details,
> rationale and previous discussion in the JIRA itself, but in short this
> JIRA will change the readWSDL methods so that they return a Description
> component rather than a DescriptionElement. Note that a deprecation
> strategy will not work here as it's only the return type that is changing.
>
> Please let me know whether Axis2 is dependent on Woden trunk and if so, if
> we can agree a date to make this change in both Woden and Axis2. I am
> proposing Thursday 18th January.
>
> http://issues.apache.org/jira/browse/WODEN-120
>
> thanks,
> John Kaputin
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org