On Mon, Aug 11, 2008 at 9:40 AM, Lorenzo Bolzani <[EMAIL PROTECTED]> wrote:
> 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 one-way-fits-all way of configuring pages, this is too
application specific for us to provide anything.
>> 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
ok, thats done... getString("key") will read the .properties files...
> or, for example, a complete integration with Spring
> would be useful.
yeah, that would be awesome. and what about all those pesky users we
have who do not use spring?
-igor
>
>
> Thanks, bye
>
> Lorenzo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
