Sure I can appreciate that :) However I define my panels to accept certain
objects to chuck into the model, so thats fine.
It means I can provide translations for pojos from non wicket jars using a
method similar to wickets nice 1 class, 1 property file approach.
Eg,
mypanel extends panel {
mypanel(id, Person person) {
setModel(new Person())
}
}
MyNonWicketProject.jar
Person.class
Person.properties
entity=Person
name=Name
surname=Surname
Great for generating forms, and combined with generics becomes quite
powerful.
My usecase and requirement of wicket is probably non typical (which is why
wicket rocks because I can customise it) - I have a large team each
developing different modules, and things like translations need to be
available in non wicket environments. Everything is translatable.
Still - would be nice if the
MarkupInheritanceResolver$TransparentWebMarkupContainer somehow indicated it
was the the page (and returned the pages model).
I can live without it.
igor.vaynberg wrote:
>
> hm. dont know if doing localization based on type of model object is a
> great idea. there are many usecases where model type is quiet
> aribitrary, and as you have found out yourself you dont know what
> component you get passed in, so you just need to handle it in a way
> that makes sense to you.
>
> -igor
>
--
View this message in context:
http://www.nabble.com/loadStringResource%28Component-component%2C-String-key%29---correct-method-to-check-if-the-component-IS-a-Page--tp16930303p16979272.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
