> > > > Erm. I meant relative src/ href values. thus things like: > > src="myimage.jpg". There are the ones that cause problems. > > > > Than we run into the <wicket:link> problem. IMO the user should have > the choice to switch it on and off. And than <wicket:link> must > support at least two different means of translating the relative into > whatever url scheme is currently in place.
What schemes do we need though? What other cases than prepending /contextpath/ do we need? Are you thinking of when people mount their webapps to e.g. *.do instead of a /do/* ? > You know during pre-processing if it is needed already. Only you don't > change the user values. You'd expect the user the know what he is > doing (and he is in the control of adding the context path) > Maybe you're right. I guess it could work like that too, and that's probably nicer from a component's point of view. But there are more options that a component can screw up. While there are no such dangers with post processing as by then it is just plain text (or a simple tree). Eelco Eelco ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
