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.
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); IPage page = cycle.getPage(); IComponent component = page.getNestedComponent(componentId); IChartProvider provider = (IChartProvider) component; But when I call it as a service, getPage() returns null! This makes complete sense to me, I just don't understand how I'm supposed to utilize this new service setup. Any help is appreciated ;) -- Cory 'G' Watson http://www.onemogin.com
