Ok, I fiddled with this for two whole days, did a whole bunch of stuff, and couldn't figure it out. Finally after I had sent out this email, I was reading the 5.2 docs and had an idea when reading the section on securing assets from this page:
http://tapestry.formos.com/nightly/tapestry5/guide/assets.html Long story short, I added this contribution to my AppModule and that seems to have fixed the issue: public static void contributeRegexAuthorizer(Configuration<String> configuration) { String pattern = "([^/.]+/)*[^/.]+\\.((css)|(js)|(jpg)|(jpeg)|(png)|(gif)|(html)|(xml))$"; configuration.add("^org/chenillekit/tapestry/core/" + pattern); } Now, this brings up another question. Does this mean I have to add similar contributions for all other component library jars, because all of them are for Tapestry 5.1. I am not sure what else is broken at this point, as I am yet to do my full test. Anyways, thanks to anyone who looked at this. --- On Sun, 5/8/11, Jeshurun Daniel <sjeshu...@yahoo.ca> wrote: From: Jeshurun Daniel <sjeshu...@yahoo.ca> Subject: Chenillekit Editor component doesn't work after upgrading from 5.1.0.5 to 5.1.0.8-SNAPSHOT To: users@tapestry.apache.org Received: Sunday, May 8, 2011, 9:32 PM Hi Everyone, I recently upgraded an application from Tapestry version 5.1.0.5 to 5.1.0.8, primarily to address a bug with the ajax form loop. But ever since the upgrade, chenillekit's editor component has stopped working. At the place where the component is rendered (via an iframe) is a Tomcat 404 error page. I noticed that the rendered url for the src attribute of the frame under both versions is: https://localhost:8443/appname/assets/classpath/1.2.1/org/chenillekit/tapestry/core/components/fckeditor/editor/fckeditor.html?InstanceName=editor1&Toolbar=Default Under 5.1.0.5, this returns the asset, wheras in 5.1.0.8 this comes up with Tomcat's 404 page. By upgrading, I mean that I replaced the following jar files with their corresponding version in 5.1.0.8: tapestry5-annotations-5.1.0.8.jar tapestry-core-5.1.0.8.jar tapestry-ioc-5.1.0.8.jar tapestry-spring-5.1.0.8.jar tapestry-test-5.1.0.8.jar tapestry-upload-5.1.0.8.jar I am not using Maven, and using it is presently not an option for us. I am not very familiar with the internal workings of Tapestry, and have been struggling with this problem for over two days now. Any suggestions will be much appreciated! Thanks, Jeshurun