Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Servus Status"

(New page: = Limitations = Current limitations of the transformations and models. == WSDLv1 to Ecore == * if there are 2 <definitions> with the same ''targetNamespace'', they are merged in Ecore. ...)
 
Line 1: Line 1:
= Limitations =
+
This page lists:
 +
 
 +
* [[#Features | Features]] - a list of features we plan to implement and the current status of the implementation.
 +
* [[#Conceptual Limitations | Conceptual Limitations]] - conceptual limitations of the current implementation.
 +
 
 +
= Features =
 +
 
 +
== WSDLv1 to Ecore ==
 +
 
 +
* basic implementation is working, with the following limitations:
 +
** only the ''full'' representation can be generated
 +
** there are no semantic checks (can transform ''incorrect'' WSDLs)
 +
** it is not tested on a large WSDL code base
 +
** it's form is not stable yet (we're refining the annotations)
 +
 
 +
== Ecore to WSDLv1 ==
 +
 
 +
* in development
 +
 
 +
== Ecore to JAX-WS ==
 +
 
 +
* in development
 +
 
 +
== CXF Databinding ==
 +
 
 +
* development has <font color="red">not</font> started.
 +
 
 +
= Conceptual Limitations =
  
 
Current limitations of the transformations and models.
 
Current limitations of the transformations and models.

Revision as of 17:31, 25 July 2008

This page lists:

  • Features - a list of features we plan to implement and the current status of the implementation.
  • Conceptual Limitations - conceptual limitations of the current implementation.

Features

WSDLv1 to Ecore

  • basic implementation is working, with the following limitations:
    • only the full representation can be generated
    • there are no semantic checks (can transform incorrect WSDLs)
    • it is not tested on a large WSDL code base
    • it's form is not stable yet (we're refining the annotations)

Ecore to WSDLv1

  • in development

Ecore to JAX-WS

  • in development

CXF Databinding

  • development has not started.

Conceptual Limitations

Current limitations of the transformations and models.

WSDLv1 to Ecore

  • if there are 2 <definitions> with the same targetNamespace, they are merged in Ecore. The name of an arbitrary <definitions> is used.
  • it is not possible to generate multiple ecore files for the Servus Models (the whole WSDL chain is put into a single Servus Model). That's because the mapping becomes complicated (we would have to create mock EClasses to attach annotations. For example, if one file has the SEI but another file has the WebEndpoint annotation).

Servus Models

  • it is not possible to create the Servus Model in the same ecore model as the Data Models. That's because it makes it difficult to generate the schema for just a portion of the EClasses (we would have to look for EClasses and DataTypes being used as parameters and return types and generate a schema only for them).

Back to the top