Modules not found by Tapestry 5.4.1; serving 'index' instead

I just upgraded to 5.4.1 from 5.3. I am switching my js libraries to requirejs modules. Following the guide at http://tapestry.apache.org/javascript-modules.html, I placed my module files in 'src/main/resources/META-INF/modules' and included one in a page's java class: @Import(module = {

Modules not found by Tapestry 5.4.1; serving 'index' instead

I just upgraded to 5.4.1 from 5.3. I am switching my js libraries to requirejs modules. Following the guide at http://tapestry.apache.org/javascript-modules.html, I placed my module files in 'src/main/resources/META-INF/modules' and included one in a page's java class: @Import(module = {

Re: after migrating to T5.4 home page won't load

Here are the effective dependencies: org.apache.tapestry tapestry-core 5.4.1 compile org.testng testng 5.14.10 test org.easymock easymock 3.0 test org.apache.tapestry

Re: problem accessing assets after migration to 5.4

On Thu, 30 Jun 2016 13:13:23 -0300, Qbyte Consulting wrote: Hi, Hi! I've changed my project deps to T5.4. After fixing some depricated page link methods my app compiles. However when I run I get exceptions from a menu loading service: is =

Re: after migrating to T5.4 home page won't load

On Thu, 30 Jun 2016 13:47:31 -0300, Qbyte Consulting wrote: I got jetty:run to launch the app, but when requesting the home page: HTTP ERROR 500 Problem accessing /audit/. Reason: Server Error Caused by: java.lang.AbstractMethodError This very probably

after migrating to T5.4 home page won't load

I got jetty:run to launch the app, but when requesting the home page: HTTP ERROR 500 Problem accessing /audit/. Reason: Server Error Caused by: java.lang.AbstractMethodError at

problem accessing assets after migration to 5.4

Hi, I've changed my project deps to T5.4. After fixing some depricated page link methods my app compiles. However when I run I get exceptions from a menu loading service: is = assetSource.getClasspathAsset("menu.properties").getResource() .openStream(); } catch (RuntimeException e) { final

Tapestry with Selenium and Cucumber

Hi, Are there any Tapestry sample projects around with Selenium and/or Cucumber tests? thanks, John

Re: Caching problem?

Ok, thanks for the heads-up, I added it to the constraint. Nathan On 30/06/16 17:10, Chris Poulsen wrote: btw the modules path can be both "modules" and "modules.gz" depending on various things. On Thu, Jun 30, 2016 at 4:35 PM, Nathan Quirynen

Re: Caching problem?

btw the modules path can be both "modules" and "modules.gz" depending on various things. On Thu, Jun 30, 2016 at 4:35 PM, Nathan Quirynen < nat...@pensionarchitects.be> wrote: > Hey Chris, > > Yeah, that's the only option I've found until now using following check as > you said: > > if( !

Re: Caching problem?

Hey Chris, Yeah, that's the only option I've found until now using following check as you said: if( ! (path.startsWith("/assets/") || path.startsWith("/modules.gz/")) ) { // add headers } Hope I got everything covered by this, but it's at least an improvement as how it was before

Re: Caching problem?

check the path? (asset paths usually contains "/asset/" and module paths contains "/modules/") On Thu, Jun 30, 2016 at 11:55 AM, Nathan Quirynen < nat...@pensionarchitects.be> wrote: > Is there any way to know in a Request filter if it is a page request (not > a request to some asset). > > I

Re: Caching problem?

Is there any way to know in a Request filter if it is a page request (not a request to some asset). I thought doing the following: PageRenderRequestParameters parameters = linkEncoder.decodePageRenderRequest(request); if (parameters == null) { // not a page request } But it seems

Re: FW: Null pointer on sort with 5.3.8 that didn't occur with 5.3.7

I guess using t:add is OK as long as the grid is not performing operations where it needs to access the property in the data source (for operations like sorting/filtering). Generally speaking we (@work) almost always end up using bean models, except in the most simple cases. -- Chris On Thu,

RE: FW: Null pointer on sort with 5.3.8 that didn't occur with 5.3.7

Thanks for the pointers, creating a BeanModel and adding my extra columns to it sounds like the right way to go. As an emergency solution for now I'm just going through all grids and adding the t:add columns into t:excludeSort in order to avoid the crashes on sorting. Then I will work on the