It depends on you node implementation:
If Foo is an object from your UI layer, just add #createContent() to it
and let it return a suitable representation.
If Foo is part of the domain layer, I'd prefer a factory for that, e.g.
ContentFactory#createContent(Foo). This factory could consists of a huge
switch statement, be configured via Spring or use some lookup to be
extensible from different modules.
Just some ideas
Sven
On 07/05/2013 11:11 PM, Piratenvisier wrote:
What is the best way to build a nested Tree with different
BookmarkablePageLinks per node?
The best would be when I build the Foo node to give the information to
build the BookmarkablePageLink.
Who should know the different PageClasses?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
