You can leave the asset in the old location, and Tapestry will find it, with a warning.
Or you can move it to the new location; /assets/LIB-NAME/path.js ... the LIB-NAME is determined from the library containing the component. The error message only reports the 5.3 location; it should be updated to be the 5.4 location (under META-INF/assets) and perhaps the 5.3 location as well (until 5.5, when 5.3 locations will not be supported). JIRA issue would be welcome. On Thu, Sep 5, 2013 at 5:14 PM, Lenny Primak <lpri...@hope.nyc.ny.us> wrote: > Now I understand how I could get so confused: > The error message is this: > targetException > org.apache.tapestry5.ioc.internal.OperationException: Unable to locate > asset 'classpath:com/flowlogix/web/mixins/js/DateFieldParserPatch.js' (the > file does not exist). > > But, I have to put the asset here: > META-INF/assets/flowlogix/js/DateFieldParserPatch.js > > Notice the lack of the com/flowlogix/web/... etc. The path in the error > message is wrong. This is why I got so confused on where to put these > assets. > > Should I file a JIRA? > > On Sep 5, 2013, at 7:56 PM, Lenny Primak wrote: > > > (answering my own question) > > Looks like the semantics have changed. Used to be that assets were > looked up relative to class package name, > > now they are just looked up relative to root. > > > > On Sep 5, 2013, at 6:37 PM, Lenny Primak wrote: > > > >> I am trying to migrate FlowLogix library to T5.4... > >> There are a whole bunch of mixins there, that use JavaScript > @Import(library="xxx.js"). > >> I used to have those .js in the classpath in the same package. > >> Now, with the new packaging scheme, I moved them to > META-INF/assets/flowlogix. > >> After this, none of the imports work with the following exception: > >> > >> Example: > >> org.apache.tapestry5.ioc.internal.OperationException: Unable to locate > asset 'classpath:com/flowlogix/web/mixins/PeriodicUpdater.js' (the file > does not exist). > >> > >> If i change the code to use > JavaScriptSupport.importJavaScriptLibrary("xxx.js") it starts working. > >> Assuming this is a bug, should I file a JIRA? Seems pretty bad to me. > >> > >> Using alpha-17 > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com