I wonder which of the methods I need to override:
protected IMarkupLoader getMarkupLoader()
In case there is a need
In my app I already override ResourceStreamLocator to tell wicket where
to find the markup (as it can't be in the web app itself for our app).
Are there any other methods in that class which would be appropriate for
overriding?
> Chris,
>
> Have you looked at subclassing MarkupCache? I'm just a Wicket user so
one
> of
> the devs might want to weigh in but that is where I would start
looking.
>
>
http://people.apache.org/~tobrien/wicket/apidocs/org/apache/wicket/marku
p/
> MarkupCache.html
>
> Cheers,
> Jay
>
> On Thu, Feb 28, 2008 at 4:01 PM, Chris Colman
> <[EMAIL PROTECTED]>
> wrote:
>
> > > Chris,
> > >
> > > Generating static markup files is not really the "Wicket way" of
doing
> > > things. Couldn't you just use multiple panels and dynamically
> > add/replace
> > > as needed ...create-dynamic-markup-hierarchies-using-panels.html?
> >
> > The scope of different markup we use involves massive changes to the
> > whole page, not just a few panels so this solution won't work well
for
> > us.
> >
> > > Or maybe variations will work for you (see
> > > http://cwiki.apache.org/WICKET/multiple-markups-per-page.html)?
> >
> > We do use variations - therein lies the problem: A new variation is
> > generated to the file system by the web app but when wicket tries to
> > render the page using that new variation the variation's markup will
be
> > ignored until after we bounce the web app.
> >
> > > If neither of these fits th bill, you could try using a
> > > ReloadingWicketFilter:
> > >
> >
>
http://people.apache.org/~tobrien/wicket/apidocs/org/apache/wicket/proto
<h
>
ttp://people.apache.org/%7Etobrien/wicket/apidocs/org/apache/wicket/prot
o>
> > co
> > > l/http/ReloadingWicketFilter.html
> >
> > Does this solution cause a reloading of the entire web app when a
new
> > markup is detected? If so, ouch! The markup files can be regenerated
> > quite frequently and we can't afford to bounce the whole web app
each
> > time.
> >
> > Is there an interface used to provide the markup to wicket for which
we
> > can provide our own implementation and do the loading and caching of
> > markup and checking for new markup ourselves?
> >
> > >
> > > Cheers,
> > > Jay
> > > On Thu, Feb 28, 2008 at 2:40 PM, Chris Colman
> > > <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > > Is there a wicket mode I can configure in which new markup (eg.,
new
> > > > markup variations) can be picked up at run time without
restarting
> > the
> > > > app?
> > > >
> > > > In our app we can create/generate new markup at runtime. We
don't
> > want
> > > > to have to force a bounce of the web app for wicket to 'see'
this
> > new
> > > > markup.
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > > ============================================
> > > Computer Science: solving today's problems tomorrow.
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> ============================================
> Computer Science: solving today's problems tomorrow.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
