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 Graham Turrell <GT...@uk.ibm.com> on 2006/09/11 18:29:13 UTC
[WODEN-USER :)] how to access xsi:schemaLocation attribute of from
either parser?
Hi List,
Here's a "WODEN-USER" type posting :)
I've been rummaging around for some time trying to find out how to access
the xsi:schemaLocation attribute via the API, in the following parsed
fragment of WSDL2:
<description targetNamespace="http://example.com/bank"
xmlns="http://www.w3.org/2006/01/wsdl"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=
"http://www.w3.org/2006/01/wsdl
http://www.w3.org/2006/01/wsdl/wsdl20.xsd
http://www.w3.org/2001/XMLSchema
http://www.w3.org/2001/XMLSchema.xsd" >
Can anyone tell me how this should be done, at least in theory?
(As far as parsing is concerned, I can see that
parseExtensionAttributes(...) is intended to do that,
though the method is a TODO in the OM parser, and in the DOM parser
http://www.w3.org/2001/XMLSchema-instance is explicitly excluded from being
parsed).
Thanks in advance.
Kind Regards,
Graham.
_____________________________________________
Graham C Turrell CEng, MBCS
Chartered IT Practitioner
WebSphere ESB Foundation Technologies
DE3F16 / MP 211
IBM Labs
Hursley Park
Winchester, Hampshire
England. SO21 2JN
Tel +44-(0)1962-815018
email: gturrell@uk.ibm.com
"No army can withstand the force of an idea whose time
has come.". -Victor Hugo
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of from either parser?
Posted by Jeremy Hughes <hu...@apache.org>.
OK fair point.
Jeremy
On 9/12/06, Arthur Ryman <ry...@ca.ibm.com> wrote:
>
>
> I think the xsi attributes shown be handled as built-in since they are
> part of XSD. The extension mechanism should be reserved for WSDL extensions.
>
> 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
>
>
> *"Jeremy Hughes" <hu...@apache.org>*
> Sent by: jpjhughes@gmail.com
>
> 09/12/2006 04:57 AM Please respond to
> woden-dev@ws.apache.org
>
> To
> woden-dev@ws.apache.org, oshanis@gmail.com cc
>
> Subject
> Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of
> <description> from either parser?
>
>
>
>
>
>
> I think this should be handled like any other extension. Anything not
> in the WSDL namespace is an extension to the WSDL. If we start
> 'special-casing' extensions then we could find other extensions would
> like to do the same.
>
> Jeremy
>
> On 9/12/06, Oshani Seneviratne <os...@gmail.com> wrote:
> > Hi Graham and all,
> >
> > Even in the DOMWSDLReader, I assume that parseExtensionAttributes
> > method was not intended to handle this. I'm referring to the comment
> > "//TODO handle xsi attrs elsewhere, without need to register". (Please
> > correct me if I'm wrong on this! )
> >
> > So, theoretically as you asked, how about having a method like
> > parseExtensionAttributeSchema (or whatever the name) which gets called
> > from the parseExtensionAttributes? We could also have a schema
> > implementation like ExtensionAttributeSchema that could represent such
> > external schemas. (Or maybe ImportedSchema could be used here).
> > Any comments?
> >
> > Also, just to clarify, in the WSDL fragment you've given there are 2
> > schema locations for 1 attribute. Is that possible?
> >
> > > <description targetNamespace="http://example.com/bank"
> > > xmlns="http://www.w3.org/2006/01/wsdl"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > > xsi:schemaLocation=
> > > "http://www.w3.org/2006/01/wsdl
> > > http://www.w3.org/2006/01/wsdl/wsdl20.xsd
> > > http://www.w3.org/2001/XMLSchema
> > > http://www.w3.org/2001/XMLSchema.xsd" >
> > >
> >
> > Thanks and Regards,
> > Oshani
> >
> > ---------------------------------------------------------------------
> > 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-USER :)] how to access xsi:schemaLocation attribute of from either parser?
Posted by Oshani Seneviratne <os...@gmail.com>.
Hi Arthur,
Thanks for the clarification and I guess your explanation answers the
original question in this thread.
You asked: "Do you need it at parse time? "
Well, I guess we need it as an extension attribute and nothing more. So, it
would be okay have the same treatment for it as any other extension
attribute.
As you suggested we could implement getXsiSchemaLocation() from
DescriptionElement and leave it upto the client app to decide what to do
with the schema representation. (I was initially of the opinion that Woden
should take care of the schema too.)
Thanks,
Oshani.
On 9/13/06, Arthur Ryman < ryman@ca.ibm.com > wrote:
>
>
> Oshani,
>
> I mean that it should NOT be treated as a WSDL extension. It should be a
> well-typed part of the interface, e.g. on the DocumentElement, maybe
> getXsiSchemaLocation() and return an array of URIs. However, it depends on
> what you want to do with it. Do you need it at parse time?
>
> 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
>
>
> *"Oshani Seneviratne" <os...@gmail.com>*
>
> 09/12/2006 02:41 PM Please respond to
> oshanis@gmail.com
>
> To
> Arthur Ryman/Toronto/IBM@IBMCA cc
> woden-dev@ws.apache.org, jpjhughes@gmail.com
> Subject
> Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of
> <description> from either parser?
>
>
>
>
>
>
> Hi Arthur,
>
> I am trying to figure out how to implement this with OM. So, could you
> please explain what you meant by "handled as built-in"? Is it having
> another XMLAttr impl, or another representation of schema in woden (similar
> to inline/imported schema)?
>
> Thanks,
> Oshani
>
> On 9/12/06, *Arthur Ryman* <*ryman@ca.ibm.com* <ry...@ca.ibm.com>> wrote:
>
> I think the xsi attributes shown be handled as built-in since they are
> part of XSD. The extension mechanism should be reserved for WSDL extensions.
>
> Arthur Ryman,
> IBM Software Group, Rational Division
>
> blog: *http://ryman.eclipsedevelopersjournal.com/ *<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* <41...@fido.ca>
>
> *"Jeremy Hughes" <**hughesj@apache.org* <hu...@apache.org> *>*
> Sent by: *jpjhughes@gmail.com* <jp...@gmail.com>
>
> 09/12/2006 04:57 AM
> Please respond to*
> **woden-dev@ws.apache.org* <wo...@ws.apache.org>
>
>
> To
> *woden-dev@ws.apache.org* <wo...@ws.apache.org> , *oshanis@gmail.com*<os...@gmail.com>
> cc
>
> Subject
> Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of
> <description> from either parser?
>
>
>
>
>
>
>
>
> I think this should be handled like any other extension. Anything not
> in the WSDL namespace is an extension to the WSDL. If we start
> 'special-casing' extensions then we could find other extensions would
> like to do the same.
>
> Jeremy
>
> On 9/12/06, Oshani Seneviratne <*oshanis@gmail.com* <os...@gmail.com>>
> wrote:
> > Hi Graham and all,
> >
> > Even in the DOMWSDLReader, I assume that parseExtensionAttributes
> > method was not intended to handle this. I'm referring to the comment
> > "//TODO handle xsi attrs elsewhere, without need to register". (Please
> > correct me if I'm wrong on this! )
> >
> > So, theoretically as you asked, how about having a method like
> > parseExtensionAttributeSchema (or whatever the name) which gets called
> > from the parseExtensionAttributes? We could also have a schema
> > implementation like ExtensionAttributeSchema that could represent such
> > external schemas. (Or maybe ImportedSchema could be used here).
> > Any comments?
> >
> > Also, just to clarify, in the WSDL fragment you've given there are 2
> > schema locations for 1 attribute. Is that possible?
> >
> > > <description targetNamespace="*http://example.com/bank *<http://example.com/bank>
> "
> > > xmlns="*http://www.w3.org/2006/01/wsdl *<http://www.w3.org/2006/01/wsdl>
> "
> > > xmlns:xsi="*http://www.w3.org/2001/XMLSchema-instance *<http://www.w3.org/2001/XMLSchema-instance>
> "
> > > xsi:schemaLocation=
> > > "*http://www.w3.org/2006/01/wsdl*<http://www.w3.org/2006/01/wsdl>
> > > *http://www.w3.org/2006/01/wsdl/wsdl20.xsd *<http://www.w3.org/2006/01/wsdl/wsdl20.xsd>
> > > *http://www.w3.org/2001/XMLSchema*<http://www.w3.org/2001/XMLSchema>
> > > *http://www.w3.org/2001/XMLSchema.xsd*
> <http://www.w3.org/2001/XMLSchema.xsd>" >
> > >
> >
> > Thanks and Regards,
> > Oshani
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: *woden-dev-unsubscribe@ws.apache.org *<wo...@ws.apache.org>
> > For additional commands, e-mail: *woden-dev-help@ws.apache.org *<wo...@ws.apache.org>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: *woden-dev-unsubscribe@ws.apache.org *<wo...@ws.apache.org>
> For additional commands, e-mail: *woden-dev-help@ws.apache.org *<wo...@ws.apache.org>
>
>
>
>
>
Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of from
either parser?
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Oshani,
I mean that it should NOT be treated as a WSDL extension. It should be a
well-typed part of the interface, e.g. on the DocumentElement, maybe
getXsiSchemaLocation() and return an array of URIs. However, it depends on
what you want to do with it. Do you need it at parse time?
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
"Oshani Seneviratne" <os...@gmail.com>
09/12/2006 02:41 PM
Please respond to
oshanis@gmail.com
To
Arthur Ryman/Toronto/IBM@IBMCA
cc
woden-dev@ws.apache.org, jpjhughes@gmail.com
Subject
Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of
<description> from either parser?
Hi Arthur,
I am trying to figure out how to implement this with OM. So, could you
please explain what you meant by "handled as built-in"? Is it having
another XMLAttr impl, or another representation of schema in woden
(similar to inline/imported schema)?
Thanks,
Oshani
On 9/12/06, Arthur Ryman <ry...@ca.ibm.com> wrote:
I think the xsi attributes shown be handled as built-in since they are
part of XSD. The extension mechanism should be reserved for WSDL
extensions.
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
"Jeremy Hughes" <hu...@apache.org>
Sent by: jpjhughes@gmail.com
09/12/2006 04:57 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org, oshanis@gmail.com
cc
Subject
Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of
<description> from either parser?
I think this should be handled like any other extension. Anything not
in the WSDL namespace is an extension to the WSDL. If we start
'special-casing' extensions then we could find other extensions would
like to do the same.
Jeremy
On 9/12/06, Oshani Seneviratne <os...@gmail.com> wrote:
> Hi Graham and all,
>
> Even in the DOMWSDLReader, I assume that parseExtensionAttributes
> method was not intended to handle this. I'm referring to the comment
> "//TODO handle xsi attrs elsewhere, without need to register". (Please
> correct me if I'm wrong on this! )
>
> So, theoretically as you asked, how about having a method like
> parseExtensionAttributeSchema (or whatever the name) which gets called
> from the parseExtensionAttributes? We could also have a schema
> implementation like ExtensionAttributeSchema that could represent such
> external schemas. (Or maybe ImportedSchema could be used here).
> Any comments?
>
> Also, just to clarify, in the WSDL fragment you've given there are 2
> schema locations for 1 attribute. Is that possible?
>
> > <description targetNamespace="http://example.com/bank"
> > xmlns="http://www.w3.org/2006/01/wsdl"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation=
> > "http://www.w3.org/2006/01/wsdl
> > http://www.w3.org/2006/01/wsdl/wsdl20.xsd
> > http://www.w3.org/2001/XMLSchema
> > http://www.w3.org/2001/XMLSchema.xsd" >
> >
>
> Thanks and Regards,
> Oshani
>
> ---------------------------------------------------------------------
> 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-USER :)] how to access xsi:schemaLocation attribute of from either parser?
Posted by Oshani Seneviratne <os...@gmail.com>.
Hi Arthur,
I am trying to figure out how to implement this with OM. So, could you
please explain what you meant by "handled as built-in"? Is it having another
XMLAttr impl, or another representation of schema in woden (similar to
inline/imported schema)?
Thanks,
Oshani
On 9/12/06, Arthur Ryman <ry...@ca.ibm.com> wrote:
>
>
> I think the xsi attributes shown be handled as built-in since they are
> part of XSD. The extension mechanism should be reserved for WSDL extensions.
>
> 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
>
>
> *"Jeremy Hughes" <hu...@apache.org>*
> Sent by: jpjhughes@gmail.com
>
> 09/12/2006 04:57 AM Please respond to
> woden-dev@ws.apache.org
>
> To
> woden-dev@ws.apache.org, oshanis@gmail.com cc
>
> Subject
> Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of
> <description> from either parser?
>
>
>
>
>
>
> I think this should be handled like any other extension. Anything not
> in the WSDL namespace is an extension to the WSDL. If we start
> 'special-casing' extensions then we could find other extensions would
> like to do the same.
>
> Jeremy
>
> On 9/12/06, Oshani Seneviratne <os...@gmail.com> wrote:
> > Hi Graham and all,
> >
> > Even in the DOMWSDLReader, I assume that parseExtensionAttributes
> > method was not intended to handle this. I'm referring to the comment
> > "//TODO handle xsi attrs elsewhere, without need to register". (Please
> > correct me if I'm wrong on this! )
> >
> > So, theoretically as you asked, how about having a method like
> > parseExtensionAttributeSchema (or whatever the name) which gets called
> > from the parseExtensionAttributes? We could also have a schema
> > implementation like ExtensionAttributeSchema that could represent such
> > external schemas. (Or maybe ImportedSchema could be used here).
> > Any comments?
> >
> > Also, just to clarify, in the WSDL fragment you've given there are 2
> > schema locations for 1 attribute. Is that possible?
> >
> > > <description targetNamespace="http://example.com/bank"
> > > xmlns="http://www.w3.org/2006/01/wsdl"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > > xsi:schemaLocation=
> > > "http://www.w3.org/2006/01/wsdl
> > > http://www.w3.org/2006/01/wsdl/wsdl20.xsd
> > > http://www.w3.org/2001/XMLSchema
> > > http://www.w3.org/2001/XMLSchema.xsd" >
> > >
> >
> > Thanks and Regards,
> > Oshani
> >
> > ---------------------------------------------------------------------
> > 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-USER :)] how to access xsi:schemaLocation attribute of from
either parser?
Posted by Arthur Ryman <ry...@ca.ibm.com>.
I think the xsi attributes shown be handled as built-in since they are
part of XSD. The extension mechanism should be reserved for WSDL
extensions.
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
"Jeremy Hughes" <hu...@apache.org>
Sent by: jpjhughes@gmail.com
09/12/2006 04:57 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org, oshanis@gmail.com
cc
Subject
Re: [WODEN-USER :)] how to access xsi:schemaLocation attribute of
<description> from either parser?
I think this should be handled like any other extension. Anything not
in the WSDL namespace is an extension to the WSDL. If we start
'special-casing' extensions then we could find other extensions would
like to do the same.
Jeremy
On 9/12/06, Oshani Seneviratne <os...@gmail.com> wrote:
> Hi Graham and all,
>
> Even in the DOMWSDLReader, I assume that parseExtensionAttributes
> method was not intended to handle this. I'm referring to the comment
> "//TODO handle xsi attrs elsewhere, without need to register". (Please
> correct me if I'm wrong on this! )
>
> So, theoretically as you asked, how about having a method like
> parseExtensionAttributeSchema (or whatever the name) which gets called
> from the parseExtensionAttributes? We could also have a schema
> implementation like ExtensionAttributeSchema that could represent such
> external schemas. (Or maybe ImportedSchema could be used here).
> Any comments?
>
> Also, just to clarify, in the WSDL fragment you've given there are 2
> schema locations for 1 attribute. Is that possible?
>
> > <description targetNamespace="http://example.com/bank"
> > xmlns="http://www.w3.org/2006/01/wsdl"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation=
> > "http://www.w3.org/2006/01/wsdl
> > http://www.w3.org/2006/01/wsdl/wsdl20.xsd
> > http://www.w3.org/2001/XMLSchema
> > http://www.w3.org/2001/XMLSchema.xsd" >
> >
>
> Thanks and Regards,
> Oshani
>
> ---------------------------------------------------------------------
> 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-USER :)] how to access xsi:schemaLocation attribute of from either parser?
Posted by Jeremy Hughes <hu...@apache.org>.
I think this should be handled like any other extension. Anything not
in the WSDL namespace is an extension to the WSDL. If we start
'special-casing' extensions then we could find other extensions would
like to do the same.
Jeremy
On 9/12/06, Oshani Seneviratne <os...@gmail.com> wrote:
> Hi Graham and all,
>
> Even in the DOMWSDLReader, I assume that parseExtensionAttributes
> method was not intended to handle this. I'm referring to the comment
> "//TODO handle xsi attrs elsewhere, without need to register". (Please
> correct me if I'm wrong on this! )
>
> So, theoretically as you asked, how about having a method like
> parseExtensionAttributeSchema (or whatever the name) which gets called
> from the parseExtensionAttributes? We could also have a schema
> implementation like ExtensionAttributeSchema that could represent such
> external schemas. (Or maybe ImportedSchema could be used here).
> Any comments?
>
> Also, just to clarify, in the WSDL fragment you've given there are 2
> schema locations for 1 attribute. Is that possible?
>
> > <description targetNamespace="http://example.com/bank"
> > xmlns="http://www.w3.org/2006/01/wsdl"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation=
> > "http://www.w3.org/2006/01/wsdl
> > http://www.w3.org/2006/01/wsdl/wsdl20.xsd
> > http://www.w3.org/2001/XMLSchema
> > http://www.w3.org/2001/XMLSchema.xsd" >
> >
>
> Thanks and Regards,
> Oshani
>
> ---------------------------------------------------------------------
> 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-USER :)] how to access xsi:schemaLocation attribute of from either parser?
Posted by Oshani Seneviratne <os...@gmail.com>.
Hi Graham and all,
Even in the DOMWSDLReader, I assume that parseExtensionAttributes
method was not intended to handle this. I'm referring to the comment
"//TODO handle xsi attrs elsewhere, without need to register". (Please
correct me if I'm wrong on this! )
So, theoretically as you asked, how about having a method like
parseExtensionAttributeSchema (or whatever the name) which gets called
from the parseExtensionAttributes? We could also have a schema
implementation like ExtensionAttributeSchema that could represent such
external schemas. (Or maybe ImportedSchema could be used here).
Any comments?
Also, just to clarify, in the WSDL fragment you've given there are 2
schema locations for 1 attribute. Is that possible?
> <description targetNamespace="http://example.com/bank"
> xmlns="http://www.w3.org/2006/01/wsdl"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation=
> "http://www.w3.org/2006/01/wsdl
> http://www.w3.org/2006/01/wsdl/wsdl20.xsd
> http://www.w3.org/2001/XMLSchema
> http://www.w3.org/2001/XMLSchema.xsd" >
>
Thanks and Regards,
Oshani
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org