M2Flex - Version 1.3.2
Model2Code.com is proud to announce that M2Flex 1.3.2 is now available for download. Version 1.3.2 includes new and enhanced modeling and generation capabilities.
Release Note M2Flex version 1.3.2 - New features
Process Diagrams Generation Enhancement:
- Generated code Optimization (11kb vs 98kb)
- Before -> factorization of every possible path implying code duplication
- Now -> Smart scanning of the paths using the sequential and/or overlapped “if”
Exceptions refactoring & logging system:
- Trace persistence, service and web layer
- Exceptions hierarchy
- Error page redirection added
Flex enhancement (Generated frameworks):
- Data validation:
- Constraints’ modeling within the entities and associated error messages
- Internationalization keys generation of error messages (« properties » files by local)
- Validators generation by entity (.as files)
- Evolution on the « Model Locator » (may require the mock-ups review)
- Singleton deletion
- Adding a method that allows to copy only the instances modified for each event (« CopyMethodeForEvent » method)
- Modification of the event management methods signature in order to include a reference of the screen instance, as well as a optional « callBack »
Deletion of the SPRING schemas in the generated projects:
- The XSD paths are now defined according to the SPRING jar classpath.
FLEX CRUD Booster Iteration I:
- FLEX mock-up generation from the entities and UML diagrams generated by the Bluage CRUD PAGES wizard for MagicDraw.
- Using the com.netfective.bluage.bsp.j2ee.flexBooster BSP that generates for each entity the following Mxml files:
- menuEntity.mxml
- AddEntity.mxml
- updateEntity.mxml
- listeEntity.mxml
- detailsEntity.mxml
- Application’s principal menu and home page generation.
- An AS file is associated to each generated mxml file. The AS file is referenced in the mxml file and includes the entire page’s Action Script code.
Workflow Files Versioning:
- The "Workflow" files have a new property: Workflow Version
- The workflow version allows knowing if the version for which the “workflow” has been written matches with the generator’s version.