2008/8/11 Igor Vaynberg <[EMAIL PROTECTED]>:
> then have your page look it up itself from the spring context using
> some registry
>
> class mypage extends webpage {
> @SpringBean private PageConfigRegistry registry;
>
> public mypage() {
> mydata data=(mydata)registry.getdatafor(getclass());
> // do whatever with data
>
> // ^ or put that lookup into your base page so page just has to
> call getConfigData()
> }
> }
>
So you are saying that wicket does not provide a standard way for page
configuration.
So I'll develop a custom solution based on spring or on property files.
> there is no need for a framework to provide anything special for such
> a usecase, it is just java...
Even I18N is "just java", you could write the wicket code yourself if
you should. But I chose to use wicket just not to have to.
I think configurability is a very common requirement for any web
framework (even servlets had this). Even a simple solution based on
property files or, for example, a complete integration with Spring
would be useful.
Thanks, bye
Lorenzo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
