okay, if this is DI in wicket, i'm against it. let's go with something
dirt simple like the properties file idea.
all i want now is a way for the component to get loaded when the app
starts. is IOC required these days
to load a class?
Martijn Dashorst wrote:
Jonathan Locke wrote:
you can iterate through Components.xml in your whole classloader in
like 5 lines of code...
True, but the whole idea just reeks of dependency injection. Even
though the component dialect you propose (which is only a proposal, I
know) sounds good, I think we could use a D.I. container (HiveMind
seems to fit the bill) and do the registration (just as you propose in
the last message) in the Java.
I am not waiting nor anxious to introduce a D.I. or plugin framework
into the core of Wicket. I would like it to be as automatic and
non-intrusive and non-error prone as possible. Writing Java code is
what I do best. properties/xml/configuration files I always forget :-)
Martijn
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
