ndering (e.g. the line immediately after change the setting to
> > true) then that page will render with the wrong value.
> >
> > Craig
> >
> > -Original Message-
> > From: Antoine van Wel [mailto:antoine.van....@gmail.com]
> > Sent: Tuesday, S
mailto:antoine.van@gmail.com]
> Sent: Tuesday, September 29, 2009 9:03 AM
> To: users@wicket.apache.org
> Subject: Re: better way to strip wicket markup / tags per page?
>
> Thanks for the lightning fast reply.
>
> Yes it works fine under development. Still I don't like i
on the wiki[1] it is described how to get rid of wicket markup such as
wicket:id attributes on a page basis
page basis is an specific page on your project, or you want to strip wicket
tags to all pages?
you can override application init method and put your configuration lines:
getMarkupSet
t: Re: better way to strip wicket markup / tags per page?
Thanks for the lightning fast reply.
Yes it works fine under development. Still I don't like it - after all these
statements are also executed during production mode, and even though they
can't do any harm there, I'd rather not s
Thanks for the lightning fast reply.
Yes it works fine under development. Still I don't like it - after all these
statements are also executed during production mode, and even though they
can't do any harm there, I'd rather not see them there at all. More a matter
of personal taste I guess.
Anywa
>
> In some situations during development...
With that in mind, this solution is absolutely ok.
2009/9/29 Antoine van Wel
> Hi,
>
> on the wiki[1] it is described how to get rid of wicket markup such as
> wicket:id attributes on a page basis.
> The solution looks like a dirty hack to me which m
