I wrote: > I see the experimental class WicketMessageTagHandler and note that it's > disabled by default. If I were to mimic this class for my own custom > filter, is there any way I could go about registering it without hacking > into MarkupParser? Or is there some simpler way to do this?
Okay, I'm getting there. I managed to do this with code in my Application init() that looks like this: getMarkupSettings().setMarkupParserFactory(new IMarkupParserFactory() { public MarkupParser newMarkupParser() { return new MarkupParser(new XmlPullParser()) { public void initFilterChain() { appendMarkupFilter(new MyMarkupFilter()); } }; } }); This will do almost everything I want. But I'm really considering replacing the namespace prefix "wicket" with something else. I copied much code from WicketMessageTagHandler, but that has a little "TODO" that reads /** TODO Post 1.2: General: Namespace should not be a constant */ [ ... ] String WICKET_MESSAGE_ATTRIBUTE_NAME = "wicket:message"; I would like to get hold of the namespace prefix in use during the call to nextTag() in my implementation of IMarkupFilter, but there doesn't seem to be any way to get it there. Am I missing something simple? As always, thanks, -- Scott ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user