|
MetaBoss Change Log
This document is the official log of MetaBoss's development progress.
In addition to this log, file changes.log
contains more granular (and more tech speak) log of all changes and bug fixes.
Release 1.4 (25 October 2005)
- Added ability to model Event Subscriptions - the unsolicited asyncroneous messages
produced by servers and consumed by clients. This addition required changing the Enterprise MetaModel
,which made XMI Reader incompatible with previous versions (see release notes for the instructions how to modify existing Model XMI file to
make it readable by MetaBoss 1.4.xxxx). This incompatibility is also the reason why
product minor version number has been incremented.
Release 1.3 (01 June 2005)
- Added ability to import and keep many DataDictionaries in the Enterprise. This
paves the way for importing industry specific dictionaries such as FIX, RIXML etc.
This addition required changing the Enterprise MetaModel, which made XMI Reader incompatible with
previous versions (see release notes for the instructions how to modify existing Model XMI file to
make it readable by MetaBoss 1.3.xxxx). This incompatibility is also the reason why
product minor version number has been incremented.
Release 1.2 (28 April 2005)
- Added the facility to study dependencies between model elements in the Design studio. This facility is based on displaying
an interactive diagram of the dependencies between components. Implemented with use of Prefuse Interactive Visualization Toolkit.
Release 1.1 (23 February 2005)
- Introduced support for constraints expressed in OCL (Object Constraint Language). Implemented with use of Dresden OCL toolkit.
- Created The MetaBoss Beginners Guide based on small example. It takes novice user from
design and modelling through to building, deploying and testing the system.
- Moved to Java SE SDK 1.4.2_05
- Moved to JWSDP 1.5
Release 1.0 (26 August 2004)
- Added support for XPath searches in the model repository. Implemented with use of Jaxen 1.0 FCS
- Added support for MySQL (Release 4.1.1 alpha) database. Any earlier release of MySQL does not cut it because there
is no support for subqueries.
- Moved to jgraph-3.4.1
- Implemented validation of the test scenario outcome against specimen test scenario log. This facility is intended for
regression testing. It basically highlights all the differences between current test run and the past (ie. trusted) test run.
- Introduced first version of Model Documentation Generator.
- Introduced licensing mechanism, which includes configurrable authorship properties.
- Move to NetBeans MDR. The model BO library has been replaced by MDR. MetaBoss is now
100% JMI and MOF compliant.
Release 0.5 (20 January 2004)
- Allowed single inheritance between entities within one domain.
- Added Transaction Management proxy generation. This proxy is able to provide J2EE
style transaction management in environments where J2EE container is not present (e.g. CORBA).
- Improved SQL Selector Text macro language, so it has more keywords and more possibilities.
- Introduced more tests into the MetaBoss post-build regression test.
- Moved to Java SE SDK 1.4.2_03.
Release 0.4 (05 December 2003)
- Added first release of the testing framework. MetaBossSystemTester is able to run any combination of test cases
defined in XML. The examples directory in the resease includes sample XML test definitions, and files and
and batch files used to run it.
- It is now possible for the template to lookup components via template context passed to it.
So far it is only available for Java template and Jamon template. Needs some work to make it available for velocity.
- Integrated yet another templating mechanism - Jamon. So we now have three types of templates and catering for
many different tastes.
- JNDI Component Context is now able to discover and dynamically load component implementations from
components implementation path (java system property). This is the base for MetaBoss tools extension framework.
- Added XML-oriented adapter generators.
These type of enterprise system adapters can be used with DOM Elements or even Strings with XML documents in them.
Release 0.3 (20 October 2003)
- Expanded instance id column definition to include entity type. This should make future realisation of
domain business object inheritance mechanism easier.
- Added Apache Struts Integration solution. This tightly integrates Struts form validation framework with
"selfvalidating" feature of the MetaBoss datatypes.
- Added CanUseForOrdering element to the AttributeDef element (in EnterpriseModel).
CanUseForOrdering is a boolean attribute, which specifies whether entity collection can be sorted on this attribute.
- Added OperationTransactionPolicy element to the OperationDef element (in EnterpriseModel).
OperationTransactionPolicy allows to specify operation's transaction policy in terms quite similar to J2EE.
- Introduced Storage Model - the model which captures storage technologies and
realisations of storage for particular domains.
- Reworked DataTypes framework to formalise data type translation to / from primitive, sql and xml types.
This has removed getPrimitiveValue() getXMLValue() etc methods from DataType signatures, so
some implementation code may need rectifying. It has been well flagged in prior relases that
the "system level" translator methods should not be used.
Release 0.2 (12 August 2003)
- Moved XML technology to use Sun's Java Web Services Development Pack Ver 1.1
(the last version for Java 1.3.x).
- Published Enterprise Model schema.
Release 0.1 (5 August 2003)
This is the first official release, which marks the beginning of this log.
|
Copyright © 2000-2005 Softaris Pty.Ltd. All Rights Reserved. MetaBoss is the registered trademark of Softaris Pty.Ltd. Java, Enterprise JavaBeans, JDBC, JNDI, JTA, JTS, JCA and other Java related APIs are trademarks or registered trademarks of Sun Microsystems, Inc. MDA, UML, MOF, CORBA and IIOP are trademarks or registered trademarks of the Object Management Group. Microsoft, .NET and C# are trademarks or registered trademarks of the Microsoft Corporation. All other product names mentioned herein are trademarks of their respective owners.
|
|