igor.vaynberg wrote:
>
> for what it is worth i will be creating a cms in the near future using
> wicket. my idea is simple. the cms is a single wicket page. the users have
> a
> special tag they use to define dynamic components like <cms:component
> type=foo param1=param2/>. the page itself has a single repeater, prior to
> rendering it takes the markup and splits it into chunks of static and
> component definitions. for a static piece the repeater gets a label, for a
> component definition the repeater gets a new component instantiated. no
> need
> for getvariation/java classes per page/ and all that funky stuff that is
> made for regular applications.
>
> -igor
>
>
So you can have multiple html pages managed only by one Java class? That's
could be what I need.
I all the examples I looked on Wicket site, I never found an example like
this.
Should I look to components to do this?
--
View this message in context:
http://www.nabble.com/Is-Wicket-suitable-for-my-CMS--tf4536847.html#a13191210
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
