> You make a good point. > > Is it possible to take the current property file > mechanism (where you only have to specify classes with > resources) and move it into IComponentInitializer somehow? > You are right you should only be required to specify > components with resources.
It already is, see latter. > > Sorry, with all the emails going back and forth I lost > track of what the final property file mechanism looks like. > If I remember correctly, each component must provide a file with: > > component1 = resource1, resource2, resource3 > > right? But I never understood, with this mechanism, how > does Wicket know which components actually end up being used > by a given application or not? Gili, don't take this the wrong way, but ... None of us have this project as a full time job, so our time is very limited. You have access to the source code just like the rest of us so you should be able to figure this out. Do a cvs diff on the code you have and the code in the head, one change will come up in Application.java look at it and you will see a new method called initializeComponents, inside it it has the code that does the initialization and it's stone simple. Now if you still have questions AFTER you tried to figure this out yourself, im sure I and anyone else will be more then happy to help you. -Igor ------------------------------------------------------- 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
