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.
Anyway I have something in mind to improve it according to my taste. Will
implement that when I got time... This is not really an urgent issue to me.
Thanks anyway for the reply - I'm assuming now there really is no other way
to do this than temporarily changing the global settings.
Antoine
On Tue, Sep 29, 2009 at 7:46 PM, Marat Radchenko <
slonopotamusor...@gmail.com> wrote:
> >
> > In some situations during development...
>
> With that in mind, this solution is absolutely ok.
>
> 2009/9/29 Antoine van Wel <antoine.van....@gmail.com>
>
> > 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 may go wrong when for
> > instance exceptions occur. Does anybody know of a better way?
> >
> > For completeness sake, here is the code duplicated from the wiki:
> >
> > private boolean stripTags;
> >
> > public TestPage() {
> > stripTags =
> > Application.get().getMarkupSettings().getStripWicketTags();
> > }
> > @Override
> > protected void onBeforeRender() {
> > Application.get().getMarkupSettings().setStripWicketTags(true);
> > }
> > @Override
> > protected void onAfterRender() {
> >
> Application.get().getMarkupSettings().setStripWicketTags(stripTags);
> > }
> >
> >
> >
> > Thanks in advance,
> >
> > Antoine.
> >
> >
> > References:
> > [1]
> >
> http://cwiki.apache.org/WICKET/how-to-remove-wicket-markup-from-output.html
> >
>
--
--8<--8<--
take your photos everywhere you go - http://www.memolio.com
--8<--8<--
We don't see things as they are, we see things as we are. - Anais Nin
Whether you think you can or whether you think you can't, you're right. -
Henry Ford
--8<--8<--
