Re: T5.4 and OLD Hibernate 3x

2016-01-11 Thread Prakash Manjeshwar
This might be useful, from StackOverflow: http://stackoverflow.com/questions/8799121/java-lang-nosuchmethoderror-org-hibernate-sessionfactory-opensessionlorg-hibe >From the accepted answer: "In Hibernate 3.6 the SessionFactory.openSession no longer returns an org.hibernate.classic.Session, rathe

Re: T5.4 and OLD Hibernate 3x

2016-01-11 Thread Kalle Korhonen
You could try backing out the tapestry-hibernate and tapestry-hibernate-core libs to a T5.4 version before beta-17 (see http://markmail.org/message/yeqlybz6hivwwcxk#query:+page:1+mid:ahfcfibfff2t6ueu+state:results). They were not available via Maven central and the staging repos are not available a

Re: T5.4 and OLD Hibernate 3x

2016-01-11 Thread Jens Breitenstein
Hi Thiago, thanks for your answer! After some "more" dependency exclusions, the following (hibernate related) libs are left: * org.apache.tapestry:tapestry-hibernate:5.4.0 * org.apache.tapestry:tapestry-hibernate-core:5.4.0 and * org.hibernate.javax.persistence:hibernate-jpa-2.0-api:1.0

Re: T5.4 and OLD Hibernate 3x

2016-01-11 Thread Thiago H de Paula Figueiredo
On Mon, 11 Jan 2016 14:06:15 -0200, Jens Breitenstein wrote: Hi All, Hi! I am migrating an application from T5.3.8 to T5.4. In the past the application was based one Hibernate 3x but T5.4 seems to make use of Hibernate 4 explicitly (correct me if I am wrong). So currently I am facing

T5.4 and OLD Hibernate 3x

2016-01-11 Thread Jens Breitenstein
Hi All, I am migrating an application from T5.3.8 to T5.4. In the past the application was based one Hibernate 3x but T5.4 seems to make use of Hibernate 4 explicitly (correct me if I am wrong). So currently I am facing the following exception: Caused by: java.lang.NoSuchMethodError: org.hi

Alter request header value in request filter

2016-01-11 Thread Nathan Quirynen
Hi, Is it possible to alter a response header in a filter? I already add some response headers with Response.setHeader(...), but I want to add "HttpOnly" to every Set-Cookie header. Or is there an alternative way to achieve this? The JSESSIONID is apparently always set with HttpOnly, but not