your css may depend on wicket tags, such as wicket:container,
wicket:extend, etc. these tags are stripped in deployment mode.
-igor
On Wed, Oct 28, 2009 at 2:13 AM, Pi Trash <ptr...@web.de> wrote:
> Hi all,
>
> I developed a simple Wicket application containing just one page with some
> tables. In development mode everything is working and looking fine. But when
> I switch to deployment mode the presentation of the page changes
> dramatically. For example borders of tables are not visible any more. What am
> I doing wrong?
> It seems to be just a CSS issue but the code and resources are exactly the
> same. I just switch the mode by changing a System property which is handled
> in WebApplication code like this:
>
> @Override
> public String getConfigurationType() {
> if (this.debugMode()) {
> return "DEVELOPMENT";
> } else {
> return "DEPLOYMENT";
> }
> }
>
> Thanks for your help!
> _______________________________________________________________
> Neu: WEB.DE DSL bis 50.000 kBit/s und 200,- Euro Startguthaben!
> http://produkte.web.de/go/02/
>
>
> ---------------------------------------------------------------------
> 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
