yes, sorry in 1.2 it is still private. I assume MarkupCache.clear() is
too heavy to remove all markup from the cache, correct? And relying on
ModificationWatcher to remove it after X secs is not a solid solution
either. Sorry I don't have any other idea.
In order to make sure feature finds it way
Juergen,
Looking at the javadoc online
(http://wicket.sourceforge.net/apidocs/wicket/markup/MarkupCache.html),
MarkupCache doesn't have the removeMarkup method.
could this be 2.0 stuff?
Thanks
Tim
On 03/09/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> I don't think so, the markup is not ver
I don't think so, the markup is not versioned
1.2.2 MarkupCache: what might work, but I haven't tested it. I assume
you either subclassed MarkupContainer.newMarkupResourceStream() or you
created your own IResourceStream implemented and registered a resource
stream locator with the application. Eit
hi again,
a little more information:
I am trying to create something a little like Archetypes for Zope.
This will allow a site admin to create new types of components based
on others previously created (although the very base types, Axioms,
are Wicket Components).
I'm struggling a little with the
Hi,
in Wicket 1.2.2, is there any way of manually refreshing the markup
cache. I know this has been discused previously, and methods for doing
this in 2.0 (and perhaps 1.3) have been discused.
The markup for my compenents is being generated by a database, and I
would like to be able to tell wicket
