Hi,
I thought about that and the only tool I know might be useful for that is Spring Framework AplicationContext (aka BeanFactory).
For me there is only one big pro:
- Simple but powerful XML syntax to define even complex solutions.
- Possibility to pre-loading values
- Possibility of usage factories
- The outcome is well and clean wrapped as used defined
cons:
- BeanFactory layer should be separated from the rest of the application. It is not difficult but might be tricky (see pros 2nd and 3rd). It might be necessary to wrap everything (factory + outcome) within borders to close possibility of creating some nasty monster for both server and putative users.
- I found spring framework is already in use so our ApplicationContext instance should not be linked with the rest of instances.
That is my thoughts,
Best regards,
Jacek
PS I could not figure out where are located templates for RDF models which are passed to the main server's repository with values given by user or is that final RDF created dynamicaly by parser?
