-
Sub-task
-
Resolution: Outdated
-
Major
-
None
-
None
-
None
-
None
Since some days I'm thinking about using rhino (javascript) to make magnolia customizable.
Now I like to get some feedback form the audience before I think farther.
Primar thoughts:
- our main developers are weboriented and know javascript
- If something is configured in a scripting language it is very felxible
- It reduces the abstract step to a configuration file like xml
- You can adapt functions (like the activation) without downloading the sources
Configuration
-------------
The startup script is written in javascript and if you need to instantiate an other cache-handler for example you just do
it by changing this startup file.
Let's call this IoC by scripting
Changing Execution
------------------
Methods like activation could be extracted to a script like activate.js which one could adapt without subclassing.
Shell
We could include Rhinos shell this would it make easy to analyze data:
- dump data
- change data
- queries
- is duplicated by
-
MGNLGROOVY-3 Provide a Groovy-aware ClassFactory implementation
- Closed