You're right. Thanks for clearing this up.
Though, can we do it so only the root Pages must be mentioned in the
property file? Components should then be able to export a list of all
nested components. I just want this to be as close to zero-configuration
as possible.
Gili
Johan Compagner wrote:
Ok, so I won't suggest the exact details of how to accomplish
this, but let me ask: why don't we declare an interface which all
components must implement which will make this possible (a la
JavaBean) as opposed to using property files? I'd prefer having this
sort of thing as part of the Class, something I run through a compiler
and gets compile-time validation.
We don;t know all the components.. It has to be at frond.
In the Application init we don't know anything what pages what
components there are nothing nada.
We have to know that from somewhere. Only thing is using property file
so that we know what to load.
johan
-------------------------------------------------------
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
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
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
