> I was actually wondering if packaging the markup and the Page classes
> in different jars would work. Something like:
>
> myapp-wicket.jar:
> com/myapp/MyApplication.class
> com/myapp/MySession.class
> com/myapp/page/Index.class
> com/myapp/page/Login.class
>
> myapp-store1-html.jar:
> com/myapp/
Thanks for the responses.
I have no upper bounds on the number of different markups. The use
case is for an Application Service Provider, which could have hundreds
of clients, each with their own website design but with a lot of
functionality in common (for example, login, registration, shopping
c
> Say I have several different sites with their own designs, and I want
> to use the same basic WebPage/Panel/Application classes. Ideally, each
> site would be deployable as a war file. How might I package different
> HTML per war to accomplish this?
If you have a limited/ set number of styles, y
Say I have several different sites with their own designs, and I wantto use the same basic WebPage/Panel/Application classes. Ideally, each
site would be deployable as a war file. How might I package differentHTML per war to accomplish this?The examples I've seen have the HTML pages in the same dir
Hi All,
I'm new to Wicket and I'm trying to evaluate. Haven't had a chance to
fully dive in, so excuse me if this question seems basic.
Say I have several different sites with their own designs, and I want
to use the same basic WebPage/Panel/Application classes. Ideally, each
site would be deploy