Re: Tapestry 4.1 Migration to Tapestry 5

No it just means T5 will not process them and they will just pass on to T4 > On Jun 28, 2016, at 10:34 AM, Mukesh Chandra > wrote: > > If I ignore the T4 urls, won't the T4 pages stop working? > > -Original Message- > From: Barry Books

RE: Tapestry 4.1 Migration to Tapestry 5

If I ignore the T4 urls, won't the T4 pages stop working? -Original Message- From: Barry Books [mailto:b...@trsvax.com] Sent: Tuesday, June 28, 2016 8:54 PM To: Mukesh Chandra Cc: Tapestry users; trs...@gmail.com Subject: Re: Tapestry 4.1 Migration to Tapestry 5 You should be able to

Re: Tapestry 4.1 Migration to Tapestry 5

You should be able to just add the T5 configuration to your existing web.xml. I think you also have to tell T5 to ignore the T4 urls. There is a T5 configuration for ignored urls > On Jun 28, 2016, at 10:16 AM, Mukesh Chandra > wrote: > > Thanks Barry! >

RE: Tapestry 4.1 Migration to Tapestry 5

Thanks Barry! One more thing, what changes do I need to make in the Web.Xml so that both T4 and T5 pages continue working. Apparently my application has started working once I put in the filters for T5 Regards Mukesh -Original Message- From: Barry Books [mailto:trs...@gmail.com] Sent:

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

Sure, I was in the process of debugging. This is what I found so far that happens when clicking the column header to sort (skipping the non-relevant steps): 1) Method GridSortModel.updateSort(String) gets called with the column name as the arg. 2) CollectionGridDataSource.prepare(int, int,

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

Hook up a debugger and see what is going on when the NPE is thrown? On Tue, Jun 28, 2016 at 3:43 PM, Davide Vecchi wrote: > Thanks, those are interesting options to change my design, which I will > probably have to do. > > But at this stage I need to focus on why the outcome of

Re: Tapestry5.4.0 'Palette' button doesn't work on IE11 compatibility mode

I have also set the response header in the SessionRequestFilter service() method. aResponse.setHeader(HEADER_KEY, "IE=Edge"); where HEADER_KEY = "X-UA-Compatible"; That didn't seem to work either. I do see in the response through fiddler that this header value is being set to IE=Edge. Any

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

Thanks, those are interesting options to change my design, which I will probably have to do. But at this stage I need to focus on why the outcome of defining columns in that way is different in 5.3.8, because it might be that more areas of this web application are affected by differences in

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

Also you can control the display blocks using the data-type on the bean model, if you need something special. -- Chris On Tue, Jun 28, 2016 at 3:30 PM, Chris Poulsen wrote: > You can use a bean model for variable number of columns, that one also > gives you full

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

You can use a bean model for variable number of columns, that one also gives you full control over conduits etc. Inject BeanModelSource and create a display model for your data source, use .include (or similar) to whitelist the desired attributes in the generated model and model.add to get your

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

Thanks for the answers, it's becoming more clear. The possibility suggested by Kalle makes sense, however I made some test about it and I don't think it's the cause of my problem. This grid column was being sorted without exceptions with Java 7 + Tapestry 5.3.7, plus I checked and none of the

Re: Tapestry 4.1 Migration to Tapestry 5

I dug up this code that allows T5 applications to access T4 sessions. I think the XXX is the app name in the T4 configuration. @Deprecated public class T4SessionStrategy extends SessionApplicationStatePersistenceStrategy implements ApplicationStatePersistenceStrategy { private

Migration from tapestry 4.1 to 5.4

We are striving to migrate Tapestry 4 pages to Tapestry 5. This endeavor requires both Tapestry 4 and Tapestry 5 pages to co-exist. I tried below options just to add a page which displays a "Hello" message in Tapestry. è Our current web.xml uses org.apache.tapestry.RedirectFilter which has