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.
Difference between revisions of "ALF/architecture/ALF Schemas 1"
(→Introduction) |
|||
| Line 19: | Line 19: | ||
4. The concept of "User" has been simplified to an extensible "credentials" type. There is now no assumption that a user will be represented by a name, login and password. | 4. The concept of "User" has been simplified to an extensible "credentials" type. There is now no assumption that a user will be represented by a name, login and password. | ||
| − | 5. The need to deflare derived types and services to allow tools to decfine their events has been addressed. The declared services, the event manager and the example service flow services, have been changed to use WS-I complient RPC Literal style. Previously, Document Literal style was prefered but that proved problematic for type overloading. The details are discussed under Vocabularies section[http://wiki.eclipse.org/index.php/ALF/Vocabularies/Event_Declaration_Schema Event Declaration Schema]. | + | 5. The need to deflare derived types and services to allow tools to decfine their events has been addressed. The declared services, the event manager and the example service flow services, have been changed to use WS-I complient RPC Literal style. Previously, Document Literal style was prefered but that proved problematic for type overloading. The details are discussed under Vocabularies section ([http://wiki.eclipse.org/index.php/ALF/Vocabularies/Event_Declaration_Schema Event Declaration Schema]). |
NOTE: While the schema and WSDL are valsi an WS-I complient we have discovered that curent versions of some web service tools have limitations that mean they cannot consume the WSDL and Schema. These problems are mostly to do with the use of restricting facets (eg: attributes such as minOccurs="0") Given this we may need to make some minor adjustments to the schema before it is final. | NOTE: While the schema and WSDL are valsi an WS-I complient we have discovered that curent versions of some web service tools have limitations that mean they cannot consume the WSDL and Schema. These problems are mostly to do with the use of restricting facets (eg: attributes such as minOccurs="0") Given this we may need to make some minor adjustments to the schema before it is final. | ||
Revision as of 20:42, 6 February 2007
Introduction
ALF Event Manager Schemas and WSDL version 1
WARNING: THIS PAGE IS BEING CONSTRUCTED. THE INFORMATION IT CONTAINS IS PRELIMINARY
The proposed version 1 ALF Event schema is presented below.
Some of the features to note are:
1. The provision for extension and versioning using nested "Extension" elements. The approach pursued is based primarily on the recommendations of this article, "Extensibility, XML Vocabularies, and XML Schema" by David Orchard[1]
2. The refactoring of the BaseEvent to divide it into two parts; the part normally set by the tool raising the event and the part normally set by the alf event manager. The primary motivation for this is to establish a structure of elements that can be passed on to the services of "alf compliant" tools. The needs of this structure correspond to those elements that are normally set by the event manager.
3. There are various name changes and a few additional fields
4. The concept of "User" has been simplified to an extensible "credentials" type. There is now no assumption that a user will be represented by a name, login and password.
5. The need to deflare derived types and services to allow tools to decfine their events has been addressed. The declared services, the event manager and the example service flow services, have been changed to use WS-I complient RPC Literal style. Previously, Document Literal style was prefered but that proved problematic for type overloading. The details are discussed under Vocabularies section (Event Declaration Schema).
NOTE: While the schema and WSDL are valsi an WS-I complient we have discovered that curent versions of some web service tools have limitations that mean they cannot consume the WSDL and Schema. These problems are mostly to do with the use of restricting facets (eg: attributes such as minOccurs="0") Given this we may need to make some minor adjustments to the schema before it is final.