Well, if the functionality is there to change the wicket prefix
name, it should at least work as expected. "wicket" is fine as a
default but I thought the entire point of the aforementioned method is
that it allows you to change it to another name. It makes no sense for
"wicket" to still get detected once you've changed it. If you don't
want to support changing the prefix, remove the method altogether but
if it's around make it work :PGili On Sun, 6 Mar 2005 11:51:13 +0100, Juergen Donnerstag wrote: >Good point. It currently does because "wicket" is the default, no >matter how you change the component name. It won't if we change it the >way I suggested (no more default). > >I think the real question is, how often do you want to change the >component name? The pre-processor is the first use case I came >accross. > >Another solution to the problem - besides a boolean to turn default >beaviour on an off - could be to make wicket-component detection >configurable. Though it is already nicely separated the source code >(IMarkupFilter), it is not configurable. > >Juergen > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Wicket-develop mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
