26 Aug
2008
26 Aug
'08
11:34 a.m.
Hello Vincent,
Yes that would be nice because for now it seems less transparent to
what I have (a simple java bean class with all fields being
configuration properties). I could see annotation being useful to
separate configuration fields from other fields for example but if all
of them are configuration properties I don't see the need
I see you point, and you are right. My use case was more that a Class
with a lot of different Incarnations (Object Lifecycles) has to have
different Options set each time it is used/created, plus these options
are stored via JPA/Hibernate. The Wiki use-case is more that once the
Plugin / Component is loaded, the Configuration does not change and
Components are more or less static.
If you are however still interested than I could send you the Eclipse
Project with the Option Handling system classes + test cases. (I didn't
like to spam the list.)
greetings
Jonas