| WSDL model APIs [message #62530] |
Thu, 06 January 2005 22:35  |
Eclipse User |
|
|
|
Originally posted by: not_real.not_real.com
Hi,
I was wondering if the WSDL model API and implementation (found in
org.eclipse.wst.wsdl) will continue to be offered as public API for use
by third party extensions. I'm trying to decide whether or not I should
depend on it for WSDL manipulation. Can anyone shed light on this?
Thanks.
|
|
|
|
| Re: WSDL model APIs [message #63070 is a reply to message #62600] |
Fri, 07 January 2005 17:25  |
| Eclipse User |
|
|
|
Originally posted by: not_real.not_real.com
Thank you for your reply. I would like to use the WSDL model in order
to examine and possibly manipulate WSDLs. The features I am interested
in in particular are:
1. Resolution of references, including cross document references (ie.
operation.getInput() returns message instance and not a QName).
2. Extensibility -- I would like to extend the model with a few WSDL
extensions.
3. Fine grained events when WSDLs change(might be able to live without
these).
The WebTools WSDL model seem to take care of all of the above except for
possibly #2; I need to dig deeper to figure out if/how this can be done.
Do you have a rough idea of when the WSDL model API will be finalized?
Do you anticipate that it will change much?
Thanks!
Lawrence Mandel wrote:
>>I was wondering if the WSDL model API and implementation (found in
>>org.eclipse.wst.wsdl) will continue to be offered as public API for use
>>by third party extensions. I'm trying to decide whether or not I should
>>depend on it for WSDL manipulation. Can anyone shed light on this?
>
>
> For those reading this, org.eclipse.wst.wsdl contains an EMF WSDL 1.1
> model.
>
> The API for the WTP project should not be considered final at this point
> as it may change over the next couple milestones. The WTP project does aim
> to provide reusable components to the Eclipse commmunity so you will be
> able to depend on the WSDL model API once it is finalized. Can you post a
> summary of how you would like to use the model in order to help the
> developers decide what should be exposed in the API?
>
> Alternatively, if you're looking for a lightweight WSDL model you may want
> to take a look at WSDL4J. See
> http://www-124.ibm.com/developerworks/projects/wsdl4j/. There are plugins
> in the WTP project which rely on this model for
> performance/simplicity/requirements reasons.
>
>
> Lawrence
|
|
|
|
| Re: WSDL model APIs [message #63265 is a reply to message #63106] |
Fri, 07 January 2005 20:33 |
| Eclipse User |
|
|
|
Originally posted by: not_real.not_real.com
Yes, the XML schema references are very cool, and something that I am
very interested in using. Thanks for your response!
Craig Salter wrote:
> ka wrote:
>
>> Thank you for your reply. I would like to use the WSDL model in order
>> to examine and possibly manipulate WSDLs. The features I am
>> interested in in particular are:
>> 1. Resolution of references, including cross document references (ie.
>> operation.getInput() returns message instance and not a QName).
>> 2. Extensibility -- I would like to extend the model with a few WSDL
>> extensions.
>> 3. Fine grained events when WSDLs change(might be able to live without
>> these).
>> The WebTools WSDL model seem to take care of all of the above except
>> for possibly #2; I need to dig deeper to figure out if/how this can be
>> done.
>
>
> The WSDL model supports all three features that you list above. You'll
> notice that we provide SOAP and HTTP extensibility models that should
> demonstrate #2. You may be interested in knowing that for #1 we also
> provide cross document references to XML Schema objects (to the eclipse
> XSD model).
>
>> Do you have a rough idea of when the WSDL model API will be finalized?
>> Do you anticipate that it will change much?
>
>
> I don't anticipate too much change. Having folks use our model would
> help us understand what we need to expose as API (currently much of the
> code is marked 'internal' ... and we assume you won't need to touch
> that... but we're probably wrong in some cases). So I'd ecourage you
> to start using it. I'm guessing we'll be ready to finalize the API some
> time in March (depending on how much feed back we've received).
>
> Thanks for your interest. Please continue to post questions, comments
> and (of course) bug reports.
|
|
|
Powered by
FUDForum. Page generated in 0.03994 seconds
] 
Search
Help
Register
Login
Home
