Actions
bug #6628
closedrequire vaadin UIs to be explicitely enabled per cdm-webapp instance
Status:
Closed
Priority:
Highest
Assignee:
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:
50%
Estimated time:
Severity:
critical
Found in Version:
Description
There are reasons why it is crucial that vaadin applications are inactive in cdm-webapp instances per default unless explicitly enabled.
A vaadin application is represented by the context of a Vaadin UI, so we need a mechanism to enable vaadin UIs on a per cdm-webapp instances which must work in the cdm-server and also in development environments. Therefore a per instance java properties file seems to be appropriate:
~/.cdmLibrary/remote-wepapp/{cdm-webapp-instance-name}-app.properties
The content of the properties file to enable all UIs which are currently implemented:
cdm-vaadin.ui.activated=registration,concept,distribution,editstatus
More details on the reasons why explicit enablement of vaadin UIs is important:
- Some UIs are special to specific projects and must not be availabled in general.
- Different vaadin applications bring their own special data which need to be initially inserted into the database like for example
Roles
. This data however is not wanted in other databases. Cluttering database with management data from other projects must be avoided.
This issue must be solved prior the release 4.7!
Actions