| [mddi-dev] ModelBus Adapter Release 0.3 |
|
Sorry for multiple copies. We would like to re-announce the ModelBus V0.3
release within MDDI. The new User Guide is already available and can be found
in the org.eclipse.mddi.modelbus.adapter.doc CVS
module. The documentation is almost completed. The only missing part is an advanced topic concerning
customization of ModelBus protocol (custom serializers). Best
regards and Happy New Year, Andrey ------------------------------ Andrey
SADOVYKH, Ph. D. LIP6-SRC
ModelWare team Phone:
+33.1.44.27.87.62 Mail :
---------------------------------------------------------------------------------------------------------------- We are pleased to announce an intermediate release of
the ModelBus adapter. As it was decided during WP3 meeting, all
intermediate releases are accessible by CVS only. The text hereafter describes how to access the CVS
and what is in the new release. Anonymous CVS Access ==================== CVS repository can be checked out through anonymous
(pserver) CVS with the following instruction set. The module you wish to check
out must be specified as the modulename (if you don't know which module is
defined or if no module is set, just remplace modulename by .). Modules
that correspond to the ModelBus release begins with org.eclipse.mddi.modelbus When prompted for a password for anonymous, simply
press the Enter key. cvs
-d:pserver:anonymous@xxxxxxxxxxxxxxxxxxxxxxx:/cvsroot/modfact login cvs -z3
-d:pserver:anonymous@xxxxxxxxxxxxxxxxxxxxxxx:/cvsroot/modfact co modulename Updates from within the module's directory do not
need the -d parameter. Release Notes - ModelBus Adapter V0.3 ================================ ModelBus Adapter is purposed to simplify integration
of modeling tools with ModelBus. Adapter includes an API, as well as complete ModelBus
infrastructure. New in this release =============== * Architecture was restructured in order to clearly
separate user API and ModelBus infrastructure. * Transport service was redesigned * Server deployment flexibility, possibility to
deploy ModelBus to custom servers. * EndPoint management, possibility to reuse ModelBus
transport for non-modelbus services (see notification and BasicRegistry) * Marhaling, possibility to plug custom marshalers
and in this way customize ModelBus protocol (see sessions). * Serialization, possibility to redefine and plug
custom serializers * ToolSelection Strategy, possibility to redefine and
plug custom ToolSelection strategies * UML2 Profiles support, possibility to exchange UML2
Models with Profiles * Session support * Tomcat server support * SimpleWeb server dependency was completely removed. Limitations =========== * Serializers operate with Objects to Stings. Stream
Interface will come next * Tool Selection Strategy interface contains a method
to select a Tool depending service name only. An interface that takes into
account call parameters will come next. * UML2 Profiles should be loaded on the both
communicating sides in order to allow exchanging of models with profiles. |