Thanks a lot John.
My main need is to be able to:
* load a wsdl from a Document
* locate the service for a specified qname
* find the associated binding type
* find the associated interface name
So i'll keep a look and give you feedback as soon as M2 is out, or svn
head can fullfill some part of it.
Cheers,
Guillaume Nodet
John Kaputin wrote:
Hi Guillaume,
other readWSDL methods will be added to the WSDLReader interface, probably
similar to the readWSDL methods in the WSDL 1.1 processor, WSDL4J. This
includes a readWSDL method that takes a DOM Document. I have net yet
focussed on the other readWSDL methods required, but I can add easily add
the Document argument readWSDL method.
We have just revised the milestone plan and will update the web page
shortly. M2 is now due Dec 2nd. It still delivers Binding components,
including support for extensibility because this is required for the
mandatory extensions (SOAP and HTTP bindings). M2 will include the SOAP
extensions. HTTP bindings will follow in M3 due Jan 20. M3 is largely about
validation, but it does currently include the Service component. However,
there is not much to Service so I can do it sooner rather than later.
I will aim to meet your first objective (reading a wsdl2 description from a
DOM document) by M2 in 3 weeks time - including the Service component. The
wsdl 1.1. conversion will take longer and we have a couple of people lined
up to work on this, but let us know if you have something to contribute.
The design and implementation of Woden are maturing rapidly and should be
stable enough by M2 for others to use as a base to build upon. I'm
currently working on the Binding components and would prefer to complete
that myself to maintain consistency. This should ensure a common baseline
for reviewing the design and implementation. But there's plenty more to do
beyond Binding and Service, so M2 would probably be a good point to get
involved with functional development if you're interested.
In the meantime we could really use some help with testing what we have.
Perhaps you could try using it against your own WSDL documents. Or create
WSDL testcases based on the W3C WSDL 2.0 spec (and ideally contribute any
WSDL to the [EMAIL PROTECTED] mailing list so the W3C working group can
add it to their WSDL 2.0 test suite). And let us know if the Woden API
meets your functional and usability needs - contributing suggestions or
code as you like. To get the Binding and Service functionality as I
complete it, you should use the latest code from the Subversion repository.
Other Woden objectives beyond the core WSDL 2.0 parsing are:
* WSDL 1.1 to 2.0 conversion
* API support for the wsdl 1.1. model (e.g. via the JWSDL API from JSR110)
* WSDLWriter functionality for modifying or programmatically creating WSDL
documents.
* support for other XML parsers (e.g. JSR173 StAX)
* support for other type systems besides XML Schema.
regards,
John Kaputin
Guillaume Nodet
<[EMAIL PROTECTED]
> To
[email protected]
08/11/2005 10:46 cc
Subject
Please respond to Status and help proposal
woden-dev
Hi everybody.
I'm working on servicemix (http://servicemix.org), a JBI container.
The JBI specs mandates the use of wsdl 2.0 and we currently handle only
wsdl 1.
So i'm looking for something to read (maybe write) wsdl 2.
I need the following features:
* read wsdl 2 documents from an existing dom Document
* read wsdl 1 would be very handy, else i'll have to have two
libraries and check before what wsdl version it is
From what i understand, and what i saw, the api does not have any mean
to read a wsdl from an existing doc.
It should be very easy to add, as the parser already uses dom (just
missing in the api, i think). Having lots of ways
to read wsdls is a real need, imho (maybe reading from a jaxp source
could handle most of the cases).
The parsing currently does not read the full wsdl (binding among other
things is not parsed yet).
I do not need complete validation aso, but i need to retrieve at least
basic informations.
I've seen on the mailing list that someone will work on the wsdl 1.1 ->
2.0 conversion.
From the milestone plan, it seems that you are focusing on parsing
binding first (M2), then services (M3).
As for me, i'd prefer to be able to parse the whole wsdl, even if some
data is not handled (extensibility elements
for example), but ...
Thus, i'm willingfull to offer my help so that i could use woden in
servicemix.
Cheers,
Guillaume Nodet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
