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 Andrzej Taramina <an...@chaeron.com> on 2005/11/22 18:08:39 UTC
Compatibility plans?
I'm curious as to how compatible Woden is intended to be from two perspectives?
1) With WSDL4J APIs
2) With regards to supporting WSDL 1.x definitions
Appreciate any insight you can offer...
Thanks.
....Andrzej
Chaeron Corporation
http://www.chaeron.com
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Compatibility plans?
Posted by Arthur Ryman <ar...@gmail.com>.
Andrez,
We will be focusing on getting the WSDL 2.0 through the Candidate
Recommendation stage first. After that we can address WSDL 1.1
compatibility.
-- Arthur
On 11/22/05, John Kaputin <KA...@uk.ibm.com> wrote:
> We have two objectives for supporting WSDL 1.1 in Woden:
>
> The first is to use Woden to read a WSDL 1.1. document and convert it into
> a WSDL 2.0 object model. A couple of people are looking into the conversion
> rules now, using XSL - those rules will be implemented in Woden in some
> form later on.
>
> The second objective is to support the WSDL 1.1 object model of the JSR110
> JWSDL API within Woden (i.e. the javax.wsdl.* interfaces implemented in
> WSDL4J such as Definition, Message, PortType, Binding, etc). So, you could
> use Woden to read a WSDL 1.1 document and return a javax.wsdl.Definition
> object, rather than converting it into a WSDL 2.0 object model. This would
> be similar to use WSDL4J today, except you would be using the Woden's
> factory and reader classes instead of WSDL4J's.
>
> Our immediate focus is completing the WSDL 2.0 functionality - that is,
> reading a WSDL 2.0 document and returning it in a WSDL 2.0 object model.
> Our next milestone is M2 due December 2nd which should deliver parsing of
> <binding> and its child elements and extensions and the validation of the
> <types> and <interface> components (the parsing of these has already been
> completed). M3 due mid January should complete the WSDL 2.0 parsing and
> validation logic.
>
> We will then need to focus on the other objectives - supporting WSDL 2.0
> creation/editing/writing, supporting WSDL 1.1, etc.
>
> John Kaputin
>
>
>
>
> "Andrzej
> Taramina"
> <andrzej@chaeron. To
> com> woden-dev@ws.apache.org
> cc
> 22/11/2005 17:08
> Subject
> Compatibility plans?
> Please respond to
> woden-dev
>
>
>
>
>
>
>
>
> I'm curious as to how compatible Woden is intended to be from two
> perspectives?
>
> 1) With WSDL4J APIs
>
> 2) With regards to supporting WSDL 1.x definitions
>
> Appreciate any insight you can offer...
>
> Thanks.
>
> ....Andrzej
>
> Chaeron Corporation
> http://www.chaeron.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Compatibility plans?
Posted by John Kaputin <KA...@uk.ibm.com>.
We have two objectives for supporting WSDL 1.1 in Woden:
The first is to use Woden to read a WSDL 1.1. document and convert it into
a WSDL 2.0 object model. A couple of people are looking into the conversion
rules now, using XSL - those rules will be implemented in Woden in some
form later on.
The second objective is to support the WSDL 1.1 object model of the JSR110
JWSDL API within Woden (i.e. the javax.wsdl.* interfaces implemented in
WSDL4J such as Definition, Message, PortType, Binding, etc). So, you could
use Woden to read a WSDL 1.1 document and return a javax.wsdl.Definition
object, rather than converting it into a WSDL 2.0 object model. This would
be similar to use WSDL4J today, except you would be using the Woden's
factory and reader classes instead of WSDL4J's.
Our immediate focus is completing the WSDL 2.0 functionality - that is,
reading a WSDL 2.0 document and returning it in a WSDL 2.0 object model.
Our next milestone is M2 due December 2nd which should deliver parsing of
<binding> and its child elements and extensions and the validation of the
<types> and <interface> components (the parsing of these has already been
completed). M3 due mid January should complete the WSDL 2.0 parsing and
validation logic.
We will then need to focus on the other objectives - supporting WSDL 2.0
creation/editing/writing, supporting WSDL 1.1, etc.
John Kaputin
"Andrzej
Taramina"
<andrzej@chaeron. To
com> woden-dev@ws.apache.org
cc
22/11/2005 17:08
Subject
Compatibility plans?
Please respond to
woden-dev
I'm curious as to how compatible Woden is intended to be from two
perspectives?
1) With WSDL4J APIs
2) With regards to supporting WSDL 1.x definitions
Appreciate any insight you can offer...
Thanks.
....Andrzej
Chaeron Corporation
http://www.chaeron.com
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org