Aleksandar: Current implementation using a configuration, and the value is update manual once per month. Would be nice to have a batch job that fetches exchange rates once per day using something like Open Exchange Rate.
Aleksandar: I've used a scripting approach using mvel2 and fetch the configured script after entity/action permissions was successful.
Extending entities is difficult and time consuming because right now part of the business logic (validation) is mingled into the data layer. It would be better to extract this to ease the extension of both the data portion and the business logic. Maybe it would make sense to externalize some rules and use Drools to allow simple extensions.
Markus Geiss (Deactivated): I agree that there is some mixing of concerns that need to be refactored to have a clear separation. We are planning to introduce Drools as a add-on to a more simple approach.
Aleksandar: Drools offer a very simple Excel-template to allow non-devs to create rules. Most the users will be comfortable and experienced with Excel.
Is there a plan to replace native SQL statements with a more abstract solution (JPQL, HQL)?
Markus Geiss (Deactivated): Yes, it's part of some technical enhancements. We still need to find define a clear road map and mingle it into the general release planning.
Right now the platform is only one project, all modules are part of one source tree and it is hard to extend this without loosing backwards compatibility. Are there plans to modularize the platform to become a real platform?
Aleksandar: I've worked with Broadleaf Commerce and I think their approach would give enough freedom to extend the platform. They simply split the project into multiple modules and provide maven artifacts that can be pulled to create a project with all needed things.