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 jim ma <ma...@gmail.com> on 2006/03/16 07:13:21 UTC
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
Re: Woden & WSDL 1.1
Posted by Jeremy Hughes <hu...@apache.org>.
Jim,
Please feel free to contribute here. The WSDL4J source contributed by
IBM is here [1].
We should have some discussion around the interfaces we provide for
the WSDL 1.1 object model. The Woden proposal to the incubator [2]
states that "Woden will not be an implementation of JSR110." So we
could just rename the packages from javax.wsdl to
org.apache.woden.wsdl11 (or should that be
org.apache.woden.wsdl11.xml) which would give us one set of interfaces
for manipulating WSDL 1.1 and another set for manipulating WSDL 2.0.
An alternative is to abstract above both models - but really this is
the objective of the WOM in Axis2.
Thoughts?
[1] http://cvs.apache.org/dist/ws/woden/wsdl4j_src.zip
[2] http://incubator.apache.org/woden/proposal.html#Initial+Source
Thx,
Jeremy
On 3/16/06, John Kaputin <KA...@uk.ibm.com> wrote:
> Jim,
> as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
> the project.
>
> There are actually two objectives:
> 1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
> 2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
> Definition object implemented in wsdl4j)
>
> Option 1) will support applications that need a common wsdl model
> regardless of the source document (1.1 or 2.0).
> Option 2) will provide 'native' wsdl 1.1 support for applications that
> currently require it, with a migration path to move to wsdl 2.0.
>
> The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
> 1.1 support in Woden is based on current priorities and available resource.
> Our developer resource to date (2 developers) have only been able to focus
> on the highest priority item, WSDL 2.0 functionality and for the time being
> will continue to do so until the reference implementation is complete. If
> Woden can attract more developers we may be able to expand our scope
> sooner. Contributors can volunteer to work on particular items such as
> WSDL 1.1 support if that is of interest to them.
>
> regards,
> John Kaputin
>
>
>
>
> Arthur Ryman
> <ryman@ca.ibm.com
> > To
> woden-dev@ws.apache.org
> 16/03/2006 14:25 cc
> woden-dev@ws.apache.org
> Subject
> Please respond to Re: Woden & WSDL 1.1
> woden-dev@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
> Jim,
>
> The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
> of the CR stage and become a W3C Recommendation. We are therefore focusing
> on the quality of the WSDL 2.0. We want to identify problems in the spec
> before they become enshrined as part of the standard. So no, both WSDL 1.1
> and WS-I are out of scope for the initial release. However, it is a longer
> term goal to have a single implementation that handles WSDL 1.1 too and
> that is extensible so that other validation rules, like WS-I, can be
> plug-in.
>
> If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
> Tools Tools in WTP at Eclipse.
>
> Arthur Ryman,
> IBM Software Group, Rational Division
>
> blog: http://ryman.eclipsedevelopersjournal.com/
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
>
>
> "jim ma" <ma...@gmail.com>
>
> To
> 03/16/2006 01:13 AM woden-dev@ws.apache.or
> g
> cc
> Please respond to
> woden-dev@ws.apache.org Subject
> Woden & WSDL 1.1
>
>
>
>
>
>
>
>
>
>
>
>
> Hi , all
>
> Just tried woden and I have two qustions about it :
>
> [1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
>
> [2] Does Woden intend to do the validation inculde ws-i basic profile
> conformance ?
>
> Thanks
>
> Jim
>
>
> ---------------------------------------------------------------------
> 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: Woden & WSDL 1.1
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Chathura,
I just replied to a note from Matthew Duffler.
I suggest that WSDL 2.0 is so extensible that we could in fact define a
few extensions that would express the WSDL 1.1 differences. This means
that we could base Axis2 on the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"Chathura Herath" <ch...@gmail.com>
03/17/2006 11:23 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: Woden & WSDL 1.1
Hi,
I could find some time to download and play with woden. It looks
really great. I am working on a woden to WOM builder, which i believe
the Axis2 guys are heading towards.
I am wondering what would be the road map for the woden and WSDL 1.1.
At some point are we planning to implement JWSDL interefaces to the
woden element model or perhaps the component model too, or are we
gonna return two models at the WSDLReader Level. From discussions what
i understood was that it is the general consent to go towards option
1, i.e. to incorporate the WSDL 1.1 capabilities in the woden model
itself.
Actually i tried a toy to implement both the interfaces to woden
element model and got stuck because the method prototypes of the two
interfaces clash sometime.
eg woden
public URI getDocumentBaseURI();
wsdl4j
public String getDocumentBaseURI();
Have you guys looked into this/ is there any work already done in this
regard?? Discussion in this regard before the interface freeze would
help.
Further is there any ideas about how to handle the RPC encoded stuff.
What we right now do in Axis2 is to build a doc style element from the
rpc parts. There was some mention of this problem in Glen's mail too.
Thanks
Chathura
On 3/17/06, Matthew Duftler <du...@us.ibm.com> wrote:
> Hi Guys,
>
> I have some code that can help with a shorter-term solution for option
1.
>
> In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some
Java
> code that can convert a 1.1 document into a 2.0 document.
>
> When I started this project, quite a while ago, I had intended to use
XSLT.
> After working on it for a few days, I decided to abandon the XSLT
effort,
> and switch to a Java-based solution. The utility works by first reading
the
> document into a JWSDL Definition. The advantages of this method over
using
> XSLT are:
>
> - The dereferencing of WSDL elements is basically done already (I say
> basically, because no real validation is being done.)
> - The message pattern of each WSDL 1.1 operation (one-way,
> request-response, solicit-response, notification) is determined by the
> WSDLReader, not the conversion utility.
> - Faster development time (and easier maintenance).
> - It will be easier to modify this code to directly produce the new
WSDL
> 2.0 model, if desired.
>
> The code consists of 2 classes, with a total of about 1500 lines of
code.
> It presently is used as a command-line utility, but does have
entry-points
> that would only require minor modification to code-gen into
> client-specified streams, instead of files. The reason it presently
> produces files is because it attempts to walk the entire Definition
graph
> to convert all imported definitions into WSDL 2.0. This obviously
requires
> multiple output streams.
>
> I can provide some more details if folks are interested. In short, its
only
> major constraint is that it supports solely doc/lit WSDL 1.1 documents.
If
> it encounters a non- doc/lit 1.1 document, it throws an exception. There
is
> a sort-term solution (gen <xsd:any> elements), and a long-term solution
> (generate whatever MEP and associated stuff is appropriate), but I don't
> really have the time to add this logic anymore.
>
> I also wrote a bit of testing code that will attempt to convert entire
> trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
> presently does only schema-validation. This could be easily changed to
use
> Woden to do the validation. I was using this code to ensure proper
coverage
> of the 1.1 specification.
>
> I would probably need a couple of days time to properly integrate it
into
> the codebase, and to add some comments.
>
> At present, I am in limbo with regards to committing anyway. If I read
the
> link that was posted yesterday properly, my Apache id falls into both of
> the following categories:
>
> - I am a committer who has not signed a CLA.
> - I have a signed CLA, but I am not a committer.
>
> I'm not quite sure how both of these things can be true at the same
time,
> but I have signed a new ICLA and I faxed it to Apache yesterday.
>
> Thanks,
> -Matt Duftler
>
>
>
>
> John Kaputin
> <KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
> om> cc:
> Subject: Re: Woden &
WSDL 1.1
> 03/16/2006 11:01
> AM
> Please respond to
> woden-dev
>
>
>
>
>
> Jim,
> as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective
of
> the project.
>
> There are actually two objectives:
> 1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
> 2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
> Definition object implemented in wsdl4j)
>
> Option 1) will support applications that need a common wsdl model
> regardless of the source document (1.1 or 2.0).
> Option 2) will provide 'native' wsdl 1.1 support for applications that
> currently require it, with a migration path to move to wsdl 2.0.
>
> The current focus on WSDL 2.0 compliance and the longer term plan for
wsdl
> 1.1 support in Woden is based on current priorities and available
resource.
> Our developer resource to date (2 developers) have only been able to
focus
> on the highest priority item, WSDL 2.0 functionality and for the time
being
> will continue to do so until the reference implementation is complete.
If
> Woden can attract more developers we may be able to expand our scope
> sooner. Contributors can volunteer to work on particular items such as
> WSDL 1.1 support if that is of interest to them.
>
> regards,
> John Kaputin
>
>
>
>
> Arthur Ryman
> <ryman@ca.ibm.com
> > To
> woden-dev@ws.apache.org
> 16/03/2006 14:25 cc
> woden-dev@ws.apache.org
> Subject
> Please respond to Re: Woden & WSDL 1.1
> woden-dev@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
> Jim,
>
> The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out
> of the CR stage and become a W3C Recommendation. We are therefore
focusing
> on the quality of the WSDL 2.0. We want to identify problems in the spec
> before they become enshrined as part of the standard. So no, both WSDL
1.1
> and WS-I are out of scope for the initial release. However, it is a
longer
> term goal to have a single implementation that handles WSDL 1.1 too and
> that is extensible so that other validation rules, like WS-I, can be
> plug-in.
>
> If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
> Tools Tools in WTP at Eclipse.
>
> Arthur Ryman,
> IBM Software Group, Rational Division
>
> blog: http://ryman.eclipsedevelopersjournal.com/
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
>
>
> "jim ma" <ma...@gmail.com>
>
> To
> 03/16/2006 01:13 AM woden-dev@ws.apache.or
> g
> cc
> Please respond to
> woden-dev@ws.apache.org Subject
> Woden & WSDL 1.1
>
>
>
>
>
>
>
>
>
>
>
>
> Hi , all
>
> Just tried woden and I have two qustions about it :
>
> [1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
>
> [2] Does Woden intend to do the validation inculde ws-i basic profile
> conformance ?
>
> Thanks
>
> Jim
>
>
> ---------------------------------------------------------------------
> 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
>
>
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Chathura,
Sounds like you're making good progress.
The W3C is trying to plan a WSDL 2.0 interop event. Since Axis2 is a major
player, the meeting will be gated by its availability. Any time estimate?
There might be a couple of f2f meetings. The first one would be to plan
the testing, but having some partially working code would be an assert.
Any idea when Axis2 could handle some simple test cases?
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"Chathura Herath" <ch...@gmail.com>
03/23/2006 11:31 PM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: Woden & WSDL 1.1
Hi,
Ok, I am on it and started stipping the WOM out. Give me a lil time to
get it stable and will give an update, probably will do tht on the
axis dev.
First goal to get the codegen to generate code. Which i am working on
now and i am in the process of integrating the woden element component
model.
Code is in my windows box do you think i should branch out in the svn.
Cos we cant do much with most of the wsdls we have till the woden
supports the wsdl 1.1. Further this breaks all the test we have and
need to fix them one by one.
THanks
Chathura
On 3/23/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> Hi Chathura,
>
> > I could find some time to download and play with woden. It looks
> > really great. I am working on a woden to WOM builder, which i believe
> > the Axis2 guys are heading towards.
>
> We're actually going to try to eliminate WOM ASAP. WOM was a temp
> solution as you know and now the runtime works purely off the
> AxisService/AxisOperation/etc. stuff.
>
> Can you write a Woden to Axis* thing? That will make it possible to use
> Woden from Axis2 directly.
>
> Sanjiva.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Jeremy Hughes <hu...@apache.org>.
+1 to a branch (which of course you don't need a vote for anyway).
Then Axis2 baseline isn't disrupted.
Matt Duftler has already mentioned committing a wsdl 1.1->2.0
converter to Woden tool but is having problems with his karma. We can
then work it into Woden to read 1.1 docs and represent them in the
component model and element model as 2.0 docs. Then we should have 1.1
support. There will be some gotchas as the converter doesn't do
everything yet.
Looks like he's on vac until Monday. I'm hoping his karma is fixed and
we can get to looking at the converter code then.
Jeremy
On 3/24/06, Chathura Herath <ch...@gmail.com> wrote:
> Hi,
> Ok, I am on it and started stipping the WOM out. Give me a lil time to
> get it stable and will give an update, probably will do tht on the
> axis dev.
> First goal to get the codegen to generate code. Which i am working on
> now and i am in the process of integrating the woden element component
> model.
> Code is in my windows box do you think i should branch out in the svn.
> Cos we cant do much with most of the wsdls we have till the woden
> supports the wsdl 1.1. Further this breaks all the test we have and
> need to fix them one by one.
>
>
> THanks
> Chathura
>
>
> On 3/23/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> > Hi Chathura,
> >
> > > I could find some time to download and play with woden. It looks
> > > really great. I am working on a woden to WOM builder, which i believe
> > > the Axis2 guys are heading towards.
> >
> > We're actually going to try to eliminate WOM ASAP. WOM was a temp
> > solution as you know and now the runtime works purely off the
> > AxisService/AxisOperation/etc. stuff.
> >
> > Can you write a Woden to Axis* thing? That will make it possible to use
> > Woden from Axis2 directly.
> >
> > Sanjiva.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: woden-dev-help@ws.apache.org
> >
> >
>
>
> --
> Chathura Herath
> http://people.apache.org/~chathura/
> http://chathurah.blogspot.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
Re: Woden & WSDL 1.1
Posted by Chathura Herath <ch...@gmail.com>.
Hi,
Ok, I am on it and started stipping the WOM out. Give me a lil time to
get it stable and will give an update, probably will do tht on the
axis dev.
First goal to get the codegen to generate code. Which i am working on
now and i am in the process of integrating the woden element component
model.
Code is in my windows box do you think i should branch out in the svn.
Cos we cant do much with most of the wsdls we have till the woden
supports the wsdl 1.1. Further this breaks all the test we have and
need to fix them one by one.
THanks
Chathura
On 3/23/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> Hi Chathura,
>
> > I could find some time to download and play with woden. It looks
> > really great. I am working on a woden to WOM builder, which i believe
> > the Axis2 guys are heading towards.
>
> We're actually going to try to eliminate WOM ASAP. WOM was a temp
> solution as you know and now the runtime works purely off the
> AxisService/AxisOperation/etc. stuff.
>
> Can you write a Woden to Axis* thing? That will make it possible to use
> Woden from Axis2 directly.
>
> Sanjiva.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Hi Chathura,
> I could find some time to download and play with woden. It looks
> really great. I am working on a woden to WOM builder, which i believe
> the Axis2 guys are heading towards.
We're actually going to try to eliminate WOM ASAP. WOM was a temp
solution as you know and now the runtime works purely off the
AxisService/AxisOperation/etc. stuff.
Can you write a Woden to Axis* thing? That will make it possible to use
Woden from Axis2 directly.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Chathura Herath <ch...@gmail.com>.
Hi,
I could find some time to download and play with woden. It looks
really great. I am working on a woden to WOM builder, which i believe
the Axis2 guys are heading towards.
I am wondering what would be the road map for the woden and WSDL 1.1.
At some point are we planning to implement JWSDL interefaces to the
woden element model or perhaps the component model too, or are we
gonna return two models at the WSDLReader Level. From discussions what
i understood was that it is the general consent to go towards option
1, i.e. to incorporate the WSDL 1.1 capabilities in the woden model
itself.
Actually i tried a toy to implement both the interfaces to woden
element model and got stuck because the method prototypes of the two
interfaces clash sometime.
eg woden
public URI getDocumentBaseURI();
wsdl4j
public String getDocumentBaseURI();
Have you guys looked into this/ is there any work already done in this
regard?? Discussion in this regard before the interface freeze would
help.
Further is there any ideas about how to handle the RPC encoded stuff.
What we right now do in Axis2 is to build a doc style element from the
rpc parts. There was some mention of this problem in Glen's mail too.
Thanks
Chathura
On 3/17/06, Matthew Duftler <du...@us.ibm.com> wrote:
> Hi Guys,
>
> I have some code that can help with a shorter-term solution for option 1.
>
> In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
> code that can convert a 1.1 document into a 2.0 document.
>
> When I started this project, quite a while ago, I had intended to use XSLT.
> After working on it for a few days, I decided to abandon the XSLT effort,
> and switch to a Java-based solution. The utility works by first reading the
> document into a JWSDL Definition. The advantages of this method over using
> XSLT are:
>
> - The dereferencing of WSDL elements is basically done already (I say
> basically, because no real validation is being done.)
> - The message pattern of each WSDL 1.1 operation (one-way,
> request-response, solicit-response, notification) is determined by the
> WSDLReader, not the conversion utility.
> - Faster development time (and easier maintenance).
> - It will be easier to modify this code to directly produce the new WSDL
> 2.0 model, if desired.
>
> The code consists of 2 classes, with a total of about 1500 lines of code.
> It presently is used as a command-line utility, but does have entry-points
> that would only require minor modification to code-gen into
> client-specified streams, instead of files. The reason it presently
> produces files is because it attempts to walk the entire Definition graph
> to convert all imported definitions into WSDL 2.0. This obviously requires
> multiple output streams.
>
> I can provide some more details if folks are interested. In short, its only
> major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
> it encounters a non- doc/lit 1.1 document, it throws an exception. There is
> a sort-term solution (gen <xsd:any> elements), and a long-term solution
> (generate whatever MEP and associated stuff is appropriate), but I don't
> really have the time to add this logic anymore.
>
> I also wrote a bit of testing code that will attempt to convert entire
> trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
> presently does only schema-validation. This could be easily changed to use
> Woden to do the validation. I was using this code to ensure proper coverage
> of the 1.1 specification.
>
> I would probably need a couple of days time to properly integrate it into
> the codebase, and to add some comments.
>
> At present, I am in limbo with regards to committing anyway. If I read the
> link that was posted yesterday properly, my Apache id falls into both of
> the following categories:
>
> - I am a committer who has not signed a CLA.
> - I have a signed CLA, but I am not a committer.
>
> I'm not quite sure how both of these things can be true at the same time,
> but I have signed a new ICLA and I faxed it to Apache yesterday.
>
> Thanks,
> -Matt Duftler
>
>
>
>
> John Kaputin
> <KAPUTIN@uk.ibm.c To: woden-dev@ws.apache.org
> om> cc:
> Subject: Re: Woden & WSDL 1.1
> 03/16/2006 11:01
> AM
> Please respond to
> woden-dev
>
>
>
>
>
> Jim,
> as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
> the project.
>
> There are actually two objectives:
> 1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
> 2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
> Definition object implemented in wsdl4j)
>
> Option 1) will support applications that need a common wsdl model
> regardless of the source document (1.1 or 2.0).
> Option 2) will provide 'native' wsdl 1.1 support for applications that
> currently require it, with a migration path to move to wsdl 2.0.
>
> The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
> 1.1 support in Woden is based on current priorities and available resource.
> Our developer resource to date (2 developers) have only been able to focus
> on the highest priority item, WSDL 2.0 functionality and for the time being
> will continue to do so until the reference implementation is complete. If
> Woden can attract more developers we may be able to expand our scope
> sooner. Contributors can volunteer to work on particular items such as
> WSDL 1.1 support if that is of interest to them.
>
> regards,
> John Kaputin
>
>
>
>
> Arthur Ryman
> <ryman@ca.ibm.com
> > To
> woden-dev@ws.apache.org
> 16/03/2006 14:25 cc
> woden-dev@ws.apache.org
> Subject
> Please respond to Re: Woden & WSDL 1.1
> woden-dev@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
> Jim,
>
> The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
> of the CR stage and become a W3C Recommendation. We are therefore focusing
> on the quality of the WSDL 2.0. We want to identify problems in the spec
> before they become enshrined as part of the standard. So no, both WSDL 1.1
> and WS-I are out of scope for the initial release. However, it is a longer
> term goal to have a single implementation that handles WSDL 1.1 too and
> that is extensible so that other validation rules, like WS-I, can be
> plug-in.
>
> If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
> Tools Tools in WTP at Eclipse.
>
> Arthur Ryman,
> IBM Software Group, Rational Division
>
> blog: http://ryman.eclipsedevelopersjournal.com/
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
>
>
> "jim ma" <ma...@gmail.com>
>
> To
> 03/16/2006 01:13 AM woden-dev@ws.apache.or
> g
> cc
> Please respond to
> woden-dev@ws.apache.org Subject
> Woden & WSDL 1.1
>
>
>
>
>
>
>
>
>
>
>
>
> Hi , all
>
> Just tried woden and I have two qustions about it :
>
> [1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
>
> [2] Does Woden intend to do the validation inculde ws-i basic profile
> conformance ?
>
> Thanks
>
> Jim
>
>
> ---------------------------------------------------------------------
> 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
>
>
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Thu, 2006-03-23 at 16:45 -0500, Arthur Ryman wrote:
> I've been thinking about how StAX would fit with Woden. There are two
> possible designs:
>
> 1. Woden use StAX to read WSDL 2.0 & XSD, and builds up a complete
> Component Model. There is no DOM in memory but there is a complete
> Component Model in memory.
>
> 2. Woden uses StAX to read WSDL 2.0 & XSD, but does not build up a
> Component Model in memory. Instead, Woden fires a Component Model
> event stream that Axis2 listens to and does whatever is needed. There
> is no Component Model build up in memory here.
>
> What is the requirement from Axis2?
(2) would be ideal from a perf perspective because Axis2 runs off its
own meta model (o.a.axis2.description.Axis* classes). However, (1) would
be ok because then we at least reduce one memory tree for WSDL.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Arthur Ryman <ar...@gmail.com>.
I've been thinking about how StAX would fit with Woden. There are two
possible designs:
1. Woden use StAX to read WSDL 2.0 & XSD, and builds up a complete
Component Model. There is no DOM in memory but there is a complete
Component Model in memory.
2. Woden uses StAX to read WSDL 2.0 & XSD, but does not build up a
Component Model in memory. Instead, Woden fires a Component Model
event stream that Axis2 listens to and does whatever is needed. There
is no Component Model build up in memory here.
What is the requirement from Axis2?
On 3/23/06, Guillaume Nodet <gn...@codehaus.org> wrote:
> Sanjiva Weerawarana wrote:
>
> > I'd love to get off WOM and get onto Woden but we have two key needs to
> > do that: Woden needs to have a StaX (or AXIOM) builder and it must
> > support WSDL 1.1 also.
> >
> >
> WSDL 1.1 is really a need for ServiceMix too, but I guess we will be
> able to keep both wsdl4j and
> woden at the same time until Woden handles WSDL 1.1.
>
> Btw, I 'm wondering about the need for a StaX based Woden parser.
> AFAIK, even WS-Commons
> XMLSchema only supports DOM, and I do not really see the need for a StaX
> based WSDL parser.
> This would of course alleviate the need to build the DOM in memory, but
> apart from that ...
> And having a parser based on AXIOM would imho not be a good idea, as it
> would put a strong
> dependency on AXIOM in the public interfaces.
>
> Cheers,
> Guillaume Nodet
>
>
> ---------------------------------------------------------------------
> 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: Woden & WSDL 1.1
Posted by Guillaume Nodet <gn...@codehaus.org>.
Sanjiva Weerawarana wrote:
> I'd love to get off WOM and get onto Woden but we have two key needs to
> do that: Woden needs to have a StaX (or AXIOM) builder and it must
> support WSDL 1.1 also.
>
>
WSDL 1.1 is really a need for ServiceMix too, but I guess we will be
able to keep both wsdl4j and
woden at the same time until Woden handles WSDL 1.1.
Btw, I 'm wondering about the need for a StaX based Woden parser.
AFAIK, even WS-Commons
XMLSchema only supports DOM, and I do not really see the need for a StaX
based WSDL parser.
This would of course alleviate the need to build the DOM in memory, but
apart from that ...
And having a parser based on AXIOM would imho not be a good idea, as it
would put a strong
dependency on AXIOM in the public interfaces.
Cheers,
Guillaume Nodet
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Matthew Duftler <du...@us.ibm.com>.
Hi Sanjiva,
The converter code generates new files, so there is no need to represent
Schema. The <types> sections are just moved into the new files.
As I haven't worked on converting RPC style 1.1 documents, there hasn't
been any need to read into the Schema.
BTW, I think my priveleges are straightened out. I haven't tried committing
yet, but I can SSH in, and I can checkout the code using SVN.
Thanks,
-Matt
Sanjiva
Weerawarana To: woden-dev@ws.apache.org
<sanjiva@opensour cc:
ce.lk> Subject: Re: Woden & WSDL 1.1
03/20/2006 08:37
PM
Please respond to
woden-dev
Hi Matt!
So immediate question for me: What do you use to deal with XSD? In Axis2
we use the WS-Commons XMLSchema project for this and wish to continue
that (and to see Woden take a dependency on that, which IIRC is the
plan).
BTW we've done something similar to this in Axis2 land. WOM was
originally created because Axis2 runs off a pure WSDL2 like model
internally - all XML schema driven and no built in concept of RPC etc..
We created WOM because we needed a WSDL2 model and one wasn't around.
When Woden started our expectation (hope!) was that they'd take what we
did and go off of that but alas that didn't happen.
Anyway, we now have support for taking many styles of WSDL 1.1 documents
into WOM which means we do the schema wrapping etc. needed to make that
work. If we write a WOM2WSDL2 serializer then we'll have yet another
WSDL1.1 to WSDL2.0 convertor. We should probably do that. (And it should
really be straightforward.)
I'd love to get off WOM and get onto Woden but we have two key needs to
do that: Woden needs to have a StaX (or AXIOM) builder and it must
support WSDL 1.1 also.
Sanjiva.
On Fri, 2006-03-17 at 09:25 -0500, Matthew Duftler wrote:
> Hi Guys,
>
> I have some code that can help with a shorter-term solution for option 1.
>
> In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
> code that can convert a 1.1 document into a 2.0 document.
>
> When I started this project, quite a while ago, I had intended to use
XSLT.
> After working on it for a few days, I decided to abandon the XSLT effort,
> and switch to a Java-based solution. The utility works by first reading
the
> document into a JWSDL Definition. The advantages of this method over
using
> XSLT are:
>
> - The dereferencing of WSDL elements is basically done already (I say
> basically, because no real validation is being done.)
> - The message pattern of each WSDL 1.1 operation (one-way,
> request-response, solicit-response, notification) is determined by the
> WSDLReader, not the conversion utility.
> - Faster development time (and easier maintenance).
> - It will be easier to modify this code to directly produce the new
WSDL
> 2.0 model, if desired.
>
> The code consists of 2 classes, with a total of about 1500 lines of code.
> It presently is used as a command-line utility, but does have
entry-points
> that would only require minor modification to code-gen into
> client-specified streams, instead of files. The reason it presently
> produces files is because it attempts to walk the entire Definition graph
> to convert all imported definitions into WSDL 2.0. This obviously
requires
> multiple output streams.
>
> I can provide some more details if folks are interested. In short, its
only
> major constraint is that it supports solely doc/lit WSDL 1.1 documents.
If
> it encounters a non- doc/lit 1.1 document, it throws an exception. There
is
> a sort-term solution (gen <xsd:any> elements), and a long-term solution
> (generate whatever MEP and associated stuff is appropriate), but I don't
> really have the time to add this logic anymore.
>
> I also wrote a bit of testing code that will attempt to convert entire
> trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
> presently does only schema-validation. This could be easily changed to
use
> Woden to do the validation. I was using this code to ensure proper
coverage
> of the 1.1 specification.
>
> I would probably need a couple of days time to properly integrate it into
> the codebase, and to add some comments.
>
> At present, I am in limbo with regards to committing anyway. If I read
the
> link that was posted yesterday properly, my Apache id falls into both of
> the following categories:
>
> - I am a committer who has not signed a CLA.
> - I have a signed CLA, but I am not a committer.
>
> I'm not quite sure how both of these things can be true at the same time,
> but I have signed a new ICLA and I faxed it to Apache yesterday.
>
> Thanks,
> -Matt Duftler
>
>
>
>
> John Kaputin
> <KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
> om> cc:
> Subject: Re: Woden & WSDL
1.1
> 03/16/2006 11:01
> AM
> Please respond to
> woden-dev
>
>
>
>
>
> Jim,
> as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
> the project.
>
> There are actually two objectives:
> 1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
> 2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
> Definition object implemented in wsdl4j)
>
> Option 1) will support applications that need a common wsdl model
> regardless of the source document (1.1 or 2.0).
> Option 2) will provide 'native' wsdl 1.1 support for applications that
> currently require it, with a migration path to move to wsdl 2.0.
>
> The current focus on WSDL 2.0 compliance and the longer term plan for
wsdl
> 1.1 support in Woden is based on current priorities and available
resource.
> Our developer resource to date (2 developers) have only been able to
focus
> on the highest priority item, WSDL 2.0 functionality and for the time
being
> will continue to do so until the reference implementation is complete.
If
> Woden can attract more developers we may be able to expand our scope
> sooner. Contributors can volunteer to work on particular items such as
> WSDL 1.1 support if that is of interest to them.
>
> regards,
> John Kaputin
>
>
>
>
> Arthur Ryman
> <ryman@ca.ibm.com
> >
To
> woden-dev@ws.apache.org
> 16/03/2006 14:25
cc
> woden-dev@ws.apache.org
>
Subject
> Please respond to Re: Woden & WSDL 1.1
> woden-dev@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
> Jim,
>
> The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out
> of the CR stage and become a W3C Recommendation. We are therefore
focusing
> on the quality of the WSDL 2.0. We want to identify problems in the spec
> before they become enshrined as part of the standard. So no, both WSDL
1.1
> and WS-I are out of scope for the initial release. However, it is a
longer
> term goal to have a single implementation that handles WSDL 1.1 too and
> that is extensible so that other validation rules, like WS-I, can be
> plug-in.
>
> If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
> Tools Tools in WTP at Eclipse.
>
> Arthur Ryman,
> IBM Software Group, Rational Division
>
> blog: http://ryman.eclipsedevelopersjournal.com/
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
>
>
> "jim ma" <ma...@gmail.com>
>
>
To
> 03/16/2006 01:13 AM
woden-dev@ws.apache.or
> g
>
cc
> Please respond to
> woden-dev@ws.apache.org
Subject
> Woden & WSDL 1.1
>
>
>
>
>
>
>
>
>
>
>
>
> Hi , all
>
> Just tried woden and I have two qustions about it :
>
> [1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
>
> [2] Does Woden intend to do the validation inculde ws-i basic profile
> conformance ?
>
> Thanks
>
> Jim
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Hi Matt!
So immediate question for me: What do you use to deal with XSD? In Axis2
we use the WS-Commons XMLSchema project for this and wish to continue
that (and to see Woden take a dependency on that, which IIRC is the
plan).
BTW we've done something similar to this in Axis2 land. WOM was
originally created because Axis2 runs off a pure WSDL2 like model
internally - all XML schema driven and no built in concept of RPC etc..
We created WOM because we needed a WSDL2 model and one wasn't around.
When Woden started our expectation (hope!) was that they'd take what we
did and go off of that but alas that didn't happen.
Anyway, we now have support for taking many styles of WSDL 1.1 documents
into WOM which means we do the schema wrapping etc. needed to make that
work. If we write a WOM2WSDL2 serializer then we'll have yet another
WSDL1.1 to WSDL2.0 convertor. We should probably do that. (And it should
really be straightforward.)
I'd love to get off WOM and get onto Woden but we have two key needs to
do that: Woden needs to have a StaX (or AXIOM) builder and it must
support WSDL 1.1 also.
Sanjiva.
On Fri, 2006-03-17 at 09:25 -0500, Matthew Duftler wrote:
> Hi Guys,
>
> I have some code that can help with a shorter-term solution for option 1.
>
> In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
> code that can convert a 1.1 document into a 2.0 document.
>
> When I started this project, quite a while ago, I had intended to use XSLT.
> After working on it for a few days, I decided to abandon the XSLT effort,
> and switch to a Java-based solution. The utility works by first reading the
> document into a JWSDL Definition. The advantages of this method over using
> XSLT are:
>
> - The dereferencing of WSDL elements is basically done already (I say
> basically, because no real validation is being done.)
> - The message pattern of each WSDL 1.1 operation (one-way,
> request-response, solicit-response, notification) is determined by the
> WSDLReader, not the conversion utility.
> - Faster development time (and easier maintenance).
> - It will be easier to modify this code to directly produce the new WSDL
> 2.0 model, if desired.
>
> The code consists of 2 classes, with a total of about 1500 lines of code.
> It presently is used as a command-line utility, but does have entry-points
> that would only require minor modification to code-gen into
> client-specified streams, instead of files. The reason it presently
> produces files is because it attempts to walk the entire Definition graph
> to convert all imported definitions into WSDL 2.0. This obviously requires
> multiple output streams.
>
> I can provide some more details if folks are interested. In short, its only
> major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
> it encounters a non- doc/lit 1.1 document, it throws an exception. There is
> a sort-term solution (gen <xsd:any> elements), and a long-term solution
> (generate whatever MEP and associated stuff is appropriate), but I don't
> really have the time to add this logic anymore.
>
> I also wrote a bit of testing code that will attempt to convert entire
> trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
> presently does only schema-validation. This could be easily changed to use
> Woden to do the validation. I was using this code to ensure proper coverage
> of the 1.1 specification.
>
> I would probably need a couple of days time to properly integrate it into
> the codebase, and to add some comments.
>
> At present, I am in limbo with regards to committing anyway. If I read the
> link that was posted yesterday properly, my Apache id falls into both of
> the following categories:
>
> - I am a committer who has not signed a CLA.
> - I have a signed CLA, but I am not a committer.
>
> I'm not quite sure how both of these things can be true at the same time,
> but I have signed a new ICLA and I faxed it to Apache yesterday.
>
> Thanks,
> -Matt Duftler
>
>
>
>
> John Kaputin
> <KAPUTIN@uk.ibm.c To: woden-dev@ws.apache.org
> om> cc:
> Subject: Re: Woden & WSDL 1.1
> 03/16/2006 11:01
> AM
> Please respond to
> woden-dev
>
>
>
>
>
> Jim,
> as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
> the project.
>
> There are actually two objectives:
> 1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
> 2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
> Definition object implemented in wsdl4j)
>
> Option 1) will support applications that need a common wsdl model
> regardless of the source document (1.1 or 2.0).
> Option 2) will provide 'native' wsdl 1.1 support for applications that
> currently require it, with a migration path to move to wsdl 2.0.
>
> The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
> 1.1 support in Woden is based on current priorities and available resource.
> Our developer resource to date (2 developers) have only been able to focus
> on the highest priority item, WSDL 2.0 functionality and for the time being
> will continue to do so until the reference implementation is complete. If
> Woden can attract more developers we may be able to expand our scope
> sooner. Contributors can volunteer to work on particular items such as
> WSDL 1.1 support if that is of interest to them.
>
> regards,
> John Kaputin
>
>
>
>
> Arthur Ryman
> <ryman@ca.ibm.com
> > To
> woden-dev@ws.apache.org
> 16/03/2006 14:25 cc
> woden-dev@ws.apache.org
> Subject
> Please respond to Re: Woden & WSDL 1.1
> woden-dev@ws.apac
> he.org
>
>
>
>
>
>
>
>
>
> Jim,
>
> The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
> of the CR stage and become a W3C Recommendation. We are therefore focusing
> on the quality of the WSDL 2.0. We want to identify problems in the spec
> before they become enshrined as part of the standard. So no, both WSDL 1.1
> and WS-I are out of scope for the initial release. However, it is a longer
> term goal to have a single implementation that handles WSDL 1.1 too and
> that is extensible so that other validation rules, like WS-I, can be
> plug-in.
>
> If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
> Tools Tools in WTP at Eclipse.
>
> Arthur Ryman,
> IBM Software Group, Rational Division
>
> blog: http://ryman.eclipsedevelopersjournal.com/
> phone: +1-905-413-3077, TL 969-3077
> assistant: +1-905-413-2411, TL 969-2411
> fax: +1-905-413-4920, TL 969-4920
> mobile: +1-416-939-5063, text: 4169395063@fido.ca
>
>
> "jim ma" <ma...@gmail.com>
>
> To
> 03/16/2006 01:13 AM woden-dev@ws.apache.or
> g
> cc
> Please respond to
> woden-dev@ws.apache.org Subject
> Woden & WSDL 1.1
>
>
>
>
>
>
>
>
>
>
>
>
> Hi , all
>
> Just tried woden and I have two qustions about it :
>
> [1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
>
> [2] Does Woden intend to do the validation inculde ws-i basic profile
> conformance ?
>
> Thanks
>
> Jim
>
>
> ---------------------------------------------------------------------
> 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: Woden & WSDL 1.1
Posted by Matthew Duftler <du...@us.ibm.com>.
Hi Lawrence,
>1. Aside from being written in Java, how does your conversion tool differ
from the one offered by the W3C [1]? Have you done a comparison?
I haven't done a comparison. My intuition is the coverage will be quite
similar. I believe they generate xsd:any by way of supporting non doc/lit
style documents.
>2. You said that you've written "a bit of testing code". How much is a
bit? Although we're currently short on test cases, Woden needs to be very
well tested. >Can you beef up the test suite and will you be able to
integrate it into the existing Woden test suite (JUnit)?
It is not a test suite. It is some code that is used from an Ant task to
convert batches of WSDL 1.1 files and then Schema-validate them (while
counting numbers of errors and the like). The best way to enhance it would
probably be to change the validation step to use Woden to validate the
output instead of just a validating DOM parser. I can make this change. I
don't see any reason why it can't be integrated into the existing Woden
test suite.
> To the matter at hand, are you a WS committer and will you be able to
maintain your contribution to Woden?
I see that I have commit priveleges to ws-all, but I don't see ws-woden
listed. Do you know what I need to do to ensure I have proper commit
priveleges?
My current schedule will allow me to apply bug fixes and make minor
changes, but I won't be able to make any large-scale changes.
Thanks,
-Matt
Lawrence Mandel
<lmandel@ca.ibm.c To: woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL 1.1
03/17/2006 12:16
PM
Please respond to
woden-dev
Matt,
A conversion utility in Woden will definitely be useful and may help us
solve some of the Axis integration issues we're currently discussing. A few
questions:
1. Aside from being written in Java, how does your conversion tool differ
from the one offered by the W3C [1]? Have you done a comparison?
2. You said that you've written "a bit of testing code". How much is a bit?
Although we're currently short on test cases, Woden needs to be very well
tested. Can you beef up the test suite and will you be able to integrate it
into the existing Woden test suite (JUnit)?
3. So somehow you're both a committer who has not signed a CLA and you
have a signed CLA, but are not a committer. Interesting. To the matter at
hand, are you a WS committer and will you be able to maintain your
contribution to Woden?
[1] http://www.w3.org/2006/02/WSDLConvert.html
Thanks,
Lawrence Mandel
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 09:25 AM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
Matt,
A conversion utility in Woden will definitely be useful and may help us
solve some of the Axis integration issues we're currently discussing. A
few questions:
1. Aside from being written in Java, how does your conversion tool differ
from the one offered by the W3C [1]? Have you done a comparison?
2. You said that you've written "a bit of testing code". How much is a
bit? Although we're currently short on test cases, Woden needs to be very
well tested. Can you beef up the test suite and will you be able to
integrate it into the existing Woden test suite (JUnit)?
3. So somehow you're both a committer who has not signed a CLA and you
have a signed CLA, but are not a committer. Interesting. To the matter at
hand, are you a WS committer and will you be able to maintain your
contribution to Woden?
[1] http://www.w3.org/2006/02/WSDLConvert.html
Thanks,
Lawrence Mandel
Matthew Duftler <du...@us.ibm.com>
03/17/2006 09:25 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use
XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading
the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its
only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There
is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper
coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To: woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available
resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time
being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by John Kaputin <KA...@uk.ibm.com>.
Hi Matt,
+1 for contributing this to Woden as soon as you can so we can investigate
adapting it for our wsdl1.1 support in Woden. If you are going to commit it
to SVN I think best to create a new folder under the /java folder, say
/java/converter or something suitable.
John Kaputin
Matthew Duftler
<duftler@us.ibm.c
om> To
woden-dev@ws.apache.org
17/03/2006 14:25 cc
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Matt,
Axis2 needs to continue to support WSDL 1.1. Simply migrating all the old
WSDL 1.1 to WSDL 2.0 isn't a solution because the installed base of tools,
runtimes, etc. currently uses WSDL 1.1, including things like RPC/Enc that
are not part of the WSDL 2.0 Core spec.
We want to get a WSDL 2.0 implementation asap to help get the spec out of
CR status. The quickest way to do this is to integrate Woden into Axis2.
The Axis2 team wants a single object model. Currently they use WOM. We
believe Woden can replace WOM.
However, for Woden to replace WOM, it would need to support WSDL 1.1.
There is a big intersection between WSDL 1.1 and WSDL 2.0 so it is
feasible to serialize WSDL 1.1 documents from the Woden component model
(CM). However, there are feautres of WSDL 1.1 that were left out of the
WSDL 2.0 spec, e.g. RPC/Enc. WSDL 2.0 is highly extensible so it should be
possible to define WSDL 2.0 extensions to capture the missing features of
WSDL 1.1. This would effectively let you imbed WSDL 1.1 in WSDL 2.0.
To sum up, Woden CM could replace WOM and support both WSDL 2.0 and 1.1 if
we define a few extensions.
The conversion tool is still very interesting for migration and as a way
to generate WSDL 2.0 test cases.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
04/04/2006 11:18 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: Woden & WSDL 1.1
Hi Art,
So you are basically saying for Axis to use the Woden Component Model as a
replacement for the WOM, Woden needs to be able to round-trip both WSDL
1.1
and 2.0 (and also do whatever 1.1 <-> 2.0 conversions are possible).
If (for certain cases, like RPC/ENC) Axis has to learn how to navigate
newly-defined 2.0 extensions, how is that different from just navigating
JWSDL for those cases?
I guess the thing for the Woden community to decide is whether this
converter code will fulfill requirements that others have (like simply
converting 1.1 to 2.0, without regard to roundtripping).
My view is that this converter code can go a long way towards helping
Woden
support WSDL 1.1 (even if this code is just used temporarily).
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To: woden-dev@ws.apache.org
> cc: woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
04/01/2006 11:54
AM
Please respond to
woden-dev
Matt,
My suggestion is not for the converter. It's for using the WSDL 2.0
Component Model as a replacement for the WOM in Axis2. At present, there
are a lot of things in WSDL 1.1 that can't be expressed in WSDL 2.0 as you
have enumerated in your work on the converter. However, there is a huge
area of overlap so most of WSDL 1.1 can be expressed in terms of the
Component Model. To express the others, extensions are needed, e.g. for
rpc/encoded.
The goal is to use the Woden Component Model as the internal
representation
for WSDL in Axis2 and to be able to serialize it as both WSDL 2.0 or WSDL
1.1. Any component model instance could be serialized as WSDL 2.0 using
the
extensions. A subset of instances could also be serialized as WSDL 1.1.
This means that Axis2 can still support "legacy" WSDL 1.1 documents via
Woden. Otherwise, Axis2 would need 2 models.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/31/2006 04:37 PM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Art,
Sorry for taking a while to respond to this; I'm playing a bit of email
catchup.
I'm not quite sure I see why adding the ability to convert 1.1 documents
into 2.0 requires new extensions (I haven't really thought much about
supporting rpc-type WSDL 1.1 docs, though).
>Further to me previous note, we'd need WSDL 2.0 extensions to capture
most
of these differences.
Why does Woden need to capture most of these differences? As long as the
conversion/mapping from 1.1 to 2.0 is reasonable and public, why would you
need to maintain the original representation? Actually, if you are going
to
define extensions to represent all the original 1.1 semantics, why
wouldn't
you just wrap the entire original 1.1 syntax, and use that as a 2.0
extension? Either way, you need to navigate an additional representation,
no?
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To:
woden-dev@ws.apache.org
> cc:
woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 05:34
PM
Please respond to
woden-dev
Matt,
Nice list. I think the W3C once started a document that outlined all the
differences. I don't rememeber what happened to it, but I think it would
be
a very useful thing to have.
Further to me previous note, we'd need WSDL 2.0 extensions to capture most
of these differences.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 04:45 PM woden-dev@ws.apache.
org
cc
Please respond to woden-dev@ws.apache.
woden-dev@ws.apache.org org
Subject
Re: Woden & WSDL 1.1
Hi Arthur,
>The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
im>plement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0, you'd have to split up a <wsdl11:service> into several
<wsdl20:service> >elements. However, we should preserve the relation
between these split up services so we can generate the same WSDL 1.1
again.
This could also be >handled with an extension.
In the course of creating the conversion code I came across quite a few
constructs that are handled differently in 1.1 vs 2.0. I created a short
list with some notes of how I handled the issues:
Definition of service components:
- In 1.1, <service>s can have multiple <port>s, with each <port> bound to
a
different <portType>.
- In 2.0, <service>s are bound to one <interface>.
- Notes: If a service is encountered that has ports bound to more than one
portType, a service is generated for each referenced portType. Each newly
generated service has the suffix "_n" appended to its name, with n
increasing from 1 until the name is unique.
Overloading of operation names:
- In 1.1, <operation> names are permitted to be overloaded. When referring
to overloaded <operation>s from <binding>s, <operation>s are uniquely
identified by using the names of the <input> and <output> elements in
addition to the name of the <operation>.
- In 2.0, <operation> names must be unique within an <interface>.
- Notes: Any operation name found to be overloaded has the suffix "_n"
appended to it, with n increasing from 1 until the name is unique.
targetNamespace requirements:
- In 1.1, the targetNamespace attribute of <definition> is optional; if it
is not specified, all references to items defined within the document must
be done without prefixes, and the default namespace must be set to "".
Also, if no targetNamespace is specified, no top-level items defined
within
the document can be referred to from other WSDL documents.
- In 2.0, the targetNamespace attribute of <description> is required.
- Notes: There is a -targetNS command-line argument that allows the user
to
specify the targetNamespace to be used. If the source 1.1 document does
not
specify a targetNamespace, this argument is required; if the source 1.1
document does specify a targetNamespace, the argument serves as an
optional
way to override the specified targetNamespace. The targetNamespace
replacement will propagate via a generated include, but not via a
generated
import.
Ordering of top-level elements:
- In 1.1, the children of <definition> may appear in any order (even
though
the schema says otherwise).
- In 2.0, the order is strictly defined.
- Notes: This is not a problem since the JWSDL's WSDLReader is flexible
w.r.t the order of the source WSDL 1.1 document, and we output the WSDL
2.0
document in the proper order.
Definition of faults:
- In 1.1, faults are defined directly within operations, and the name of a
fault must be unique within the enclosing operation.
- In 2.0, faults are defined within interfaces, and referred to from
within
operations; fault names must be unique within the enclosing interface.
- Notes: Any fault name found to be ambiguous (when moved directly under
the interface) has the suffix "_n" appended to it, with n increasing from
1
until the name is unique. If more than 1 fault refer to the same element
type, the definitions are merged.
Imports:
- In 1.1, it is permitted to import documents that are from the same
targetNamespace as the importing document, as well as documents that are
not.
- In 2.0, import can only be used to import documents that are from a
different targetNamespace than the document doing the importing. The
include element can be used to import documents that are from the same
targetNamespace.
- Notes: If the imported document has the same targetNamespace as the
importing document, an include is generated; otherwise, an import is
generated.
Support for soapAction:
- In 1.1, there is a soapAction attribute defined on the extensibility
element <soap:operation>, which is a child of BindingOperation.
- In 2.0, there is a wsoap:action attribute defined directly on the
BindingOperation.
- Notes: During conversion, the value is copied directly from the
soapAction attribute to the wsoap:action attribute.
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To:
woden-dev@ws.apache.org
> cc:
woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 11:30
AM
Please respond to
woden-dev
Matthew,
This sounds like a great first step towards unifying WSDL 1.1 and WSDL
2.0.
We need to decide on the internal model that Axis2 will use. We could
either enhance WOM to support WSDL 2.0, or enhance Woden to support WSDL
1.1.
The way to enhance WSDL 2.0 to support WSDL 1.1 is via extensions. Would
you be able to define a WSDL 2.0 extension to support rpc/enc? I see that
as the major obstacle to adopting the Woden component model for Axis2
since
there are so many legacy rpc/enc services. WSDL 2.0 is highly extensible
so
this should be feasible. This is essentially a new binding. For
completeness, we need to support all combos of rpc and doc with encoding
and literal.
The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
implement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0,
you'd have to split up a <wsdl11:service> into several <wsdl20:service>
elements. However, we should preserve the relation between these split up
services so we can generate the same WSDL 1.1 again. This could also be
handled with an extension.
By extensions I mean a new set of elements and attributes in a new
namespace, placed in appropriate positions, together with a specification
of their meaning and affect on the component model. See WSDL 2.0 Part 2
[1]
for examples.
You would then have to morph your code so that it constructed extended
WSDL
2.0 documents and we'd also need the extension handlers so they could add
the extensions to the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 09:25 AM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use
XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading
the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its
only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There
is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper
coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available
resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time
being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by Matthew Duftler <du...@us.ibm.com>.
Hi Art,
So you are basically saying for Axis to use the Woden Component Model as a
replacement for the WOM, Woden needs to be able to round-trip both WSDL 1.1
and 2.0 (and also do whatever 1.1 <-> 2.0 conversions are possible).
If (for certain cases, like RPC/ENC) Axis has to learn how to navigate
newly-defined 2.0 extensions, how is that different from just navigating
JWSDL for those cases?
I guess the thing for the Woden community to decide is whether this
converter code will fulfill requirements that others have (like simply
converting 1.1 to 2.0, without regard to roundtripping).
My view is that this converter code can go a long way towards helping Woden
support WSDL 1.1 (even if this code is just used temporarily).
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To: woden-dev@ws.apache.org
> cc: woden-dev@ws.apache.org
Subject: Re: Woden & WSDL 1.1
04/01/2006 11:54
AM
Please respond to
woden-dev
Matt,
My suggestion is not for the converter. It's for using the WSDL 2.0
Component Model as a replacement for the WOM in Axis2. At present, there
are a lot of things in WSDL 1.1 that can't be expressed in WSDL 2.0 as you
have enumerated in your work on the converter. However, there is a huge
area of overlap so most of WSDL 1.1 can be expressed in terms of the
Component Model. To express the others, extensions are needed, e.g. for
rpc/encoded.
The goal is to use the Woden Component Model as the internal representation
for WSDL in Axis2 and to be able to serialize it as both WSDL 2.0 or WSDL
1.1. Any component model instance could be serialized as WSDL 2.0 using the
extensions. A subset of instances could also be serialized as WSDL 1.1.
This means that Axis2 can still support "legacy" WSDL 1.1 documents via
Woden. Otherwise, Axis2 would need 2 models.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/31/2006 04:37 PM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Art,
Sorry for taking a while to respond to this; I'm playing a bit of email
catchup.
I'm not quite sure I see why adding the ability to convert 1.1 documents
into 2.0 requires new extensions (I haven't really thought much about
supporting rpc-type WSDL 1.1 docs, though).
>Further to me previous note, we'd need WSDL 2.0 extensions to capture most
of these differences.
Why does Woden need to capture most of these differences? As long as the
conversion/mapping from 1.1 to 2.0 is reasonable and public, why would you
need to maintain the original representation? Actually, if you are going to
define extensions to represent all the original 1.1 semantics, why wouldn't
you just wrap the entire original 1.1 syntax, and use that as a 2.0
extension? Either way, you need to navigate an additional representation,
no?
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To:
woden-dev@ws.apache.org
> cc:
woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 05:34
PM
Please respond to
woden-dev
Matt,
Nice list. I think the W3C once started a document that outlined all the
differences. I don't rememeber what happened to it, but I think it would be
a very useful thing to have.
Further to me previous note, we'd need WSDL 2.0 extensions to capture most
of these differences.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 04:45 PM woden-dev@ws.apache.
org
cc
Please respond to woden-dev@ws.apache.
woden-dev@ws.apache.org org
Subject
Re: Woden & WSDL 1.1
Hi Arthur,
>The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
im>plement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0, you'd have to split up a <wsdl11:service> into several
<wsdl20:service> >elements. However, we should preserve the relation
between these split up services so we can generate the same WSDL 1.1 again.
This could also be >handled with an extension.
In the course of creating the conversion code I came across quite a few
constructs that are handled differently in 1.1 vs 2.0. I created a short
list with some notes of how I handled the issues:
Definition of service components:
- In 1.1, <service>s can have multiple <port>s, with each <port> bound to a
different <portType>.
- In 2.0, <service>s are bound to one <interface>.
- Notes: If a service is encountered that has ports bound to more than one
portType, a service is generated for each referenced portType. Each newly
generated service has the suffix "_n" appended to its name, with n
increasing from 1 until the name is unique.
Overloading of operation names:
- In 1.1, <operation> names are permitted to be overloaded. When referring
to overloaded <operation>s from <binding>s, <operation>s are uniquely
identified by using the names of the <input> and <output> elements in
addition to the name of the <operation>.
- In 2.0, <operation> names must be unique within an <interface>.
- Notes: Any operation name found to be overloaded has the suffix "_n"
appended to it, with n increasing from 1 until the name is unique.
targetNamespace requirements:
- In 1.1, the targetNamespace attribute of <definition> is optional; if it
is not specified, all references to items defined within the document must
be done without prefixes, and the default namespace must be set to "".
Also, if no targetNamespace is specified, no top-level items defined within
the document can be referred to from other WSDL documents.
- In 2.0, the targetNamespace attribute of <description> is required.
- Notes: There is a -targetNS command-line argument that allows the user to
specify the targetNamespace to be used. If the source 1.1 document does not
specify a targetNamespace, this argument is required; if the source 1.1
document does specify a targetNamespace, the argument serves as an optional
way to override the specified targetNamespace. The targetNamespace
replacement will propagate via a generated include, but not via a generated
import.
Ordering of top-level elements:
- In 1.1, the children of <definition> may appear in any order (even though
the schema says otherwise).
- In 2.0, the order is strictly defined.
- Notes: This is not a problem since the JWSDL's WSDLReader is flexible
w.r.t the order of the source WSDL 1.1 document, and we output the WSDL 2.0
document in the proper order.
Definition of faults:
- In 1.1, faults are defined directly within operations, and the name of a
fault must be unique within the enclosing operation.
- In 2.0, faults are defined within interfaces, and referred to from within
operations; fault names must be unique within the enclosing interface.
- Notes: Any fault name found to be ambiguous (when moved directly under
the interface) has the suffix "_n" appended to it, with n increasing from 1
until the name is unique. If more than 1 fault refer to the same element
type, the definitions are merged.
Imports:
- In 1.1, it is permitted to import documents that are from the same
targetNamespace as the importing document, as well as documents that are
not.
- In 2.0, import can only be used to import documents that are from a
different targetNamespace than the document doing the importing. The
include element can be used to import documents that are from the same
targetNamespace.
- Notes: If the imported document has the same targetNamespace as the
importing document, an include is generated; otherwise, an import is
generated.
Support for soapAction:
- In 1.1, there is a soapAction attribute defined on the extensibility
element <soap:operation>, which is a child of BindingOperation.
- In 2.0, there is a wsoap:action attribute defined directly on the
BindingOperation.
- Notes: During conversion, the value is copied directly from the
soapAction attribute to the wsoap:action attribute.
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To:
woden-dev@ws.apache.org
> cc:
woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 11:30
AM
Please respond to
woden-dev
Matthew,
This sounds like a great first step towards unifying WSDL 1.1 and WSDL 2.0.
We need to decide on the internal model that Axis2 will use. We could
either enhance WOM to support WSDL 2.0, or enhance Woden to support WSDL
1.1.
The way to enhance WSDL 2.0 to support WSDL 1.1 is via extensions. Would
you be able to define a WSDL 2.0 extension to support rpc/enc? I see that
as the major obstacle to adopting the Woden component model for Axis2 since
there are so many legacy rpc/enc services. WSDL 2.0 is highly extensible so
this should be feasible. This is essentially a new binding. For
completeness, we need to support all combos of rpc and doc with encoding
and literal.
The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
implement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL 2.0,
you'd have to split up a <wsdl11:service> into several <wsdl20:service>
elements. However, we should preserve the relation between these split up
services so we can generate the same WSDL 1.1 again. This could also be
handled with an extension.
By extensions I mean a new set of elements and attributes in a new
namespace, placed in appropriate positions, together with a specification
of their meaning and affect on the component model. See WSDL 2.0 Part 2 [1]
for examples.
You would then have to morph your code so that it constructed extended WSDL
2.0 documents and we'd also need the extension handlers so they could add
the extensions to the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 09:25 AM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Matt,
My suggestion is not for the converter. It's for using the WSDL 2.0
Component Model as a replacement for the WOM in Axis2. At present, there
are a lot of things in WSDL 1.1 that can't be expressed in WSDL 2.0 as you
have enumerated in your work on the converter. However, there is a huge
area of overlap so most of WSDL 1.1 can be expressed in terms of the
Component Model. To express the others, extensions are needed, e.g. for
rpc/encoded.
The goal is to use the Woden Component Model as the internal
representation for WSDL in Axis2 and to be able to serialize it as both
WSDL 2.0 or WSDL 1.1. Any component model instance could be serialized as
WSDL 2.0 using the extensions. A subset of instances could also be
serialized as WSDL 1.1.
This means that Axis2 can still support "legacy" WSDL 1.1 documents via
Woden. Otherwise, Axis2 would need 2 models.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
03/31/2006 04:37 PM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: Woden & WSDL 1.1
Hi Art,
Sorry for taking a while to respond to this; I'm playing a bit of email
catchup.
I'm not quite sure I see why adding the ability to convert 1.1 documents
into 2.0 requires new extensions (I haven't really thought much about
supporting rpc-type WSDL 1.1 docs, though).
>Further to me previous note, we'd need WSDL 2.0 extensions to capture
most
of these differences.
Why does Woden need to capture most of these differences? As long as the
conversion/mapping from 1.1 to 2.0 is reasonable and public, why would you
need to maintain the original representation? Actually, if you are going
to
define extensions to represent all the original 1.1 semantics, why
wouldn't
you just wrap the entire original 1.1 syntax, and use that as a 2.0
extension? Either way, you need to navigate an additional representation,
no?
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To: woden-dev@ws.apache.org
> cc: woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 05:34
PM
Please respond to
woden-dev
Matt,
Nice list. I think the W3C once started a document that outlined all the
differences. I don't rememeber what happened to it, but I think it would
be
a very useful thing to have.
Further to me previous note, we'd need WSDL 2.0 extensions to capture most
of these differences.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 04:45 PM woden-dev@ws.apache.
org
cc
Please respond to woden-dev@ws.apache.
woden-dev@ws.apache.org org
Subject
Re: Woden & WSDL 1.1
Hi Arthur,
>The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
im>plement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0, you'd have to split up a <wsdl11:service> into several
<wsdl20:service> >elements. However, we should preserve the relation
between these split up services so we can generate the same WSDL 1.1
again.
This could also be >handled with an extension.
In the course of creating the conversion code I came across quite a few
constructs that are handled differently in 1.1 vs 2.0. I created a short
list with some notes of how I handled the issues:
Definition of service components:
- In 1.1, <service>s can have multiple <port>s, with each <port> bound to
a
different <portType>.
- In 2.0, <service>s are bound to one <interface>.
- Notes: If a service is encountered that has ports bound to more than one
portType, a service is generated for each referenced portType. Each newly
generated service has the suffix "_n" appended to its name, with n
increasing from 1 until the name is unique.
Overloading of operation names:
- In 1.1, <operation> names are permitted to be overloaded. When referring
to overloaded <operation>s from <binding>s, <operation>s are uniquely
identified by using the names of the <input> and <output> elements in
addition to the name of the <operation>.
- In 2.0, <operation> names must be unique within an <interface>.
- Notes: Any operation name found to be overloaded has the suffix "_n"
appended to it, with n increasing from 1 until the name is unique.
targetNamespace requirements:
- In 1.1, the targetNamespace attribute of <definition> is optional; if it
is not specified, all references to items defined within the document must
be done without prefixes, and the default namespace must be set to "".
Also, if no targetNamespace is specified, no top-level items defined
within
the document can be referred to from other WSDL documents.
- In 2.0, the targetNamespace attribute of <description> is required.
- Notes: There is a -targetNS command-line argument that allows the user
to
specify the targetNamespace to be used. If the source 1.1 document does
not
specify a targetNamespace, this argument is required; if the source 1.1
document does specify a targetNamespace, the argument serves as an
optional
way to override the specified targetNamespace. The targetNamespace
replacement will propagate via a generated include, but not via a
generated
import.
Ordering of top-level elements:
- In 1.1, the children of <definition> may appear in any order (even
though
the schema says otherwise).
- In 2.0, the order is strictly defined.
- Notes: This is not a problem since the JWSDL's WSDLReader is flexible
w.r.t the order of the source WSDL 1.1 document, and we output the WSDL
2.0
document in the proper order.
Definition of faults:
- In 1.1, faults are defined directly within operations, and the name of a
fault must be unique within the enclosing operation.
- In 2.0, faults are defined within interfaces, and referred to from
within
operations; fault names must be unique within the enclosing interface.
- Notes: Any fault name found to be ambiguous (when moved directly under
the interface) has the suffix "_n" appended to it, with n increasing from
1
until the name is unique. If more than 1 fault refer to the same element
type, the definitions are merged.
Imports:
- In 1.1, it is permitted to import documents that are from the same
targetNamespace as the importing document, as well as documents that are
not.
- In 2.0, import can only be used to import documents that are from a
different targetNamespace than the document doing the importing. The
include element can be used to import documents that are from the same
targetNamespace.
- Notes: If the imported document has the same targetNamespace as the
importing document, an include is generated; otherwise, an import is
generated.
Support for soapAction:
- In 1.1, there is a soapAction attribute defined on the extensibility
element <soap:operation>, which is a child of BindingOperation.
- In 2.0, there is a wsoap:action attribute defined directly on the
BindingOperation.
- Notes: During conversion, the value is copied directly from the
soapAction attribute to the wsoap:action attribute.
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To:
woden-dev@ws.apache.org
> cc:
woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 11:30
AM
Please respond to
woden-dev
Matthew,
This sounds like a great first step towards unifying WSDL 1.1 and WSDL
2.0.
We need to decide on the internal model that Axis2 will use. We could
either enhance WOM to support WSDL 2.0, or enhance Woden to support WSDL
1.1.
The way to enhance WSDL 2.0 to support WSDL 1.1 is via extensions. Would
you be able to define a WSDL 2.0 extension to support rpc/enc? I see that
as the major obstacle to adopting the Woden component model for Axis2
since
there are so many legacy rpc/enc services. WSDL 2.0 is highly extensible
so
this should be feasible. This is essentially a new binding. For
completeness, we need to support all combos of rpc and doc with encoding
and literal.
The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
implement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0,
you'd have to split up a <wsdl11:service> into several <wsdl20:service>
elements. However, we should preserve the relation between these split up
services so we can generate the same WSDL 1.1 again. This could also be
handled with an extension.
By extensions I mean a new set of elements and attributes in a new
namespace, placed in appropriate positions, together with a specification
of their meaning and affect on the component model. See WSDL 2.0 Part 2
[1]
for examples.
You would then have to morph your code so that it constructed extended
WSDL
2.0 documents and we'd also need the extension handlers so they could add
the extensions to the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 09:25 AM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use
XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading
the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its
only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There
is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper
coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available
resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time
being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Matthew Duftler <du...@us.ibm.com>.
Hi Art,
Sorry for taking a while to respond to this; I'm playing a bit of email
catchup.
I'm not quite sure I see why adding the ability to convert 1.1 documents
into 2.0 requires new extensions (I haven't really thought much about
supporting rpc-type WSDL 1.1 docs, though).
>Further to me previous note, we'd need WSDL 2.0 extensions to capture most
of these differences.
Why does Woden need to capture most of these differences? As long as the
conversion/mapping from 1.1 to 2.0 is reasonable and public, why would you
need to maintain the original representation? Actually, if you are going to
define extensions to represent all the original 1.1 semantics, why wouldn't
you just wrap the entire original 1.1 syntax, and use that as a 2.0
extension? Either way, you need to navigate an additional representation,
no?
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To: woden-dev@ws.apache.org
> cc: woden-dev@ws.apache.org
Subject: Re: Woden & WSDL 1.1
03/17/2006 05:34
PM
Please respond to
woden-dev
Matt,
Nice list. I think the W3C once started a document that outlined all the
differences. I don't rememeber what happened to it, but I think it would be
a very useful thing to have.
Further to me previous note, we'd need WSDL 2.0 extensions to capture most
of these differences.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 04:45 PM woden-dev@ws.apache.
org
cc
Please respond to woden-dev@ws.apache.
woden-dev@ws.apache.org org
Subject
Re: Woden & WSDL 1.1
Hi Arthur,
>The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
im>plement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0, you'd have to split up a <wsdl11:service> into several
<wsdl20:service> >elements. However, we should preserve the relation
between these split up services so we can generate the same WSDL 1.1 again.
This could also be >handled with an extension.
In the course of creating the conversion code I came across quite a few
constructs that are handled differently in 1.1 vs 2.0. I created a short
list with some notes of how I handled the issues:
Definition of service components:
- In 1.1, <service>s can have multiple <port>s, with each <port> bound to a
different <portType>.
- In 2.0, <service>s are bound to one <interface>.
- Notes: If a service is encountered that has ports bound to more than one
portType, a service is generated for each referenced portType. Each newly
generated service has the suffix "_n" appended to its name, with n
increasing from 1 until the name is unique.
Overloading of operation names:
- In 1.1, <operation> names are permitted to be overloaded. When referring
to overloaded <operation>s from <binding>s, <operation>s are uniquely
identified by using the names of the <input> and <output> elements in
addition to the name of the <operation>.
- In 2.0, <operation> names must be unique within an <interface>.
- Notes: Any operation name found to be overloaded has the suffix "_n"
appended to it, with n increasing from 1 until the name is unique.
targetNamespace requirements:
- In 1.1, the targetNamespace attribute of <definition> is optional; if it
is not specified, all references to items defined within the document must
be done without prefixes, and the default namespace must be set to "".
Also, if no targetNamespace is specified, no top-level items defined within
the document can be referred to from other WSDL documents.
- In 2.0, the targetNamespace attribute of <description> is required.
- Notes: There is a -targetNS command-line argument that allows the user to
specify the targetNamespace to be used. If the source 1.1 document does not
specify a targetNamespace, this argument is required; if the source 1.1
document does specify a targetNamespace, the argument serves as an optional
way to override the specified targetNamespace. The targetNamespace
replacement will propagate via a generated include, but not via a generated
import.
Ordering of top-level elements:
- In 1.1, the children of <definition> may appear in any order (even though
the schema says otherwise).
- In 2.0, the order is strictly defined.
- Notes: This is not a problem since the JWSDL's WSDLReader is flexible
w.r.t the order of the source WSDL 1.1 document, and we output the WSDL 2.0
document in the proper order.
Definition of faults:
- In 1.1, faults are defined directly within operations, and the name of a
fault must be unique within the enclosing operation.
- In 2.0, faults are defined within interfaces, and referred to from within
operations; fault names must be unique within the enclosing interface.
- Notes: Any fault name found to be ambiguous (when moved directly under
the interface) has the suffix "_n" appended to it, with n increasing from 1
until the name is unique. If more than 1 fault refer to the same element
type, the definitions are merged.
Imports:
- In 1.1, it is permitted to import documents that are from the same
targetNamespace as the importing document, as well as documents that are
not.
- In 2.0, import can only be used to import documents that are from a
different targetNamespace than the document doing the importing. The
include element can be used to import documents that are from the same
targetNamespace.
- Notes: If the imported document has the same targetNamespace as the
importing document, an include is generated; otherwise, an import is
generated.
Support for soapAction:
- In 1.1, there is a soapAction attribute defined on the extensibility
element <soap:operation>, which is a child of BindingOperation.
- In 2.0, there is a wsoap:action attribute defined directly on the
BindingOperation.
- Notes: During conversion, the value is copied directly from the
soapAction attribute to the wsoap:action attribute.
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To:
woden-dev@ws.apache.org
> cc:
woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 11:30
AM
Please respond to
woden-dev
Matthew,
This sounds like a great first step towards unifying WSDL 1.1 and WSDL 2.0.
We need to decide on the internal model that Axis2 will use. We could
either enhance WOM to support WSDL 2.0, or enhance Woden to support WSDL
1.1.
The way to enhance WSDL 2.0 to support WSDL 1.1 is via extensions. Would
you be able to define a WSDL 2.0 extension to support rpc/enc? I see that
as the major obstacle to adopting the Woden component model for Axis2 since
there are so many legacy rpc/enc services. WSDL 2.0 is highly extensible so
this should be feasible. This is essentially a new binding. For
completeness, we need to support all combos of rpc and doc with encoding
and literal.
The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
implement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL 2.0,
you'd have to split up a <wsdl11:service> into several <wsdl20:service>
elements. However, we should preserve the relation between these split up
services so we can generate the same WSDL 1.1 again. This could also be
handled with an extension.
By extensions I mean a new set of elements and attributes in a new
namespace, placed in appropriate positions, together with a specification
of their meaning and affect on the component model. See WSDL 2.0 Part 2 [1]
for examples.
You would then have to morph your code so that it constructed extended WSDL
2.0 documents and we'd also need the extension handlers so they could add
the extensions to the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 09:25 AM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Matt,
Nice list. I think the W3C once started a document that outlined all the
differences. I don't rememeber what happened to it, but I think it would
be a very useful thing to have.
Further to me previous note, we'd need WSDL 2.0 extensions to capture most
of these differences.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
03/17/2006 04:45 PM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
woden-dev@ws.apache.org
Subject
Re: Woden & WSDL 1.1
Hi Arthur,
>The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
im>plement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0, you'd have to split up a <wsdl11:service> into several
<wsdl20:service> >elements. However, we should preserve the relation
between these split up services so we can generate the same WSDL 1.1
again.
This could also be >handled with an extension.
In the course of creating the conversion code I came across quite a few
constructs that are handled differently in 1.1 vs 2.0. I created a short
list with some notes of how I handled the issues:
Definition of service components:
- In 1.1, <service>s can have multiple <port>s, with each <port> bound to
a
different <portType>.
- In 2.0, <service>s are bound to one <interface>.
- Notes: If a service is encountered that has ports bound to more than one
portType, a service is generated for each referenced portType. Each newly
generated service has the suffix "_n" appended to its name, with n
increasing from 1 until the name is unique.
Overloading of operation names:
- In 1.1, <operation> names are permitted to be overloaded. When referring
to overloaded <operation>s from <binding>s, <operation>s are uniquely
identified by using the names of the <input> and <output> elements in
addition to the name of the <operation>.
- In 2.0, <operation> names must be unique within an <interface>.
- Notes: Any operation name found to be overloaded has the suffix "_n"
appended to it, with n increasing from 1 until the name is unique.
targetNamespace requirements:
- In 1.1, the targetNamespace attribute of <definition> is optional; if it
is not specified, all references to items defined within the document must
be done without prefixes, and the default namespace must be set to "".
Also, if no targetNamespace is specified, no top-level items defined
within
the document can be referred to from other WSDL documents.
- In 2.0, the targetNamespace attribute of <description> is required.
- Notes: There is a -targetNS command-line argument that allows the user
to
specify the targetNamespace to be used. If the source 1.1 document does
not
specify a targetNamespace, this argument is required; if the source 1.1
document does specify a targetNamespace, the argument serves as an
optional
way to override the specified targetNamespace. The targetNamespace
replacement will propagate via a generated include, but not via a
generated
import.
Ordering of top-level elements:
- In 1.1, the children of <definition> may appear in any order (even
though
the schema says otherwise).
- In 2.0, the order is strictly defined.
- Notes: This is not a problem since the JWSDL's WSDLReader is flexible
w.r.t the order of the source WSDL 1.1 document, and we output the WSDL
2.0
document in the proper order.
Definition of faults:
- In 1.1, faults are defined directly within operations, and the name of a
fault must be unique within the enclosing operation.
- In 2.0, faults are defined within interfaces, and referred to from
within
operations; fault names must be unique within the enclosing interface.
- Notes: Any fault name found to be ambiguous (when moved directly under
the interface) has the suffix "_n" appended to it, with n increasing from
1
until the name is unique. If more than 1 fault refer to the same element
type, the definitions are merged.
Imports:
- In 1.1, it is permitted to import documents that are from the same
targetNamespace as the importing document, as well as documents that are
not.
- In 2.0, import can only be used to import documents that are from a
different targetNamespace than the document doing the importing. The
include element can be used to import documents that are from the same
targetNamespace.
- Notes: If the imported document has the same targetNamespace as the
importing document, an include is generated; otherwise, an import is
generated.
Support for soapAction:
- In 1.1, there is a soapAction attribute defined on the extensibility
element <soap:operation>, which is a child of BindingOperation.
- In 2.0, there is a wsoap:action attribute defined directly on the
BindingOperation.
- Notes: During conversion, the value is copied directly from the
soapAction attribute to the wsoap:action attribute.
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To: woden-dev@ws.apache.org
> cc: woden-dev@ws.apache.org
Subject: Re: Woden & WSDL
1.1
03/17/2006 11:30
AM
Please respond to
woden-dev
Matthew,
This sounds like a great first step towards unifying WSDL 1.1 and WSDL
2.0.
We need to decide on the internal model that Axis2 will use. We could
either enhance WOM to support WSDL 2.0, or enhance Woden to support WSDL
1.1.
The way to enhance WSDL 2.0 to support WSDL 1.1 is via extensions. Would
you be able to define a WSDL 2.0 extension to support rpc/enc? I see that
as the major obstacle to adopting the Woden component model for Axis2
since
there are so many legacy rpc/enc services. WSDL 2.0 is highly extensible
so
this should be feasible. This is essentially a new binding. For
completeness, we need to support all combos of rpc and doc with encoding
and literal.
The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
implement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0,
you'd have to split up a <wsdl11:service> into several <wsdl20:service>
elements. However, we should preserve the relation between these split up
services so we can generate the same WSDL 1.1 again. This could also be
handled with an extension.
By extensions I mean a new set of elements and attributes in a new
namespace, placed in appropriate positions, together with a specification
of their meaning and affect on the component model. See WSDL 2.0 Part 2
[1]
for examples.
You would then have to morph your code so that it constructed extended
WSDL
2.0 documents and we'd also need the extension handlers so they could add
the extensions to the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 09:25 AM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use
XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading
the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its
only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There
is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper
coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available
resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time
being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by Matthew Duftler <du...@us.ibm.com>.
Hi Arthur,
>The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
im>plement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0, you'd have to split up a <wsdl11:service> into several
<wsdl20:service> >elements. However, we should preserve the relation
between these split up services so we can generate the same WSDL 1.1 again.
This could also be >handled with an extension.
In the course of creating the conversion code I came across quite a few
constructs that are handled differently in 1.1 vs 2.0. I created a short
list with some notes of how I handled the issues:
Definition of service components:
- In 1.1, <service>s can have multiple <port>s, with each <port> bound to a
different <portType>.
- In 2.0, <service>s are bound to one <interface>.
- Notes: If a service is encountered that has ports bound to more than one
portType, a service is generated for each referenced portType. Each newly
generated service has the suffix "_n" appended to its name, with n
increasing from 1 until the name is unique.
Overloading of operation names:
- In 1.1, <operation> names are permitted to be overloaded. When referring
to overloaded <operation>s from <binding>s, <operation>s are uniquely
identified by using the names of the <input> and <output> elements in
addition to the name of the <operation>.
- In 2.0, <operation> names must be unique within an <interface>.
- Notes: Any operation name found to be overloaded has the suffix "_n"
appended to it, with n increasing from 1 until the name is unique.
targetNamespace requirements:
- In 1.1, the targetNamespace attribute of <definition> is optional; if it
is not specified, all references to items defined within the document must
be done without prefixes, and the default namespace must be set to "".
Also, if no targetNamespace is specified, no top-level items defined within
the document can be referred to from other WSDL documents.
- In 2.0, the targetNamespace attribute of <description> is required.
- Notes: There is a -targetNS command-line argument that allows the user to
specify the targetNamespace to be used. If the source 1.1 document does not
specify a targetNamespace, this argument is required; if the source 1.1
document does specify a targetNamespace, the argument serves as an optional
way to override the specified targetNamespace. The targetNamespace
replacement will propagate via a generated include, but not via a generated
import.
Ordering of top-level elements:
- In 1.1, the children of <definition> may appear in any order (even though
the schema says otherwise).
- In 2.0, the order is strictly defined.
- Notes: This is not a problem since the JWSDL's WSDLReader is flexible
w.r.t the order of the source WSDL 1.1 document, and we output the WSDL 2.0
document in the proper order.
Definition of faults:
- In 1.1, faults are defined directly within operations, and the name of a
fault must be unique within the enclosing operation.
- In 2.0, faults are defined within interfaces, and referred to from within
operations; fault names must be unique within the enclosing interface.
- Notes: Any fault name found to be ambiguous (when moved directly under
the interface) has the suffix "_n" appended to it, with n increasing from 1
until the name is unique. If more than 1 fault refer to the same element
type, the definitions are merged.
Imports:
- In 1.1, it is permitted to import documents that are from the same
targetNamespace as the importing document, as well as documents that are
not.
- In 2.0, import can only be used to import documents that are from a
different targetNamespace than the document doing the importing. The
include element can be used to import documents that are from the same
targetNamespace.
- Notes: If the imported document has the same targetNamespace as the
importing document, an include is generated; otherwise, an import is
generated.
Support for soapAction:
- In 1.1, there is a soapAction attribute defined on the extensibility
element <soap:operation>, which is a child of BindingOperation.
- In 2.0, there is a wsoap:action attribute defined directly on the
BindingOperation.
- Notes: During conversion, the value is copied directly from the
soapAction attribute to the wsoap:action attribute.
Thanks,
-Matt
Arthur Ryman
<ryman@ca.ibm.com To: woden-dev@ws.apache.org
> cc: woden-dev@ws.apache.org
Subject: Re: Woden & WSDL 1.1
03/17/2006 11:30
AM
Please respond to
woden-dev
Matthew,
This sounds like a great first step towards unifying WSDL 1.1 and WSDL 2.0.
We need to decide on the internal model that Axis2 will use. We could
either enhance WOM to support WSDL 2.0, or enhance Woden to support WSDL
1.1.
The way to enhance WSDL 2.0 to support WSDL 1.1 is via extensions. Would
you be able to define a WSDL 2.0 extension to support rpc/enc? I see that
as the major obstacle to adopting the Woden component model for Axis2 since
there are so many legacy rpc/enc services. WSDL 2.0 is highly extensible so
this should be feasible. This is essentially a new binding. For
completeness, we need to support all combos of rpc and doc with encoding
and literal.
The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
implement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL 2.0,
you'd have to split up a <wsdl11:service> into several <wsdl20:service>
elements. However, we should preserve the relation between these split up
services so we can generate the same WSDL 1.1 again. This could also be
handled with an extension.
By extensions I mean a new set of elements and attributes in a new
namespace, placed in appropriate positions, together with a specification
of their meaning and affect on the component model. See WSDL 2.0 Part 2 [1]
for examples.
You would then have to morph your code so that it constructed extended WSDL
2.0 documents and we'd also need the extension handlers so they could add
the extensions to the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
To
03/17/2006 09:25 AM woden-dev@ws.apache.
org
cc
Please respond to
woden-dev@ws.apache.org Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To:
woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Matthew,
This sounds like a great first step towards unifying WSDL 1.1 and WSDL
2.0.
We need to decide on the internal model that Axis2 will use. We could
either enhance WOM to support WSDL 2.0, or enhance Woden to support WSDL
1.1.
The way to enhance WSDL 2.0 to support WSDL 1.1 is via extensions. Would
you be able to define a WSDL 2.0 extension to support rpc/enc? I see that
as the major obstacle to adopting the Woden component model for Axis2
since there are so many legacy rpc/enc services. WSDL 2.0 is highly
extensible so this should be feasible. This is essentially a new binding.
For completeness, we need to support all combos of rpc and doc with
encoding and literal.
The other main mismatch is that a WSDL 2.0 <service> implements a single
<interface>. In WSDL 1.1, a service can contain endpoints ( <port>'s) that
implement arbitrary interfaces (<portType>'s). To map WSDL 1.1 to WSDL
2.0, you'd have to split up a <wsdl11:service> into several
<wsdl20:service> elements. However, we should preserve the relation
between these split up services so we can generate the same WSDL 1.1
again. This could also be handled with an extension.
By extensions I mean a new set of elements and attributes in a new
namespace, placed in appropriate positions, together with a specification
of their meaning and affect on the component model. See WSDL 2.0 Part 2
[1] for examples.
You would then have to morph your code so that it constructed extended
WSDL 2.0 documents and we'd also need the extension handlers so they could
add the extensions to the Woden component model.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Matthew Duftler <du...@us.ibm.com>
03/17/2006 09:25 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: Woden & WSDL 1.1
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use
XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading
the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its
only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There
is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper
coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To: woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL
1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available
resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time
being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by Matthew Duftler <du...@us.ibm.com>.
Hi Guys,
I have some code that can help with a shorter-term solution for option 1.
In the course of comparing WSDL 2.0 with WSDL 1.1, I've written some Java
code that can convert a 1.1 document into a 2.0 document.
When I started this project, quite a while ago, I had intended to use XSLT.
After working on it for a few days, I decided to abandon the XSLT effort,
and switch to a Java-based solution. The utility works by first reading the
document into a JWSDL Definition. The advantages of this method over using
XSLT are:
- The dereferencing of WSDL elements is basically done already (I say
basically, because no real validation is being done.)
- The message pattern of each WSDL 1.1 operation (one-way,
request-response, solicit-response, notification) is determined by the
WSDLReader, not the conversion utility.
- Faster development time (and easier maintenance).
- It will be easier to modify this code to directly produce the new WSDL
2.0 model, if desired.
The code consists of 2 classes, with a total of about 1500 lines of code.
It presently is used as a command-line utility, but does have entry-points
that would only require minor modification to code-gen into
client-specified streams, instead of files. The reason it presently
produces files is because it attempts to walk the entire Definition graph
to convert all imported definitions into WSDL 2.0. This obviously requires
multiple output streams.
I can provide some more details if folks are interested. In short, its only
major constraint is that it supports solely doc/lit WSDL 1.1 documents. If
it encounters a non- doc/lit 1.1 document, it throws an exception. There is
a sort-term solution (gen <xsd:any> elements), and a long-term solution
(generate whatever MEP and associated stuff is appropriate), but I don't
really have the time to add this logic anymore.
I also wrote a bit of testing code that will attempt to convert entire
trees of WSDL 1.1 documents into WSDL 2.0, and then validate them. It
presently does only schema-validation. This could be easily changed to use
Woden to do the validation. I was using this code to ensure proper coverage
of the 1.1 specification.
I would probably need a couple of days time to properly integrate it into
the codebase, and to add some comments.
At present, I am in limbo with regards to committing anyway. If I read the
link that was posted yesterday properly, my Apache id falls into both of
the following categories:
- I am a committer who has not signed a CLA.
- I have a signed CLA, but I am not a committer.
I'm not quite sure how both of these things can be true at the same time,
but I have signed a new ICLA and I faxed it to Apache yesterday.
Thanks,
-Matt Duftler
John Kaputin
<KAPUTIN@uk.ibm.c To: woden-dev@ws.apache.org
om> cc:
Subject: Re: Woden & WSDL 1.1
03/16/2006 11:01
AM
Please respond to
woden-dev
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
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: Woden & WSDL 1.1
Posted by John Kaputin <KA...@uk.ibm.com>.
Jim,
as Arthur mentions, WSDL 1.1 support in Woden is an ultimate objective of
the project.
There are actually two objectives:
1) converting a wsdl 1.1 document into the WSDL 2.0 component model.
2) converting a wsdl 1.1 document into a WSDL 1.1 object model (e.g. the
Definition object implemented in wsdl4j)
Option 1) will support applications that need a common wsdl model
regardless of the source document (1.1 or 2.0).
Option 2) will provide 'native' wsdl 1.1 support for applications that
currently require it, with a migration path to move to wsdl 2.0.
The current focus on WSDL 2.0 compliance and the longer term plan for wsdl
1.1 support in Woden is based on current priorities and available resource.
Our developer resource to date (2 developers) have only been able to focus
on the highest priority item, WSDL 2.0 functionality and for the time being
will continue to do so until the reference implementation is complete. If
Woden can attract more developers we may be able to expand our scope
sooner. Contributors can volunteer to work on particular items such as
WSDL 1.1 support if that is of interest to them.
regards,
John Kaputin
Arthur Ryman
<ryman@ca.ibm.com
> To
woden-dev@ws.apache.org
16/03/2006 14:25 cc
woden-dev@ws.apache.org
Subject
Please respond to Re: Woden & WSDL 1.1
woden-dev@ws.apac
he.org
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification out
of the CR stage and become a W3C Recommendation. We are therefore focusing
on the quality of the WSDL 2.0. We want to identify problems in the spec
before they become enshrined as part of the standard. So no, both WSDL 1.1
and WS-I are out of scope for the initial release. However, it is a longer
term goal to have a single implementation that handles WSDL 1.1 too and
that is extensible so that other validation rules, like WS-I, can be
plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
To
03/16/2006 01:13 AM woden-dev@ws.apache.or
g
cc
Please respond to
woden-dev@ws.apache.org Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Woden & WSDL 1.1
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Jim,
The initial goal of Woden 1.0 is to help get the WSDL 2.0 specification
out of the CR stage and become a W3C Recommendation. We are therefore
focusing on the quality of the WSDL 2.0. We want to identify problems in
the spec before they become enshrined as part of the standard. So no, both
WSDL 1.1 and WS-I are out of scope for the initial release. However, it is
a longer term goal to have a single implementation that handles WSDL 1.1
too and that is extensible so that other validation rules, like WS-I, can
be plug-in.
If you need WSDL 1.1 and WS-I support, use WSDL4J at Apache and the WS-I
Tools Tools in WTP at Eclipse.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
"jim ma" <ma...@gmail.com>
03/16/2006 01:13 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Woden & WSDL 1.1
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile
conformance ?
Thanks
Jim