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

Servus Status

Revision as of 17:25, 25 July 2008 by Ttonelli.swen.uwaterloo.ca (Talk | contribs) (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. ...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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