Hello everyone
CLD 1.5.0.S74 of edoras one is now available:
https://confluence.edorasware.com/display/EDWDEV/CLD+1.5.0.S74
In the release 1.5.0.S74 we focused on the security of edoras one and we were able to fix a lot of security issues regarding XSS, cookies, XML etc.
1.5.0.S74 release introduces new modeler validation and clipboard enhancements. The validation feedback is shown in the new Validation details tab displayed at the bottom of
the designer view when the validation operation is invoked.
Besides the things mentioned above, we have added various small improvements and many fixes.
Regards,
edoras one team
High-level Goals
- Improve security
- Improve display of warnings in vis designer view
- Usability improvement in Form design clipboard operations
Migration Notes
- In the vis-handler-config.xml add bean declaration for the class com.edorasware.user.handler.UserConfigHandler with id='userConfigHandler'
- In the vis-handler-config.xml add bean declaration for the class com.edorasware.one.service.UserConfigurationService with id='userConfigurationService'
- In the vis-handler-config.xml remove the bean declaration for the class com.edorasware.encrypt.handler.PasswordEncrypterHandler
- The propertyPlaceholder-config.xml has been removed and the new property placeholder is configured in the edoras-one-hosted module. This means that each project which does not use the edoras-one-hosted module, needs to add a property placeholder with the proper properties. All the properties are listed in the one-hosted.properties file in the edoras-one-hosted module.
- The data-context-${databaseType}.xml files have been moved to the edoras-one-hosted module. They have also been renamed to database-${databaseType}-config.xml. This means that each project which does not use the edoras-one-hosted module, needs to add a data source with the appropriate transaction manager. For example the database-H2-config.xml.
- All the security-context-${security.type}.xml files have been moved to the edoras-one-hosted module. They have also been renamed to security-${security.type}-config.xml . This means that each project which does not use the edoras-one-hosted module, needs to add a security configuration. For example the security-basic-config.xml.
Limitations