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 <sagara.gunathu...@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 <demet...@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 <demet...@ece.neu.edu <mailto:
demet...@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...@gmail.com <mailto:dilshan...@gmail.com>
       <mailto:dilshan...@gmail.com <mailto:dilshan...@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
       <demet...@ece.neu.edu <mailto:demet...@ece.neu.edu>
          <mailto:demet...@ece.neu.edu
       <mailto:demet...@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
                  <demet...@ece.neu.edu <mailto:demet...@ece.neu.edu>
       <mailto:demet...@ece.neu.edu <mailto:demet...@ece.neu.edu>>
                  <mailto:demet...@ece.neu.edu
       <mailto:demet...@ece.neu.edu>
                  <mailto:demet...@ece.neu.edu
       <mailto:demet...@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-unsubscr...@ws.apache.org
       <mailto:woden-dev-unsubscr...@ws.apache.org>
                  <mailto:woden-dev-unsubscr...@ws.apache.org
       <mailto:woden-dev-unsubscr...@ws.apache.org>>
                     <mailto:woden-dev-unsubscr...@ws.apache.org
       <mailto:woden-dev-unsubscr...@ws.apache.org>
                  <mailto:woden-dev-unsubscr...@ws.apache.org
       <mailto:woden-dev-unsubscr...@ws.apache.org>>>

                     For additional commands, e-mail:
                  woden-dev-h...@ws.apache.org
       <mailto:woden-dev-h...@ws.apache.org>
                  <mailto:woden-dev-h...@ws.apache.org
       <mailto:woden-dev-h...@ws.apache.org>>
                     <mailto:woden-dev-h...@ws.apache.org
       <mailto:woden-dev-h...@ws.apache.org>
                  <mailto:woden-dev-h...@ws.apache.org
       <mailto:woden-dev-h...@ws.apache.org>>>



---------------------------------------------------------------------
              To unsubscribe, e-mail:
       woden-dev-unsubscr...@ws.apache.org
       <mailto:woden-dev-unsubscr...@ws.apache.org>
              <mailto:woden-dev-unsubscr...@ws.apache.org
       <mailto:woden-dev-unsubscr...@ws.apache.org>>
              For additional commands, e-mail:
       woden-dev-h...@ws.apache.org <mailto:woden-dev-h...@ws.apache.org>
              <mailto:woden-dev-h...@ws.apache.org
       <mailto:woden-dev-h...@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-unsubscr...@ws.apache.org
   <mailto:woden-dev-unsubscr...@ws.apache.org>
   For additional commands, e-mail: woden-dev-h...@ws.apache.org
   <mailto:woden-dev-h...@ws.apache.org>





---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscr...@ws.apache.org
For additional commands, e-mail: woden-dev-h...@ws.apache.org

Reply via email to