Cory Watson <jheephat <at> gmail.com> writes: > > Tapestry 3 had the <external-asset> for linking to a stylesheet that wasn't > included in the WAR of my web app. I saw some references in TP4 to an > external loader fo assets, but I can't tickle it in a way that isn't context > or classpath. I see that I can give it an unrecognized prefix (http: for > example) and have it pass it through unchanged. What if I just want it > request /stylesheet.css? I don't want it in my context or classpath.
You may try providing an implementation for the service point tapestry.asset.LookupAssetFactory. It will be called to create an asset when it has no prefix. In your code, you can create an ExternalAsset. > While I'm at it, the ChartService example that comes with TP4-beta6 seems to > still be TP3-ified. Can someone clue me in to how to get ChartService > working in TP4? I see how to set it up in hivemodule.xml, but extending > AbstractAsset with ChartAsset and instantiating it in the page doesn't seem > to be the Right Way anymore. I see that services could request the chart > service via chart.svc from the app, but my service(IRequestCycle) method is > written to handle: > > String pageName = cycle.getParameter(ServiceConstants.PAGE); > String componentId = cycle.getParameter(ServiceConstants.COMPONENT); You shouldn't use the svc service encoder as it only works for services taking no parameters. You should make sure it works with ugly URLs first. Only then should you start to create your own service encoder. -- Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
