WSMX started being driven by the need to have a semantic
execution environment capable to consume semantic messages,
discover semantically described web services, invoke and
compose them for the end-user benefit. On the way, many
components have been added, to provide support for the main
scope of the execution environment.
Another reason to build such an execution environment
was the need to have a functional service open architecture
prototype, able to encapsulate new components with new
functionalities. Components reusability was another key
feature aimed by WSMX, as reusability and generic
functionality are core concepts that guide WSMX
development.