Re: Caching problem?

I have found that in one of the applications request filters following is added to every response: Cache-Control: no-cache, no-store, must-revalidate Pragma: no-cache On 29/06/16 17:33, Nathan Quirynen wrote: Hi, I have a "weird" problem where this one image won't show up. Never had this

Caching problem?

Hi, I have a "weird" problem where this one image won't show up. Never had this problem before the upgrade to 5.4 and since there have been changes with caching, I guess it has something to do with that. I don't know a lot about the caching Tapestry does (or in general), so I hope someone can

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

Just a correction, that t:add is not just unnecessary, but it will be ignored if you specify the beanModel explicitly: > A comma-seperated list of property names to be added to the > org.apache.tapestry5.beaneditor.BeanModel. Cells for added columns will be > blank unless a cell override is

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

I'm guessing that something in the sorting part attempts to pull out the value from your passed data source (possibly coerced from a collection). The thing is that your data source does not contain the property (as it is synthetic) and you do not really pull the value from the data source ever,

Re: Tapestry 5.4.1 + Hibernate 5 exception

Greetings. I compiled tapestry-hibernate-core against hibernate 5.2 and since have 0 problems with hibernate. Maybe you should reconsider to do same thing? On 29 June 2016 at 12:41, M J wrote: > Hi! > > > It seems that Tapestry 5.4.1 is compatible with Hibernate 5.x ( >

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

I changed my plan of finding out what causes this difference between 5.3.7 and 5.3.8. Instead I will go with some re-design, using some suggestions I got here. However I am still very interested in knowing whether my way of defining these t:add columns (pasted below) in general has something

Tapestry 5.4.1 + Hibernate 5 exception

Hi! It seems that Tapestry 5.4.1 is compatible with Hibernate 5.x (https://issues.apache.org/jira/browse/TAP5-2525) and I've seen a few e-mails on this list that suggest people are successfully using 5.0 and 5.1

Re: Dynamic Security Role Value - Tynamo Security

Just specify the prop: binding prefix explicitly, i.e.: role="prop:dynamicRoles" This parameter just uses literal: binding prefix by default. Also make sure you read this: http://tapestry.apache.org/component-parameters.html#ComponentParameters-BindingExpressions On Wednesday, June 29, 2016,

Re: Dynamic Security Role Value - Tynamo Security

Maybe use a and move the role related code to your java page? Von meinem iPhone gesendet > Am 29.06.2016 um 08:24 schrieb Matthew Bush > : > > I want to dynamically set required roles at runtime dynamically rather than > have them statically coded. Is

Dynamic Security Role Value - Tynamo Security

I want to dynamically set required roles at runtime dynamically rather than have them statically coded. Is this possible? Taken from the tynamo-security page (http://www.tynamo.org/tapestry-security+guide/ ) delete user What I would like to