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 Demetris <de...@ece.neu.edu> on 2010/03/31 07:21:58 UTC
Examples
Hi all,
I am learning Woden and I have simply copied the examples listed both
in the User Guide and in the distribution release notes - I noticed a
few issues
with the examples:
DescriptionElement descElem = reader.readWSDL(wsdlurl2); //
the <description> element
The above right hand side of the statement returns a Description and NOT
a DescriptionElement
so the compilation fails. To fix it I used this instead:
Description descComp = reader.readWSDL(wsdlurl2);
// the Description component, always returned
DescriptionElement descElem = descComp.toElement(); //
the <description> element, if required
Why is the original statement broken?
Also with these statements the last one fails on the faults[0]:
InterfaceElement interfaceElem = interfaces[0];
InterfaceFaultElement[] faults =
interfaceElem.getInterfaceFaultElements();
XmlSchemaElement xsElem = faults[0].getElement();
To fix it I has to use:
XmlSchemaElement xsElem = faults[0].getXmlSchemaElement();
I am wondering if the examples are stale or if I am missing something.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Sounds good Sagara thanks - I will post my requirements and see what
others say.
Thanks
Sagara Gunathunga wrote:
>
>
> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Ok Thanks Sagara and Dilshan ---
>
> I guess I will need to use the lighter parsers ( I have used kXML
> once before) and do the parsing
> my self. I am assuming needing to parse both for SOAP and REST
> descriptions will be a separate
> project by itself but if my app is seeking only a few particular
> parts of the WSDL file it should not
> be as bad.
>
> I can also look at Axis2, CXF and WSO2 even though they don't use
> mobile parsers either - just
> to get an idea on the parsing. Will anyone working with Woden fix
> the examples that have the issues
> I pointed out?
>
>
> User guide should be corrected now.
>
>
>
> Are there any other examples available?
>
>
> At the moment no , but if you have any specific requirement please
> post to the list so that some one can help out. Also you can refer
> unit tests.
>
> Thanks,
>
>
>
> Thanks
>
> Sagara Gunathunga wrote:
>
> Demetris,
>
> AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you
> could mange to run Woden on J2ME CDC, performance wise it's
> not a good option because Woden itself and XML parsers used by
> the Woden were not optimized to support J2ME CDC. IMO better
> to handle WSDL.2.0 doc in a XML level using parser like KXML
> or NanoXML .
>
> Thanks,
> On Thu, Apr 1, 2010 at 2:18 PM, Dilshan Edirisuriya
> <dilshan.ed@gmail.com <ma...@gmail.com>
> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>>
> wrote:
>
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME
> technologies. But
> I feel woden will be bit heavy weight to work with mobile
> devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on mobile
> devices (on J2ME CDC).
> I am getting errors on standard Java methods (ex.
> split) so I
> guess that test would suffice
> that I cannot run Woden until CDC. I can look at the source
> code and see if I can figure out
> the extend of what needs to be changed but I may not
> have the
> time to port it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
> Hi Demetris,
>
>
> You are correct, those user guide pages are
> outdated. This
> is already reported in Woden-218 [1].
>
> [1] - https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply copied the
> examples listed
> both
> in the User Guide and in the distribution
> release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem =
> reader.readWSDL(wsdlurl2); // the
> <description>
> element
>
> The above right hand side of the statement returns a
> Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I used this
> instead:
>
> Description descComp =
> reader.readWSDL(wsdlurl2);
> // the Description component,
> always returned
> DescriptionElement descElem =
> descComp.toElement(); // the
> <description>
> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one fails on the
> faults[0]:
> InterfaceElement interfaceElem = interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem =
> faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem =
> faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale or if I am
> missing something.
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
One more question I have is this - since I am trying to parse WSDL 2.0
documents
on mobile devices, importing the complete Woden package over will be
impossible
at this point. How easy will it be to extract components from Woden that
will allow
me to carry out the tasks that my peers (devices) need - for example, if
all a mobile
client is interested in is to retrieve the address of the REST resource,
or the Qname
etc for the SOAP service, how easy will it be to extract those parts of
the functionality
from Woden's baseline?
Thanks again
Arthur Ryman wrote:
> There is a REST example in the WSDL 2.0 Primer [1]
>
> There is also a REST example in the W3C Test Suite (for W3C Bugzilla) [2]
>
> [1]
> http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626/#adv-service-references
> [2]
> http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/good/W3CBugzillaHttp-1G/
>
> Regards,
> ___________________________________________________________________________
>
> Arthur Ryman, PhD, DE
>
>
> Chief Architect, Project and Portfolio Management
>
> IBM Software, Rational
>
> Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
> Twitter | Facebook | YouTube
>
>
>
>
>
>
>
> From:
> Sagara Gunathunga <sa...@gmail.com>
> To:
> woden-dev@ws.apache.org
> Date:
> 04/06/2010 01:11 AM
> Subject:
> Re: Examples
>
>
>
> http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html
>
>
> HTH
>
> Thanks,
>
> On Tue, Apr 6, 2010 at 9:22 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Is there a WSDL 2.0 sample for a REST and for SOAP service posted
> anywhere?
> I do have Laurence's example from his article but I was wondering if I can
> a variety
> of such documents to study so that I can work my way through the Woden
> code a bit
> easier.
>
> Thanks
>
> (I guess I can generate such documents by querying Axis2 engines ...)
>
> Sagara Gunathunga wrote:
>
>
> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu <mailto:
> demetris@ece.neu.edu>> wrote:
>
>
> Ok Thanks Sagara and Dilshan ---
>
> I guess I will need to use the lighter parsers ( I have used kXML
> once before) and do the parsing
> my self. I am assuming needing to parse both for SOAP and REST
> descriptions will be a separate
> project by itself but if my app is seeking only a few particular
> parts of the WSDL file it should not
> be as bad.
>
> I can also look at Axis2, CXF and WSO2 even though they don't use
> mobile parsers either - just
> to get an idea on the parsing. Will anyone working with Woden fix
> the examples that have the issues
> I pointed out?
>
> User guide should be corrected now.
>
>
> Are there any other examples available?
>
>
> At the moment no , but if you have any specific requirement please post
> to the list so that some one can help out. Also you can refer unit tests.
>
> Thanks,
>
>
> Thanks
>
> Sagara Gunathunga wrote:
>
> Demetris,
>
> AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you
> could mange to run Woden on J2ME CDC, performance wise it's
> not a good option because Woden itself and XML parsers used by
> the Woden were not optimized to support J2ME CDC. IMO better
> to handle WSDL.2.0 doc in a XML level using parser like KXML
> or NanoXML .
>
> Thanks, On Thu, Apr 1, 2010 at 2:18 PM, Dilshan
> Edirisuriya
> <dilshan.ed@gmail.com <ma...@gmail.com>
> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>>
>
> wrote:
>
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME
> technologies. But
> I feel woden will be bit heavy weight to work with mobile
> devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on mobile
> devices (on J2ME CDC).
> I am getting errors on standard Java methods (ex.
> split) so I
> guess that test would suffice
> that I cannot run Woden until CDC. I can look at the source
> code and see if I can figure out
> the extend of what needs to be changed but I may not
> have the
> time to port it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
> Hi Demetris,
>
>
> You are correct, those user guide pages are
> outdated. This
> is already reported in Woden-218 [1].
>
> [1] - https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply copied the
> examples listed
> both
> in the User Guide and in the distribution
> release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem =
> reader.readWSDL(wsdlurl2); // the
> <description>
> element
>
> The above right hand side of the statement returns a
> Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I used this
> instead:
>
> Description descComp =
> reader.readWSDL(wsdlurl2);
> // the Description component,
> always returned
> DescriptionElement descElem =
> descComp.toElement(); // the
> <description>
> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one fails on the
> faults[0]:
> InterfaceElement interfaceElem = interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem =
> faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem =
> faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale or if I am
> missing something.
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> -- Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@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: Examples
Posted by Demetris <de...@ece.neu.edu>.
Super - thanks Arthur and Sagara
Arthur Ryman wrote:
> There is a REST example in the WSDL 2.0 Primer [1]
>
> There is also a REST example in the W3C Test Suite (for W3C Bugzilla) [2]
>
> [1]
> http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626/#adv-service-references
> [2]
> http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/good/W3CBugzillaHttp-1G/
>
> Regards,
> ___________________________________________________________________________
>
> Arthur Ryman, PhD, DE
>
>
> Chief Architect, Project and Portfolio Management
>
> IBM Software, Rational
>
> Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
> Twitter | Facebook | YouTube
>
>
>
>
>
>
>
> From:
> Sagara Gunathunga <sa...@gmail.com>
> To:
> woden-dev@ws.apache.org
> Date:
> 04/06/2010 01:11 AM
> Subject:
> Re: Examples
>
>
>
> http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html
>
>
> HTH
>
> Thanks,
>
> On Tue, Apr 6, 2010 at 9:22 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Is there a WSDL 2.0 sample for a REST and for SOAP service posted
> anywhere?
> I do have Laurence's example from his article but I was wondering if I can
> a variety
> of such documents to study so that I can work my way through the Woden
> code a bit
> easier.
>
> Thanks
>
> (I guess I can generate such documents by querying Axis2 engines ...)
>
> Sagara Gunathunga wrote:
>
>
> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu <mailto:
> demetris@ece.neu.edu>> wrote:
>
>
> Ok Thanks Sagara and Dilshan ---
>
> I guess I will need to use the lighter parsers ( I have used kXML
> once before) and do the parsing
> my self. I am assuming needing to parse both for SOAP and REST
> descriptions will be a separate
> project by itself but if my app is seeking only a few particular
> parts of the WSDL file it should not
> be as bad.
>
> I can also look at Axis2, CXF and WSO2 even though they don't use
> mobile parsers either - just
> to get an idea on the parsing. Will anyone working with Woden fix
> the examples that have the issues
> I pointed out?
>
> User guide should be corrected now.
>
>
> Are there any other examples available?
>
>
> At the moment no , but if you have any specific requirement please post
> to the list so that some one can help out. Also you can refer unit tests.
>
> Thanks,
>
>
> Thanks
>
> Sagara Gunathunga wrote:
>
> Demetris,
>
> AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you
> could mange to run Woden on J2ME CDC, performance wise it's
> not a good option because Woden itself and XML parsers used by
> the Woden were not optimized to support J2ME CDC. IMO better
> to handle WSDL.2.0 doc in a XML level using parser like KXML
> or NanoXML .
>
> Thanks, On Thu, Apr 1, 2010 at 2:18 PM, Dilshan
> Edirisuriya
> <dilshan.ed@gmail.com <ma...@gmail.com>
> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>>
>
> wrote:
>
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME
> technologies. But
> I feel woden will be bit heavy weight to work with mobile
> devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on mobile
> devices (on J2ME CDC).
> I am getting errors on standard Java methods (ex.
> split) so I
> guess that test would suffice
> that I cannot run Woden until CDC. I can look at the source
> code and see if I can figure out
> the extend of what needs to be changed but I may not
> have the
> time to port it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
> Hi Demetris,
>
>
> You are correct, those user guide pages are
> outdated. This
> is already reported in Woden-218 [1].
>
> [1] - https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply copied the
> examples listed
> both
> in the User Guide and in the distribution
> release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem =
> reader.readWSDL(wsdlurl2); // the
> <description>
> element
>
> The above right hand side of the statement returns a
> Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I used this
> instead:
>
> Description descComp =
> reader.readWSDL(wsdlurl2);
> // the Description component,
> always returned
> DescriptionElement descElem =
> descComp.toElement(); // the
> <description>
> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one fails on the
> faults[0]:
> InterfaceElement interfaceElem = interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem =
> faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem =
> faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale or if I am
> missing something.
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> -- Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@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: Examples
Posted by Arthur Ryman <ry...@ca.ibm.com>.
There is a REST example in the WSDL 2.0 Primer [1]
There is also a REST example in the W3C Test Suite (for W3C Bugzilla) [2]
[1]
http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626/#adv-service-references
[2]
http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/good/W3CBugzillaHttp-1G/
Regards,
___________________________________________________________________________
Arthur Ryman, PhD, DE
Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
Twitter | Facebook | YouTube
From:
Sagara Gunathunga <sa...@gmail.com>
To:
woden-dev@ws.apache.org
Date:
04/06/2010 01:11 AM
Subject:
Re: Examples
http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html
HTH
Thanks,
On Tue, Apr 6, 2010 at 9:22 AM, Demetris <de...@ece.neu.edu> wrote:
Is there a WSDL 2.0 sample for a REST and for SOAP service posted
anywhere?
I do have Laurence's example from his article but I was wondering if I can
a variety
of such documents to study so that I can work my way through the Woden
code a bit
easier.
Thanks
(I guess I can generate such documents by querying Axis2 engines ...)
Sagara Gunathunga wrote:
On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu <mailto:
demetris@ece.neu.edu>> wrote:
Ok Thanks Sagara and Dilshan ---
I guess I will need to use the lighter parsers ( I have used kXML
once before) and do the parsing
my self. I am assuming needing to parse both for SOAP and REST
descriptions will be a separate
project by itself but if my app is seeking only a few particular
parts of the WSDL file it should not
be as bad.
I can also look at Axis2, CXF and WSO2 even though they don't use
mobile parsers either - just
to get an idea on the parsing. Will anyone working with Woden fix
the examples that have the issues
I pointed out?
User guide should be corrected now.
Are there any other examples available?
At the moment no , but if you have any specific requirement please post
to the list so that some one can help out. Also you can refer unit tests.
Thanks,
Thanks
Sagara Gunathunga wrote:
Demetris,
AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you
could mange to run Woden on J2ME CDC, performance wise it's
not a good option because Woden itself and XML parsers used by
the Woden were not optimized to support J2ME CDC. IMO better
to handle WSDL.2.0 doc in a XML level using parser like KXML
or NanoXML .
Thanks, On Thu, Apr 1, 2010 at 2:18 PM, Dilshan
Edirisuriya
<dilshan.ed@gmail.com <ma...@gmail.com>
<mailto:dilshan.ed@gmail.com <ma...@gmail.com>>>
wrote:
Hi Demetris,
Sorry Demetris I am not that familiar with J2ME
technologies. But
I feel woden will be bit heavy weight to work with mobile
devices.
On Thu, Apr 1, 2010 at 1:08 AM, Demetris
<demetris@ece.neu.edu <ma...@ece.neu.edu>
<mailto:demetris@ece.neu.edu
<ma...@ece.neu.edu>>> wrote:
Got it - thanks Dilshan.
I spoke with Laurence regarding running Woden on mobile
devices (on J2ME CDC).
I am getting errors on standard Java methods (ex.
split) so I
guess that test would suffice
that I cannot run Woden until CDC. I can look at the source
code and see if I can figure out
the extend of what needs to be changed but I may not
have the
time to port it. Anyone knows
of any mobile wsdl parsers?
Thanks
Dilshan Edirisuriya wrote:
Hi Demetris,
You are correct, those user guide pages are
outdated. This
is already reported in Woden-218 [1].
[1] - https://issues.apache.org/jira/browse/WODEN-218
Thanks ,
Dilshan
blog : http://dilshaned.blogspot.com/
On Wed, Mar 31, 2010 at 10:51 AM, Demetris
<demetris@ece.neu.edu <ma...@ece.neu.edu>
<mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
<mailto:demetris@ece.neu.edu
<ma...@ece.neu.edu>
<mailto:demetris@ece.neu.edu
<ma...@ece.neu.edu>>>> wrote:
Hi all,
I am learning Woden and I have simply copied the
examples listed
both
in the User Guide and in the distribution
release notes - I
noticed a few issues
with the examples:
DescriptionElement descElem =
reader.readWSDL(wsdlurl2); // the
<description>
element
The above right hand side of the statement returns a
Description
and NOT a DescriptionElement
so the compilation fails. To fix it I used this
instead:
Description descComp =
reader.readWSDL(wsdlurl2);
// the Description component,
always returned
DescriptionElement descElem =
descComp.toElement(); // the
<description>
element, if required
Why is the original statement broken?
Also with these statements the last one fails on the
faults[0]:
InterfaceElement interfaceElem = interfaces[0];
InterfaceFaultElement[] faults =
interfaceElem.getInterfaceFaultElements();
XmlSchemaElement xsElem =
faults[0].getElement();
To fix it I has to use:
XmlSchemaElement xsElem =
faults[0].getXmlSchemaElement();
I am wondering if the examples are stale or if I am
missing something.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail:
woden-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>
<mailto:woden-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>>
<mailto:woden-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>
<mailto:woden-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>>>
For additional commands, e-mail:
woden-dev-help@ws.apache.org
<ma...@ws.apache.org>
<mailto:woden-dev-help@ws.apache.org
<ma...@ws.apache.org>>
<mailto:woden-dev-help@ws.apache.org
<ma...@ws.apache.org>
<mailto:woden-dev-help@ws.apache.org
<ma...@ws.apache.org>>>
---------------------------------------------------------------------
To unsubscribe, e-mail:
woden-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>
<mailto:woden-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>>
For additional commands, e-mail:
woden-dev-help@ws.apache.org <ma...@ws.apache.org>
<mailto:woden-dev-help@ws.apache.org
<ma...@ws.apache.org>>
-- Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
<http://people.apache.org/%7Esagara/>
<http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>
For additional commands, e-mail: woden-dev-help@ws.apache.org
<ma...@ws.apache.org>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/ <
http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Hi Arthur - thanks for the response. I will give it a shot and let you know.
Arthur Ryman wrote:
> Demetris,
>
> in-out operations have exactly two messages. In this example, there is
> an input, but it's encoded in the IRI of the request. That's what the
> style attribute specifies. IRI style lets you put the input message on
> the IRI.
>
> This is a good test for Woden. Drop the <input> and see if Woden
> complains.
>
> -- Arthur
>
> On Wed, May 19, 2010 at 12:35 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Is there any code implementing the example I am refering to below
> (http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/)
> that is downloadable?
>
> Thanks
>
>
> Demetris wrote:
>
>
> Hi all,
>
> in one of the examples wsdl for the REST-based BookList I see
> the following:
>
> <wsdl:interface name="BookListInterface">
> <wsdl:operation name="getBookList"
> pattern="http://www.w3.org/ns/wsdl/in-out"
> style="http://www.w3.org/ns/wsdl/style/iri"
> wsdlx:safe="true">
> <wsdl:documentation>
> This operation returns a list of books.
> </wsdl:documentation>
> <wsdl:input element="msg:getBookList"/>
> <wsdl:output element="msg:bookList"/>
> </wsdl:operation>
> </wsdl:interface>
>
> If no inputs are required for the particular method I am
> assuming that the wsdl:input element
> can be left out. Yes? And if the this is a 'set and forget'
> method the same would apply
> to the wsdl:output element?
>
> Thanks
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@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: Examples
Posted by Arthur Ryman <ar...@gmail.com>.
Demetris,
in-out operations have exactly two messages. In this example, there is an
input, but it's encoded in the IRI of the request. That's what the style
attribute specifies. IRI style lets you put the input message on the IRI.
This is a good test for Woden. Drop the <input> and see if Woden complains.
-- Arthur
On Wed, May 19, 2010 at 12:35 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Is there any code implementing the example I am refering to below
> (http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/)
> that is downloadable?
>
> Thanks
>
>
> Demetris wrote:
>
>>
>> Hi all,
>>
>> in one of the examples wsdl for the REST-based BookList I see the
>> following:
>>
>> <wsdl:interface name="BookListInterface">
>> <wsdl:operation name="getBookList"
>> pattern="http://www.w3.org/ns/wsdl/in-out"
>> style="http://www.w3.org/ns/wsdl/style/iri"
>> wsdlx:safe="true">
>> <wsdl:documentation>
>> This operation returns a list of books.
>> </wsdl:documentation>
>> <wsdl:input element="msg:getBookList"/>
>> <wsdl:output element="msg:bookList"/>
>> </wsdl:operation>
>> </wsdl:interface>
>>
>> If no inputs are required for the particular method I am assuming that the
>> wsdl:input element
>> can be left out. Yes? And if the this is a 'set and forget' method the
>> same would apply
>> to the wsdl:output element?
>>
>> Thanks
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Sounds good - thanks Arthur.
Arthur Ryman wrote:
> Demetris,
>
> Yes, the WSDL file advertises the available bindings, The client picks the
> best binding for its purposes.
>
> Regards,
> ___________________________________________________________________________
>
> Arthur Ryman, PhD, DE
>
>
> Chief Architect, Project and Portfolio Management
>
> IBM Software, Rational
>
> Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
> Twitter | Facebook | YouTube
>
>
>
>
>
>
>
> From:
> Demetris <de...@ece.neu.edu>
> To:
> woden-dev@ws.apache.org
> Date:
> 05/03/2010 01:39 PM
> Subject:
> Re: Examples
>
>
>
>
> Hi Arthur and thanks for the response as well - so just as I thought ...
> Axis for example
> uses the WSDL file to generate appropriate stubs for invoking a service
> (based on
> the binding). My pt was along the same lines, that without prior
> knowledge of the remote
> service, parsing the incoming WSDL file the client should be able to
> determine the binding
> type and to take appropriate actions to invoke it - SOAP or REST or
> whatever else.
> Do you agree?
>
> Arthur Ryman wrote:
>
>> Demetris,
>>
>> Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly
>> by defining its <interface>. You then define one or more <binding>s
>> for it to describe the concrete protocol used to invoke it.
>>
>> There is a binding types for SOAP:/ http://www.w3.org/ns/wsdl/soap/
>>
>> REST uses the HTTP binding: /http://www.w3.org/ns/wsdl/http/
>>
>> These are described in Part 2 of the spec. [1]
>>
>> -- Arthur
>>
>> [1] http://www.w3.org/TR/wsdl20-adjuncts/
>>
>> On Mon, May 3, 2010 at 12:56 AM, Demetris <demetris@ece.neu.edu
>> <ma...@ece.neu.edu>> wrote:
>>
>>
>> Hi Sagara,
>>
>> sorry if my original posting was a bit confusing. You are indeed
>> providing some good information below and in fact
>> I am aware of most of it. To say it in simpler terms, if a client
>> is retrieving WSDL files from a set of remote sites
>> without knowing if what they describe is a deployed service is a
>> SOAP service or a REST service, can the
>> client know by inspecting the WSDL document such a type? My
>> feeling (and as you may be suggesting below)
>> that this is not a reliable method to find such a difference as
>> descriptions of these services may yield identical
>> WSDL documents. Is this correct? But I do see that SOAP
>> descriptions usually carry either a SOAPAction
>> or a soap operation tag - is this always the case or not?
>>
>> Thanks again
>>
>> Sagara Gunathunga wrote:
>>
>>
>> I' m not sure what is the exact problem you have here,
>> basically WSDL 2.0 Interface is used to describe abstract
>> interface of a service (contract) and it's common for both
>> SOAP and REST. WSDL 2.0 Binding component describe how to
>> access above interface using a concrete protocol like SOAP ,
>> HTTP etc.
>>
>> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that
>> can be used to provide required details in order to access the
>> service using SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2]
>> describe details required to access the service using HTTP
>> protocol ( REST ) , in WSDL level this is the mechanism to
>> describe REST and SOAP services, I guess this make sense.
>>
>>
>> BTW each WS engine use their own techniques to distinguish
>> SOAP and REST invocations at run time , As an example Axis2
>> basically assume absence of SAOP structure in a incoming
>> message as a REST invocation. But this is not relevant to WSDL
>> description .
>> [1] -
>> http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
>> [2] -
>>
>>
> http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
>> Thanks,
>>
>> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
>> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>> wrote:
>>
>>
>> Hi all,
>>
>> what is (or are) the particular and specific difference
>> between
>> a SOAP serv WSDL 2.0
>> description and a REST serv WSDL 2.0 description that will
>> make a
>> parser (or a flag
>> setter) distinguish between the two? Would the existance of
>>
> the
>
>> keyword 'soap' in the former
>> case be such an indisputable evidence? The ports may be?
>>
>>
>> Thanks
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org <
>>
> mailto:woden-dev-help@ws.apache.org>
>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>> <http://people.apache.org/%7Esagara/>
>> <http://people.apache.org/%7Esagara/>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@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: Examples
Posted by Demetris <de...@ece.neu.edu>.
Is there any code implementing the example I am refering to below
(http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/)
that is downloadable?
Thanks
Demetris wrote:
>
> Hi all,
>
> in one of the examples wsdl for the REST-based BookList I see the
> following:
>
> <wsdl:interface name="BookListInterface">
> <wsdl:operation name="getBookList"
> pattern="http://www.w3.org/ns/wsdl/in-out"
> style="http://www.w3.org/ns/wsdl/style/iri"
> wsdlx:safe="true">
> <wsdl:documentation>
> This operation returns a list of books.
> </wsdl:documentation>
> <wsdl:input element="msg:getBookList"/>
> <wsdl:output element="msg:bookList"/>
> </wsdl:operation>
> </wsdl:interface>
>
> If no inputs are required for the particular method I am assuming that
> the wsdl:input element
> can be left out. Yes? And if the this is a 'set and forget' method the
> same would apply
> to the wsdl:output element?
>
> Thanks
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Hi all,
in one of the examples wsdl for the REST-based BookList I see the following:
<wsdl:interface name="BookListInterface">
<wsdl:operation name="getBookList"
pattern="http://www.w3.org/ns/wsdl/in-out"
style="http://www.w3.org/ns/wsdl/style/iri"
wsdlx:safe="true">
<wsdl:documentation>
This operation returns a list of books.
</wsdl:documentation>
<wsdl:input element="msg:getBookList"/>
<wsdl:output element="msg:bookList"/>
</wsdl:operation>
</wsdl:interface>
If no inputs are required for the particular method I am assuming that
the wsdl:input element
can be left out. Yes? And if the this is a 'set and forget' method the
same would apply
to the wsdl:output element?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Demetris,
Yes, the WSDL file advertises the available bindings, The client picks the
best binding for its purposes.
Regards,
___________________________________________________________________________
Arthur Ryman, PhD, DE
Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
Twitter | Facebook | YouTube
From:
Demetris <de...@ece.neu.edu>
To:
woden-dev@ws.apache.org
Date:
05/03/2010 01:39 PM
Subject:
Re: Examples
Hi Arthur and thanks for the response as well - so just as I thought ...
Axis for example
uses the WSDL file to generate appropriate stubs for invoking a service
(based on
the binding). My pt was along the same lines, that without prior
knowledge of the remote
service, parsing the incoming WSDL file the client should be able to
determine the binding
type and to take appropriate actions to invoke it - SOAP or REST or
whatever else.
Do you agree?
Arthur Ryman wrote:
> Demetris,
>
> Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly
> by defining its <interface>. You then define one or more <binding>s
> for it to describe the concrete protocol used to invoke it.
>
> There is a binding types for SOAP:/ http://www.w3.org/ns/wsdl/soap/
>
> REST uses the HTTP binding: /http://www.w3.org/ns/wsdl/http/
>
> These are described in Part 2 of the spec. [1]
>
> -- Arthur
>
> [1] http://www.w3.org/TR/wsdl20-adjuncts/
>
> On Mon, May 3, 2010 at 12:56 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Hi Sagara,
>
> sorry if my original posting was a bit confusing. You are indeed
> providing some good information below and in fact
> I am aware of most of it. To say it in simpler terms, if a client
> is retrieving WSDL files from a set of remote sites
> without knowing if what they describe is a deployed service is a
> SOAP service or a REST service, can the
> client know by inspecting the WSDL document such a type? My
> feeling (and as you may be suggesting below)
> that this is not a reliable method to find such a difference as
> descriptions of these services may yield identical
> WSDL documents. Is this correct? But I do see that SOAP
> descriptions usually carry either a SOAPAction
> or a soap operation tag - is this always the case or not?
>
> Thanks again
>
> Sagara Gunathunga wrote:
>
>
> I' m not sure what is the exact problem you have here,
> basically WSDL 2.0 Interface is used to describe abstract
> interface of a service (contract) and it's common for both
> SOAP and REST. WSDL 2.0 Binding component describe how to
> access above interface using a concrete protocol like SOAP ,
> HTTP etc.
>
> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that
> can be used to provide required details in order to access the
> service using SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2]
> describe details required to access the service using HTTP
> protocol ( REST ) , in WSDL level this is the mechanism to
> describe REST and SOAP services, I guess this make sense.
>
>
> BTW each WS engine use their own techniques to distinguish
> SOAP and REST invocations at run time , As an example Axis2
> basically assume absence of SAOP structure in a incoming
> message as a REST invocation. But this is not relevant to WSDL
> description .
> [1] -
> http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
> [2] -
>
http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
> Thanks,
>
> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Hi all,
>
> what is (or are) the particular and specific difference
> between
> a SOAP serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will
> make a
> parser (or a flag
> setter) distinguish between the two? Would the existance of
the
> keyword 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <
mailto:woden-dev-help@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@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: Examples
Posted by Demetris <de...@ece.neu.edu>.
Hi Arthur and thanks for the response as well - so just as I thought ...
Axis for example
uses the WSDL file to generate appropriate stubs for invoking a service
(based on
the binding). My pt was along the same lines, that without prior
knowledge of the remote
service, parsing the incoming WSDL file the client should be able to
determine the binding
type and to take appropriate actions to invoke it - SOAP or REST or
whatever else.
Do you agree?
Arthur Ryman wrote:
> Demetris,
>
> Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly
> by defining its <interface>. You then define one or more <binding>s
> for it to describe the concrete protocol used to invoke it.
>
> There is a binding types for SOAP:/ http://www.w3.org/ns/wsdl/soap/
>
> REST uses the HTTP binding: /http://www.w3.org/ns/wsdl/http/
>
> These are described in Part 2 of the spec. [1]
>
> -- Arthur
>
> [1] http://www.w3.org/TR/wsdl20-adjuncts/
>
> On Mon, May 3, 2010 at 12:56 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Hi Sagara,
>
> sorry if my original posting was a bit confusing. You are indeed
> providing some good information below and in fact
> I am aware of most of it. To say it in simpler terms, if a client
> is retrieving WSDL files from a set of remote sites
> without knowing if what they describe is a deployed service is a
> SOAP service or a REST service, can the
> client know by inspecting the WSDL document such a type? My
> feeling (and as you may be suggesting below)
> that this is not a reliable method to find such a difference as
> descriptions of these services may yield identical
> WSDL documents. Is this correct? But I do see that SOAP
> descriptions usually carry either a SOAPAction
> or a soap operation tag - is this always the case or not?
>
> Thanks again
>
> Sagara Gunathunga wrote:
>
>
> I' m not sure what is the exact problem you have here,
> basically WSDL 2.0 Interface is used to describe abstract
> interface of a service (contract) and it's common for both
> SOAP and REST. WSDL 2.0 Binding component describe how to
> access above interface using a concrete protocol like SOAP ,
> HTTP etc.
>
> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that
> can be used to provide required details in order to access the
> service using SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2]
> describe details required to access the service using HTTP
> protocol ( REST ) , in WSDL level this is the mechanism to
> describe REST and SOAP services, I guess this make sense.
>
>
> BTW each WS engine use their own techniques to distinguish
> SOAP and REST invocations at run time , As an example Axis2
> basically assume absence of SAOP structure in a incoming
> message as a REST invocation. But this is not relevant to WSDL
> description .
> [1] -
> http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
> [2] -
> http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
> Thanks,
>
> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Hi all,
>
> what is (or are) the particular and specific difference
> between
> a SOAP serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will
> make a
> parser (or a flag
> setter) distinguish between the two? Would the existance of the
> keyword 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@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: Examples
Posted by Arthur Ryman <ar...@gmail.com>.
Demetris,
Sagara is correct. WSDL 2.0 lets you describe a Web service abstractly by
defining its <interface>. You then define one or more <binding>s for it to
describe the concrete protocol used to invoke it.
There is a binding types for SOAP:* http://www.w3.org/ns/wsdl/soap*
REST uses the HTTP binding: *http://www.w3.org/ns/wsdl/http*
These are described in Part 2 of the spec. [1]
-- Arthur
[1] http://www.w3.org/TR/wsdl20-adjuncts/
On Mon, May 3, 2010 at 12:56 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Hi Sagara,
>
> sorry if my original posting was a bit confusing. You are indeed providing
> some good information below and in fact
> I am aware of most of it. To say it in simpler terms, if a client is
> retrieving WSDL files from a set of remote sites
> without knowing if what they describe is a deployed service is a SOAP
> service or a REST service, can the
> client know by inspecting the WSDL document such a type? My feeling (and as
> you may be suggesting below)
> that this is not a reliable method to find such a difference as
> descriptions of these services may yield identical
> WSDL documents. Is this correct? But I do see that SOAP descriptions
> usually carry either a SOAPAction
> or a soap operation tag - is this always the case or not?
>
> Thanks again
>
> Sagara Gunathunga wrote:
>
>>
>> I' m not sure what is the exact problem you have here, basically WSDL 2.0
>> Interface is used to describe abstract interface of a service (contract)
>> and it's common for both SOAP and REST. WSDL 2.0 Binding component describe
>> how to access above interface using a concrete protocol like SOAP , HTTP
>> etc.
>>
>> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that can be used to
>> provide required details in order to access the service using SAOP 1.1
>> protocol , WSDL 2.0 HTTP binding [2] describe details required to access
>> the service using HTTP protocol ( REST ) , in WSDL level this is the
>> mechanism to describe REST and SOAP services, I guess this make sense.
>>
>>
>> BTW each WS engine use their own techniques to distinguish SOAP and REST
>> invocations at run time , As an example Axis2 basically assume absence of
>> SAOP structure in a incoming message as a REST invocation. But this is not
>> relevant to WSDL description .
>> [1] - http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
>> [2] -
>> http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>>
>> Thanks,
>>
>> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu <mailto:
>> demetris@ece.neu.edu>> wrote:
>>
>>
>> Hi all,
>>
>> what is (or are) the particular and specific difference between
>> a SOAP serv WSDL 2.0
>> description and a REST serv WSDL 2.0 description that will make a
>> parser (or a flag
>> setter) distinguish between the two? Would the existance of the
>> keyword 'soap' in the former
>> case be such an indisputable evidence? The ports may be?
>>
>>
>> Thanks
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/><
>> http://people.apache.org/%7Esagara/>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Hi Sagara,
sorry if my original posting was a bit confusing. You are indeed
providing some good information below and in fact
I am aware of most of it. To say it in simpler terms, if a client is
retrieving WSDL files from a set of remote sites
without knowing if what they describe is a deployed service is a SOAP
service or a REST service, can the
client know by inspecting the WSDL document such a type? My feeling (and
as you may be suggesting below)
that this is not a reliable method to find such a difference as
descriptions of these services may yield identical
WSDL documents. Is this correct? But I do see that SOAP descriptions
usually carry either a SOAPAction
or a soap operation tag - is this always the case or not?
Thanks again
Sagara Gunathunga wrote:
>
> I' m not sure what is the exact problem you have here, basically WSDL
> 2.0 Interface is used to describe abstract interface of a service
> (contract) and it's common for both SOAP and REST. WSDL 2.0 Binding
> component describe how to access above interface using a concrete
> protocol like SOAP , HTTP etc.
>
> Following link [1] describe WSDL 2.0 SOAP 1.1 binding that can be
> used to provide required details in order to access the service using
> SAOP 1.1 protocol , WSDL 2.0 HTTP binding [2] describe details
> required to access the service using HTTP protocol ( REST ) , in
> WSDL level this is the mechanism to describe REST and SOAP services,
> I guess this make sense.
>
>
> BTW each WS engine use their own techniques to distinguish SOAP and
> REST invocations at run time , As an example Axis2 basically assume
> absence of SAOP structure in a incoming message as a REST invocation.
> But this is not relevant to WSDL description .
>
> [1] - http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
> [2] - http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
>
> Thanks,
>
> On Sun, May 2, 2010 at 9:34 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Hi all,
>
> what is (or are) the particular and specific difference between
> a SOAP serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will make a
> parser (or a flag
> setter) distinguish between the two? Would the existance of the
> keyword 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Sagara Gunathunga <sa...@gmail.com>.
I' m not sure what is the exact problem you have here, basically WSDL 2.0
Interface is used to describe abstract interface of a service (contract)
and it's common for both SOAP and REST. WSDL 2.0 Binding component describe
how to access above interface using a concrete protocol like SOAP , HTTP
etc.
Following link [1] describe WSDL 2.0 SOAP 1.1 binding that can be used to
provide required details in order to access the service using SAOP 1.1
protocol , WSDL 2.0 HTTP binding [2] describe details required to access
the service using HTTP protocol ( REST ) , in WSDL level this is the
mechanism to describe REST and SOAP services, I guess this make sense.
BTW each WS engine use their own techniques to distinguish SOAP and REST
invocations at run time , As an example Axis2 basically assume absence of
SAOP structure in a incoming message as a REST invocation. But this is not
relevant to WSDL description .
[1] - http://www.w3.org/TR/2007/NOTE-wsdl20-soap11-binding-20070626/
[2] - http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#http-binding
Thanks,
On Sun, May 2, 2010 at 9:34 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Hi all,
>
> what is (or are) the particular and specific difference between a SOAP
> serv WSDL 2.0
> description and a REST serv WSDL 2.0 description that will make a parser
> (or a flag
> setter) distinguish between the two? Would the existance of the keyword
> 'soap' in the former
> case be such an indisputable evidence? The ports may be?
>
>
> Thanks
>
>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Hi all,
what is (or are) the particular and specific difference between a
SOAP serv WSDL 2.0
description and a REST serv WSDL 2.0 description that will make a parser
(or a flag
setter) distinguish between the two? Would the existance of the keyword
'soap' in the former
case be such an indisputable evidence? The ports may be?
Thanks
>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Good link - thanks Arthur I will follow up on that one.
Arthur Ryman wrote:
> Demetris,
>
> I don't know of an specific endpont, However SPARQL defines a WSDL 2.0
> interace [1] so maybe there is a public SPARQL endpoint that uses it.
>
> [1] http://www.w3.org/2005/02/25-SPARQL-Prototocol/
>
> Regards,
> ___________________________________________________________________________
>
> Arthur Ryman, PhD, DE
>
>
> Chief Architect, Project and Portfolio Management
>
> IBM Software, Rational
>
> Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
> Twitter | Facebook | YouTube
>
>
>
>
>
>
>
> From:
> Demetris <de...@ece.neu.edu>
> To:
> woden-dev@ws.apache.org
> Date:
> 04/11/2010 11:18 PM
> Subject:
> Re: Examples
>
>
>
>
> Does anyone know of any public REST service(s) that is described in WSDL
> 2.0?
> I know this may be a bit of a ridiculous questions to ask but we are
> trying to exercise
> parsing of real-life WSDL files using the parts of Woden we are
> importing in mobile
> devices ...
>
> Thanks
>
> Sagara Gunathunga wrote:
>
> http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html
>
>
>> HTH
>>
>> Thanks,
>>
>> On Tue, Apr 6, 2010 at 9:22 AM, Demetris <demetris@ece.neu.edu
>> <ma...@ece.neu.edu>> wrote:
>>
>>
>> Is there a WSDL 2.0 sample for a REST and for SOAP service posted
>> anywhere?
>> I do have Laurence's example from his article but I was wondering
>> if I can a variety
>> of such documents to study so that I can work my way through the
>> Woden code a bit
>> easier.
>>
>> Thanks
>>
>> (I guess I can generate such documents by querying Axis2 engines
>>
> ...)
>
>> Sagara Gunathunga wrote:
>>
>>
>>
>> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu
>> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>> wrote:
>>
>>
>> Ok Thanks Sagara and Dilshan ---
>>
>> I guess I will need to use the lighter parsers ( I have
>> used kXML
>> once before) and do the parsing
>> my self. I am assuming needing to parse both for SOAP and
>>
> REST
>
>> descriptions will be a separate
>> project by itself but if my app is seeking only a few
>> particular
>> parts of the WSDL file it should not
>> be as bad.
>>
>> I can also look at Axis2, CXF and WSO2 even though they
>> don't use
>> mobile parsers either - just
>> to get an idea on the parsing. Will anyone working with
>> Woden fix
>> the examples that have the issues
>> I pointed out?
>>
>> User guide should be corrected now.
>>
>>
>> Are there any other examples available?
>>
>>
>> At the moment no , but if you have any specific requirement
>> please post to the list so that some one can help out. Also
>> you can refer unit tests.
>>
>> Thanks,
>>
>>
>> Thanks
>>
>> Sagara Gunathunga wrote:
>>
>> Demetris,
>>
>> AFAIK Woden is the only WSDL 2.0 parser for Java . Even
>> if you
>> could mange to run Woden on J2ME CDC, performance wise
>>
> it's
>
>> not a good option because Woden itself and XML parsers
>> used by
>> the Woden were not optimized to support J2ME CDC. IMO
>> better
>> to handle WSDL.2.0 doc in a XML level using parser like
>> KXML
>> or NanoXML .
>>
>> Thanks, On Thu, Apr 1, 2010 at 2:18 PM,
>> Dilshan Edirisuriya
>> <dilshan.ed@gmail.com <ma...@gmail.com>
>> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>
>> <mailto:dilshan.ed@gmail.com
>> <ma...@gmail.com> <mailto:dilshan.ed@gmail.com
>> <ma...@gmail.com>>>>
>>
>> wrote:
>>
>> Hi Demetris,
>>
>> Sorry Demetris I am not that familiar with J2ME
>> technologies. But
>> I feel woden will be bit heavy weight to work with
>> mobile
>> devices.
>>
>>
>>
>>
>> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
>> <demetris@ece.neu.edu <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>>> wrote:
>>
>>
>> Got it - thanks Dilshan.
>>
>> I spoke with Laurence regarding running Woden on
>> mobile
>> devices (on J2ME CDC).
>> I am getting errors on standard Java methods (ex.
>> split) so I
>> guess that test would suffice
>> that I cannot run Woden until CDC. I can look at
>> the source
>> code and see if I can figure out
>> the extend of what needs to be changed but I may
>>
> not
>
>> have the
>> time to port it. Anyone knows
>> of any mobile wsdl parsers?
>>
>> Thanks
>>
>> Dilshan Edirisuriya wrote:
>>
>> Hi Demetris,
>>
>>
>> You are correct, those user guide pages are
>> outdated. This
>> is already reported in Woden-218 [1].
>>
>> [1] -
>> https://issues.apache.org/jira/browse/WODEN-218
>>
>> Thanks ,
>>
>> Dilshan
>>
>> blog : http://dilshaned.blogspot.com/
>>
>> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
>> <demetris@ece.neu.edu
>> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu <mailto:demetris@ece.neu.edu
>>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>>>> wrote:
>>
>>
>> Hi all,
>>
>> I am learning Woden and I have simply
>> copied the
>> examples listed
>> both
>> in the User Guide and in the distribution
>> release notes - I
>> noticed a few issues
>> with the examples:
>>
>> DescriptionElement descElem =
>> reader.readWSDL(wsdlurl2); // the
>> <description>
>> element
>>
>> The above right hand side of the
>> statement returns a
>> Description
>> and NOT a DescriptionElement
>> so the compilation fails. To fix it I
>> used this
>> instead:
>>
>> Description descComp =
>> reader.readWSDL(wsdlurl2);
>> // the Description component,
>> always returned
>> DescriptionElement descElem =
>> descComp.toElement(); // the
>> <description>
>> element, if required
>>
>> Why is the original statement broken?
>>
>> Also with these statements the last one
>> fails on the
>> faults[0]:
>> InterfaceElement interfaceElem =
>> interfaces[0];
>> InterfaceFaultElement[] faults =
>> interfaceElem.getInterfaceFaultElements();
>> XmlSchemaElement xsElem =
>> faults[0].getElement();
>> To fix it I has to use:
>> XmlSchemaElement xsElem =
>> faults[0].getXmlSchemaElement();
>>
>> I am wondering if the examples are stale
>> or if I am
>> missing something.
>>
>> Thanks
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>>
>>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>>>
>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>>
>>
>>
>>
>>
>>
>> -- Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>> <http://people.apache.org/%7Esagara/>
>> <http://people.apache.org/%7Esagara/>
>> <http://people.apache.org/%7Esagara/>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org <
>>
> mailto:woden-dev-help@ws.apache.org>
>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>> <http://people.apache.org/%7Esagara/>
>> <http://people.apache.org/%7Esagara/>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>> <http://people.apache.org/%7Esagara/>
>>
>
> ---------------------------------------------------------------------
> 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: Examples
Posted by Arthur Ryman <ry...@ca.ibm.com>.
Demetris,
I don't know of an specific endpont, However SPARQL defines a WSDL 2.0
interace [1] so maybe there is a public SPARQL endpoint that uses it.
[1] http://www.w3.org/2005/02/25-SPARQL-Prototocol/
Regards,
___________________________________________________________________________
Arthur Ryman, PhD, DE
Chief Architect, Project and Portfolio Management
IBM Software, Rational
Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
Twitter | Facebook | YouTube
From:
Demetris <de...@ece.neu.edu>
To:
woden-dev@ws.apache.org
Date:
04/11/2010 11:18 PM
Subject:
Re: Examples
Does anyone know of any public REST service(s) that is described in WSDL
2.0?
I know this may be a bit of a ridiculous questions to ask but we are
trying to exercise
parsing of real-life WSDL files using the parts of Woden we are
importing in mobile
devices ...
Thanks
Sagara Gunathunga wrote:
>
http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html
>
> HTH
>
> Thanks,
>
> On Tue, Apr 6, 2010 at 9:22 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Is there a WSDL 2.0 sample for a REST and for SOAP service posted
> anywhere?
> I do have Laurence's example from his article but I was wondering
> if I can a variety
> of such documents to study so that I can work my way through the
> Woden code a bit
> easier.
>
> Thanks
>
> (I guess I can generate such documents by querying Axis2 engines
...)
>
> Sagara Gunathunga wrote:
>
>
>
> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Ok Thanks Sagara and Dilshan ---
>
> I guess I will need to use the lighter parsers ( I have
> used kXML
> once before) and do the parsing
> my self. I am assuming needing to parse both for SOAP and
REST
> descriptions will be a separate
> project by itself but if my app is seeking only a few
> particular
> parts of the WSDL file it should not
> be as bad.
>
> I can also look at Axis2, CXF and WSO2 even though they
> don't use
> mobile parsers either - just
> to get an idea on the parsing. Will anyone working with
> Woden fix
> the examples that have the issues
> I pointed out?
>
> User guide should be corrected now.
>
>
> Are there any other examples available?
>
>
> At the moment no , but if you have any specific requirement
> please post to the list so that some one can help out. Also
> you can refer unit tests.
>
> Thanks,
>
>
> Thanks
>
> Sagara Gunathunga wrote:
>
> Demetris,
>
> AFAIK Woden is the only WSDL 2.0 parser for Java . Even
> if you
> could mange to run Woden on J2ME CDC, performance wise
it's
> not a good option because Woden itself and XML parsers
> used by
> the Woden were not optimized to support J2ME CDC. IMO
> better
> to handle WSDL.2.0 doc in a XML level using parser like
> KXML
> or NanoXML .
>
> Thanks, On Thu, Apr 1, 2010 at 2:18 PM,
> Dilshan Edirisuriya
> <dilshan.ed@gmail.com <ma...@gmail.com>
> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>
> <mailto:dilshan.ed@gmail.com
> <ma...@gmail.com> <mailto:dilshan.ed@gmail.com
> <ma...@gmail.com>>>>
>
> wrote:
>
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME
> technologies. But
> I feel woden will be bit heavy weight to work with
> mobile
> devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>> wrote:
>
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on
> mobile
> devices (on J2ME CDC).
> I am getting errors on standard Java methods (ex.
> split) so I
> guess that test would suffice
> that I cannot run Woden until CDC. I can look at
> the source
> code and see if I can figure out
> the extend of what needs to be changed but I may
not
> have the
> time to port it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
> Hi Demetris,
>
>
> You are correct, those user guide pages are
> outdated. This
> is already reported in Woden-218 [1].
>
> [1] -
> https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
> <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <mailto:demetris@ece.neu.edu
>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply
> copied the
> examples listed
> both
> in the User Guide and in the distribution
> release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem =
> reader.readWSDL(wsdlurl2); // the
> <description>
> element
>
> The above right hand side of the
> statement returns a
> Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I
> used this
> instead:
>
> Description descComp =
> reader.readWSDL(wsdlurl2);
> // the Description component,
> always returned
> DescriptionElement descElem =
> descComp.toElement(); // the
> <description>
> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one
> fails on the
> faults[0]:
> InterfaceElement interfaceElem =
> interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem =
> faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem =
> faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale
> or if I am
> missing something.
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
>
>
>
>
>
> -- Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <
mailto:woden-dev-help@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
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: Examples
Posted by Demetris <de...@ece.neu.edu>.
Does anyone know of any public REST service(s) that is described in WSDL
2.0?
I know this may be a bit of a ridiculous questions to ask but we are
trying to exercise
parsing of real-life WSDL files using the parts of Woden we are
importing in mobile
devices ...
Thanks
Sagara Gunathunga wrote:
> http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html
>
> HTH
>
> Thanks,
>
> On Tue, Apr 6, 2010 at 9:22 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Is there a WSDL 2.0 sample for a REST and for SOAP service posted
> anywhere?
> I do have Laurence's example from his article but I was wondering
> if I can a variety
> of such documents to study so that I can work my way through the
> Woden code a bit
> easier.
>
> Thanks
>
> (I guess I can generate such documents by querying Axis2 engines ...)
>
> Sagara Gunathunga wrote:
>
>
>
> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Ok Thanks Sagara and Dilshan ---
>
> I guess I will need to use the lighter parsers ( I have
> used kXML
> once before) and do the parsing
> my self. I am assuming needing to parse both for SOAP and REST
> descriptions will be a separate
> project by itself but if my app is seeking only a few
> particular
> parts of the WSDL file it should not
> be as bad.
>
> I can also look at Axis2, CXF and WSO2 even though they
> don't use
> mobile parsers either - just
> to get an idea on the parsing. Will anyone working with
> Woden fix
> the examples that have the issues
> I pointed out?
>
> User guide should be corrected now.
>
>
> Are there any other examples available?
>
>
> At the moment no , but if you have any specific requirement
> please post to the list so that some one can help out. Also
> you can refer unit tests.
>
> Thanks,
>
>
> Thanks
>
> Sagara Gunathunga wrote:
>
> Demetris,
>
> AFAIK Woden is the only WSDL 2.0 parser for Java . Even
> if you
> could mange to run Woden on J2ME CDC, performance wise it's
> not a good option because Woden itself and XML parsers
> used by
> the Woden were not optimized to support J2ME CDC. IMO
> better
> to handle WSDL.2.0 doc in a XML level using parser like
> KXML
> or NanoXML .
>
> Thanks, On Thu, Apr 1, 2010 at 2:18 PM,
> Dilshan Edirisuriya
> <dilshan.ed@gmail.com <ma...@gmail.com>
> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>
> <mailto:dilshan.ed@gmail.com
> <ma...@gmail.com> <mailto:dilshan.ed@gmail.com
> <ma...@gmail.com>>>>
>
> wrote:
>
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME
> technologies. But
> I feel woden will be bit heavy weight to work with
> mobile
> devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>> wrote:
>
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on
> mobile
> devices (on J2ME CDC).
> I am getting errors on standard Java methods (ex.
> split) so I
> guess that test would suffice
> that I cannot run Woden until CDC. I can look at
> the source
> code and see if I can figure out
> the extend of what needs to be changed but I may not
> have the
> time to port it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
> Hi Demetris,
>
>
> You are correct, those user guide pages are
> outdated. This
> is already reported in Woden-218 [1].
>
> [1] -
> https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
> <demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply
> copied the
> examples listed
> both
> in the User Guide and in the distribution
> release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem =
> reader.readWSDL(wsdlurl2); // the
> <description>
> element
>
> The above right hand side of the
> statement returns a
> Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I
> used this
> instead:
>
> Description descComp =
> reader.readWSDL(wsdlurl2);
> // the Description component,
> always returned
> DescriptionElement descElem =
> descComp.toElement(); // the
> <description>
> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one
> fails on the
> faults[0]:
> InterfaceElement interfaceElem =
> interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem =
> faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem =
> faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale
> or if I am
> missing something.
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
>
>
>
>
>
> -- Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Sagara Gunathunga <sa...@gmail.com>.
http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html
HTH
Thanks,
On Tue, Apr 6, 2010 at 9:22 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Is there a WSDL 2.0 sample for a REST and for SOAP service posted
> anywhere?
> I do have Laurence's example from his article but I was wondering if I can
> a variety
> of such documents to study so that I can work my way through the Woden code
> a bit
> easier.
>
> Thanks
>
> (I guess I can generate such documents by querying Axis2 engines ...)
>
> Sagara Gunathunga wrote:
>
>>
>>
>> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu <mailto:
>> demetris@ece.neu.edu>> wrote:
>>
>>
>> Ok Thanks Sagara and Dilshan ---
>>
>> I guess I will need to use the lighter parsers ( I have used kXML
>> once before) and do the parsing
>> my self. I am assuming needing to parse both for SOAP and REST
>> descriptions will be a separate
>> project by itself but if my app is seeking only a few particular
>> parts of the WSDL file it should not
>> be as bad.
>>
>> I can also look at Axis2, CXF and WSO2 even though they don't use
>> mobile parsers either - just
>> to get an idea on the parsing. Will anyone working with Woden fix
>> the examples that have the issues
>> I pointed out?
>>
>> User guide should be corrected now.
>>
>>
>> Are there any other examples available?
>>
>>
>> At the moment no , but if you have any specific requirement please post
>> to the list so that some one can help out. Also you can refer unit tests.
>>
>> Thanks,
>>
>>
>> Thanks
>>
>> Sagara Gunathunga wrote:
>>
>> Demetris,
>>
>> AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you
>> could mange to run Woden on J2ME CDC, performance wise it's
>> not a good option because Woden itself and XML parsers used by
>> the Woden were not optimized to support J2ME CDC. IMO better
>> to handle WSDL.2.0 doc in a XML level using parser like KXML
>> or NanoXML .
>>
>> Thanks, On Thu, Apr 1, 2010 at 2:18 PM, Dilshan
>> Edirisuriya
>> <dilshan.ed@gmail.com <ma...@gmail.com>
>> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>>
>>
>> wrote:
>>
>> Hi Demetris,
>>
>> Sorry Demetris I am not that familiar with J2ME
>> technologies. But
>> I feel woden will be bit heavy weight to work with mobile
>> devices.
>>
>>
>>
>>
>> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
>> <demetris@ece.neu.edu <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>> wrote:
>>
>>
>> Got it - thanks Dilshan.
>>
>> I spoke with Laurence regarding running Woden on mobile
>> devices (on J2ME CDC).
>> I am getting errors on standard Java methods (ex.
>> split) so I
>> guess that test would suffice
>> that I cannot run Woden until CDC. I can look at the source
>> code and see if I can figure out
>> the extend of what needs to be changed but I may not
>> have the
>> time to port it. Anyone knows
>> of any mobile wsdl parsers?
>>
>> Thanks
>>
>> Dilshan Edirisuriya wrote:
>>
>> Hi Demetris,
>>
>>
>> You are correct, those user guide pages are
>> outdated. This
>> is already reported in Woden-218 [1].
>>
>> [1] - https://issues.apache.org/jira/browse/WODEN-218
>>
>> Thanks ,
>>
>> Dilshan
>>
>> blog : http://dilshaned.blogspot.com/
>>
>> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
>> <demetris@ece.neu.edu <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>>> wrote:
>>
>>
>> Hi all,
>>
>> I am learning Woden and I have simply copied the
>> examples listed
>> both
>> in the User Guide and in the distribution
>> release notes - I
>> noticed a few issues
>> with the examples:
>>
>> DescriptionElement descElem =
>> reader.readWSDL(wsdlurl2); // the
>> <description>
>> element
>>
>> The above right hand side of the statement returns a
>> Description
>> and NOT a DescriptionElement
>> so the compilation fails. To fix it I used this
>> instead:
>>
>> Description descComp =
>> reader.readWSDL(wsdlurl2);
>> // the Description component,
>> always returned
>> DescriptionElement descElem =
>> descComp.toElement(); // the
>> <description>
>> element, if required
>>
>> Why is the original statement broken?
>>
>> Also with these statements the last one fails on the
>> faults[0]:
>> InterfaceElement interfaceElem = interfaces[0];
>> InterfaceFaultElement[] faults =
>> interfaceElem.getInterfaceFaultElements();
>> XmlSchemaElement xsElem =
>> faults[0].getElement();
>> To fix it I has to use:
>> XmlSchemaElement xsElem =
>> faults[0].getXmlSchemaElement();
>>
>> I am wondering if the examples are stale or if I am
>> missing something.
>>
>> Thanks
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>>
>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>>
>>
>>
>>
>> -- Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>> <http://people.apache.org/%7Esagara/>
>> <http://people.apache.org/%7Esagara/>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/><
>> http://people.apache.org/%7Esagara/>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Is there a WSDL 2.0 sample for a REST and for SOAP service posted anywhere?
I do have Laurence's example from his article but I was wondering if I
can a variety
of such documents to study so that I can work my way through the Woden
code a bit
easier.
Thanks
(I guess I can generate such documents by querying Axis2 engines ...)
Sagara Gunathunga wrote:
>
>
> On Thu, Apr 1, 2010 at 9:50 PM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Ok Thanks Sagara and Dilshan ---
>
> I guess I will need to use the lighter parsers ( I have used kXML
> once before) and do the parsing
> my self. I am assuming needing to parse both for SOAP and REST
> descriptions will be a separate
> project by itself but if my app is seeking only a few particular
> parts of the WSDL file it should not
> be as bad.
>
> I can also look at Axis2, CXF and WSO2 even though they don't use
> mobile parsers either - just
> to get an idea on the parsing. Will anyone working with Woden fix
> the examples that have the issues
> I pointed out?
>
>
> User guide should be corrected now.
>
>
>
> Are there any other examples available?
>
>
> At the moment no , but if you have any specific requirement please
> post to the list so that some one can help out. Also you can refer
> unit tests.
>
> Thanks,
>
>
>
> Thanks
>
> Sagara Gunathunga wrote:
>
> Demetris,
>
> AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you
> could mange to run Woden on J2ME CDC, performance wise it's
> not a good option because Woden itself and XML parsers used by
> the Woden were not optimized to support J2ME CDC. IMO better
> to handle WSDL.2.0 doc in a XML level using parser like KXML
> or NanoXML .
>
> Thanks,
> On Thu, Apr 1, 2010 at 2:18 PM, Dilshan Edirisuriya
> <dilshan.ed@gmail.com <ma...@gmail.com>
> <mailto:dilshan.ed@gmail.com <ma...@gmail.com>>>
> wrote:
>
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME
> technologies. But
> I feel woden will be bit heavy weight to work with mobile
> devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on mobile
> devices (on J2ME CDC).
> I am getting errors on standard Java methods (ex.
> split) so I
> guess that test would suffice
> that I cannot run Woden until CDC. I can look at the source
> code and see if I can figure out
> the extend of what needs to be changed but I may not
> have the
> time to port it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
> Hi Demetris,
>
>
> You are correct, those user guide pages are
> outdated. This
> is already reported in Woden-218 [1].
>
> [1] - https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu <ma...@ece.neu.edu>>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply copied the
> examples listed
> both
> in the User Guide and in the distribution
> release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem =
> reader.readWSDL(wsdlurl2); // the
> <description>
> element
>
> The above right hand side of the statement returns a
> Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I used this
> instead:
>
> Description descComp =
> reader.readWSDL(wsdlurl2);
> // the Description component,
> always returned
> DescriptionElement descElem =
> descComp.toElement(); // the
> <description>
> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one fails on the
> faults[0]:
> InterfaceElement interfaceElem = interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem =
> faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem =
> faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale or if I am
> missing something.
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
> <http://people.apache.org/%7Esagara/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Thu, Apr 1, 2010 at 9:50 PM, Demetris <de...@ece.neu.edu> wrote:
>
> Ok Thanks Sagara and Dilshan ---
>
> I guess I will need to use the lighter parsers ( I have used kXML once
> before) and do the parsing
> my self. I am assuming needing to parse both for SOAP and REST
> descriptions will be a separate
> project by itself but if my app is seeking only a few particular parts of
> the WSDL file it should not
> be as bad.
>
> I can also look at Axis2, CXF and WSO2 even though they don't use mobile
> parsers either - just
> to get an idea on the parsing. Will anyone working with Woden fix the
> examples that have the issues
> I pointed out?
User guide should be corrected now.
> Are there any other examples available?
>
At the moment no , but if you have any specific requirement please post to
the list so that some one can help out. Also you can refer unit tests.
Thanks,
>
> Thanks
>
> Sagara Gunathunga wrote:
>
>> Demetris,
>>
>> AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you could mange
>> to run Woden on J2ME CDC, performance wise it's not a good option because
>> Woden itself and XML parsers used by the Woden were not optimized to support
>> J2ME CDC. IMO better to handle WSDL.2.0 doc in a XML level using parser like
>> KXML or NanoXML .
>>
>> Thanks,
>> On Thu, Apr 1, 2010 at 2:18 PM, Dilshan Edirisuriya <dilshan.ed@gmail.com<mailto:
>> dilshan.ed@gmail.com>> wrote:
>>
>> Hi Demetris,
>>
>> Sorry Demetris I am not that familiar with J2ME technologies. But
>> I feel woden will be bit heavy weight to work with mobile devices.
>>
>>
>>
>>
>> On Thu, Apr 1, 2010 at 1:08 AM, Demetris <demetris@ece.neu.edu
>> <ma...@ece.neu.edu>> wrote:
>>
>>
>> Got it - thanks Dilshan.
>>
>> I spoke with Laurence regarding running Woden on mobile
>> devices (on J2ME CDC).
>> I am getting errors on standard Java methods (ex. split) so I
>> guess that test would suffice
>> that I cannot run Woden until CDC. I can look at the source
>> code and see if I can figure out
>> the extend of what needs to be changed but I may not have the
>> time to port it. Anyone knows
>> of any mobile wsdl parsers?
>>
>> Thanks
>>
>> Dilshan Edirisuriya wrote:
>>
>> Hi Demetris,
>>
>>
>> You are correct, those user guide pages are outdated. This
>> is already reported in Woden-218 [1].
>>
>> [1] - https://issues.apache.org/jira/browse/WODEN-218
>>
>> Thanks ,
>>
>> Dilshan
>>
>> blog : http://dilshaned.blogspot.com/
>>
>> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
>> <demetris@ece.neu.edu <ma...@ece.neu.edu>
>> <mailto:demetris@ece.neu.edu
>> <ma...@ece.neu.edu>>> wrote:
>>
>>
>> Hi all,
>>
>> I am learning Woden and I have simply copied the
>> examples listed
>> both
>> in the User Guide and in the distribution release notes - I
>> noticed a few issues
>> with the examples:
>>
>> DescriptionElement descElem =
>> reader.readWSDL(wsdlurl2); // the <description>
>> element
>>
>> The above right hand side of the statement returns a
>> Description
>> and NOT a DescriptionElement
>> so the compilation fails. To fix it I used this instead:
>>
>> Description descComp = reader.readWSDL(wsdlurl2);
>> // the Description component, always returned
>> DescriptionElement descElem =
>> descComp.toElement(); // the <description>
>> element, if required
>>
>> Why is the original statement broken?
>>
>> Also with these statements the last one fails on the
>> faults[0]:
>> InterfaceElement interfaceElem = interfaces[0];
>> InterfaceFaultElement[] faults =
>> interfaceElem.getInterfaceFaultElements();
>> XmlSchemaElement xsElem = faults[0].getElement();
>> To fix it I has to use:
>> XmlSchemaElement xsElem =
>> faults[0].getXmlSchemaElement();
>>
>> I am wondering if the examples are stale or if I am
>> missing something.
>>
>> Thanks
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>> For additional commands, e-mail:
>> woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> <mailto:woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/><
>> http://people.apache.org/%7Esagara/>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Examples
Posted by Demetris <de...@ece.neu.edu>.
Ok Thanks Sagara and Dilshan ---
I guess I will need to use the lighter parsers ( I have used kXML once
before) and do the parsing
my self. I am assuming needing to parse both for SOAP and REST
descriptions will be a separate
project by itself but if my app is seeking only a few particular parts
of the WSDL file it should not
be as bad.
I can also look at Axis2, CXF and WSO2 even though they don't use mobile
parsers either - just
to get an idea on the parsing. Will anyone working with Woden fix the
examples that have the issues
I pointed out? Are there any other examples available?
Thanks
Sagara Gunathunga wrote:
> Demetris,
>
> AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you could
> mange to run Woden on J2ME CDC, performance wise it's not a good
> option because Woden itself and XML parsers used by the Woden were not
> optimized to support J2ME CDC. IMO better to handle WSDL.2.0 doc in a
> XML level using parser like KXML or NanoXML .
>
> Thanks,
>
> On Thu, Apr 1, 2010 at 2:18 PM, Dilshan Edirisuriya
> <dilshan.ed@gmail.com <ma...@gmail.com>> wrote:
>
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME technologies. But
> I feel woden will be bit heavy weight to work with mobile devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on mobile
> devices (on J2ME CDC).
> I am getting errors on standard Java methods (ex. split) so I
> guess that test would suffice
> that I cannot run Woden until CDC. I can look at the source
> code and see if I can figure out
> the extend of what needs to be changed but I may not have the
> time to port it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
> Hi Demetris,
>
>
> You are correct, those user guide pages are outdated. This
> is already reported in Woden-218 [1].
>
> [1] - https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris
> <demetris@ece.neu.edu <ma...@ece.neu.edu>
> <mailto:demetris@ece.neu.edu
> <ma...@ece.neu.edu>>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply copied the
> examples listed
> both
> in the User Guide and in the distribution release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem =
> reader.readWSDL(wsdlurl2); // the <description>
> element
>
> The above right hand side of the statement returns a
> Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I used this instead:
>
> Description descComp = reader.readWSDL(wsdlurl2);
> // the Description component, always returned
> DescriptionElement descElem =
> descComp.toElement(); // the <description>
> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one fails on the
> faults[0]:
> InterfaceElement interfaceElem = interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem = faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem =
> faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale or if I am
> missing something.
>
> Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
>
> For additional commands, e-mail:
> woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> <mailto:woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> <http://people.apache.org/%7Esagara/>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Examples
Posted by Sagara Gunathunga <sa...@gmail.com>.
Demetris,
AFAIK Woden is the only WSDL 2.0 parser for Java . Even if you could mange
to run Woden on J2ME CDC, performance wise it's not a good option because
Woden itself and XML parsers used by the Woden were not optimized to support
J2ME CDC. IMO better to handle WSDL.2.0 doc in a XML level using parser like
KXML or NanoXML .
Thanks,
On Thu, Apr 1, 2010 at 2:18 PM, Dilshan Edirisuriya <di...@gmail.com>wrote:
> Hi Demetris,
>
> Sorry Demetris I am not that familiar with J2ME technologies. But I feel
> woden will be bit heavy weight to work with mobile devices.
>
>
>
>
> On Thu, Apr 1, 2010 at 1:08 AM, Demetris <de...@ece.neu.edu> wrote:
>
>>
>> Got it - thanks Dilshan.
>>
>> I spoke with Laurence regarding running Woden on mobile devices (on J2ME
>> CDC).
>> I am getting errors on standard Java methods (ex. split) so I guess that
>> test would suffice
>> that I cannot run Woden until CDC. I can look at the source code and see
>> if I can figure out
>> the extend of what needs to be changed but I may not have the time to port
>> it. Anyone knows
>> of any mobile wsdl parsers?
>>
>> Thanks
>>
>> Dilshan Edirisuriya wrote:
>>
>>> Hi Demetris,
>>>
>>>
>>> You are correct, those user guide pages are outdated. This is already
>>> reported in Woden-218 [1].
>>>
>>> [1] - https://issues.apache.org/jira/browse/WODEN-218
>>>
>>> Thanks ,
>>>
>>> Dilshan
>>>
>>> blog : http://dilshaned.blogspot.com/
>>>
>>> On Wed, Mar 31, 2010 at 10:51 AM, Demetris <demetris@ece.neu.edu<mailto:
>>> demetris@ece.neu.edu>> wrote:
>>>
>>>
>>> Hi all,
>>>
>>> I am learning Woden and I have simply copied the examples listed
>>> both
>>> in the User Guide and in the distribution release notes - I
>>> noticed a few issues
>>> with the examples:
>>>
>>> DescriptionElement descElem = reader.readWSDL(wsdlurl2);
>>> // the <description> element
>>>
>>> The above right hand side of the statement returns a Description
>>> and NOT a DescriptionElement
>>> so the compilation fails. To fix it I used this instead:
>>>
>>> Description descComp = reader.readWSDL(wsdlurl2);
>>> // the Description component, always returned
>>> DescriptionElement descElem = descComp.toElement();
>>> // the <description> element, if required
>>>
>>> Why is the original statement broken?
>>>
>>> Also with these statements the last one fails on the faults[0]:
>>> InterfaceElement interfaceElem = interfaces[0];
>>> InterfaceFaultElement[] faults =
>>> interfaceElem.getInterfaceFaultElements();
>>> XmlSchemaElement xsElem = faults[0].getElement();
>>> To fix it I has to use:
>>> XmlSchemaElement xsElem = faults[0].getXmlSchemaElement();
>>>
>>> I am wondering if the examples are stale or if I am missing something.
>>>
>>> Thanks
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>>
>>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
Re: Examples
Posted by Dilshan Edirisuriya <di...@gmail.com>.
Hi Demetris,
Sorry Demetris I am not that familiar with J2ME technologies. But I feel
woden will be bit heavy weight to work with mobile devices.
On Thu, Apr 1, 2010 at 1:08 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Got it - thanks Dilshan.
>
> I spoke with Laurence regarding running Woden on mobile devices (on J2ME
> CDC).
> I am getting errors on standard Java methods (ex. split) so I guess that
> test would suffice
> that I cannot run Woden until CDC. I can look at the source code and see if
> I can figure out
> the extend of what needs to be changed but I may not have the time to port
> it. Anyone knows
> of any mobile wsdl parsers?
>
> Thanks
>
> Dilshan Edirisuriya wrote:
>
>> Hi Demetris,
>>
>>
>> You are correct, those user guide pages are outdated. This is already
>> reported in Woden-218 [1].
>>
>> [1] - https://issues.apache.org/jira/browse/WODEN-218
>>
>> Thanks ,
>>
>> Dilshan
>>
>> blog : http://dilshaned.blogspot.com/
>>
>> On Wed, Mar 31, 2010 at 10:51 AM, Demetris <demetris@ece.neu.edu <mailto:
>> demetris@ece.neu.edu>> wrote:
>>
>>
>> Hi all,
>>
>> I am learning Woden and I have simply copied the examples listed
>> both
>> in the User Guide and in the distribution release notes - I
>> noticed a few issues
>> with the examples:
>>
>> DescriptionElement descElem = reader.readWSDL(wsdlurl2); //
>> the <description> element
>>
>> The above right hand side of the statement returns a Description
>> and NOT a DescriptionElement
>> so the compilation fails. To fix it I used this instead:
>>
>> Description descComp = reader.readWSDL(wsdlurl2);
>> // the Description component, always returned
>> DescriptionElement descElem = descComp.toElement();
>> // the <description> element, if required
>>
>> Why is the original statement broken?
>>
>> Also with these statements the last one fails on the faults[0]:
>> InterfaceElement interfaceElem = interfaces[0];
>> InterfaceFaultElement[] faults =
>> interfaceElem.getInterfaceFaultElements();
>> XmlSchemaElement xsElem = faults[0].getElement();
>> To fix it I has to use:
>> XmlSchemaElement xsElem = faults[0].getXmlSchemaElement();
>>
>> I am wondering if the examples are stale or if I am missing something.
>>
>> Thanks
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>>
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> <ma...@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: Examples
Posted by Demetris <de...@ece.neu.edu>.
Got it - thanks Dilshan.
I spoke with Laurence regarding running Woden on mobile devices (on J2ME
CDC).
I am getting errors on standard Java methods (ex. split) so I guess that
test would suffice
that I cannot run Woden until CDC. I can look at the source code and see
if I can figure out
the extend of what needs to be changed but I may not have the time to
port it. Anyone knows
of any mobile wsdl parsers?
Thanks
Dilshan Edirisuriya wrote:
> Hi Demetris,
>
>
> You are correct, those user guide pages are outdated. This is already
> reported in Woden-218 [1].
>
> [1] - https://issues.apache.org/jira/browse/WODEN-218
>
> Thanks ,
>
> Dilshan
>
> blog : http://dilshaned.blogspot.com/
>
> On Wed, Mar 31, 2010 at 10:51 AM, Demetris <demetris@ece.neu.edu
> <ma...@ece.neu.edu>> wrote:
>
>
> Hi all,
>
> I am learning Woden and I have simply copied the examples listed
> both
> in the User Guide and in the distribution release notes - I
> noticed a few issues
> with the examples:
>
> DescriptionElement descElem = reader.readWSDL(wsdlurl2);
> // the <description> element
>
> The above right hand side of the statement returns a Description
> and NOT a DescriptionElement
> so the compilation fails. To fix it I used this instead:
>
> Description descComp = reader.readWSDL(wsdlurl2);
> // the Description component, always returned
> DescriptionElement descElem = descComp.toElement();
> // the <description> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one fails on the faults[0]:
> InterfaceElement interfaceElem = interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem = faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem = faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale or if I am missing something.
>
> Thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: woden-dev-help@ws.apache.org
> <ma...@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: Examples
Posted by Dilshan Edirisuriya <di...@gmail.com>.
Hi Demetris,
You are correct, those user guide pages are outdated. This is already
reported in Woden-218 [1].
[1] - https://issues.apache.org/jira/browse/WODEN-218
Thanks ,
Dilshan
blog : http://dilshaned.blogspot.com/
On Wed, Mar 31, 2010 at 10:51 AM, Demetris <de...@ece.neu.edu> wrote:
>
> Hi all,
>
> I am learning Woden and I have simply copied the examples listed both
> in the User Guide and in the distribution release notes - I noticed a few
> issues
> with the examples:
>
> DescriptionElement descElem = reader.readWSDL(wsdlurl2); // the
> <description> element
>
> The above right hand side of the statement returns a Description and NOT a
> DescriptionElement
> so the compilation fails. To fix it I used this instead:
>
> Description descComp = reader.readWSDL(wsdlurl2); // the
> Description component, always returned
> DescriptionElement descElem = descComp.toElement(); // the
> <description> element, if required
>
> Why is the original statement broken?
>
> Also with these statements the last one fails on the faults[0]:
> InterfaceElement interfaceElem = interfaces[0];
> InterfaceFaultElement[] faults =
> interfaceElem.getInterfaceFaultElements();
> XmlSchemaElement xsElem = faults[0].getElement();
> To fix it I has to use:
> XmlSchemaElement xsElem = faults[0].getXmlSchemaElement();
>
> I am wondering if the examples are stale or if I am missing something.
>
> Thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>