Jonathan Locke wrote:
1. user puts component jars and classfiles on classpath and is blissfully ignorant of what's going on 2. Application constructor enumerates through jars and classes via ClassLoader.getResources() looking for xml metadata, each package containing a Components.xml file a. each xml file is processed to register resources for any components in the jar or classpath folderb. the minimum format for this xml file would be something like: <wicket-components><wicket-component class="wicket.whatever.MyComponent" load="true/false"><resources><package-resource path="images/foo.gif" locale="en_CA" style="sporty"/>... </resources> </wicket-component> </wicket-components>resources not registered using the <resource> declarations for PackageResources would have to be registered by setting load="true" and using a static initializer block to do the work. we can talk more about the format and where the info should go, but the basic idea seems solid...
Sounds a lot like HiveMind, Oscar and/or Spring. Maybe we should borrow the technology for this, instead of inventing our own lingua?
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
