> While on this topic, I have a question. > > If someone changes their application's ComponentNameAttribute to say "comp". > They develop their components using id='comp-whatever'. They then use a > component form another source - say a contrib component. It has its own > markup using id='wicket-whatever'. Will this work ? Or is there a need to > allow a per component (or per markup stream) definition of > ComponentNameAttribute ? >
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
