Re: Hibernate call returns wrong day

I also checked the default PostgreSQL timezone (in the postgresql.conf file), which is set to "Poland". 2016-03-30 8:47 GMT+02:00 g kuczera : > I observed that behavior on the production server and then confirmed it on > the test server, which is not accessed by any client, etc. I forgot to > men

Re: Hibernate call returns wrong day

I observed that behavior on the production server and then confirmed it on the test server, which is not accessed by any client, etc. I forgot to mention that the calendar.getTimeZone().getDisplayName() call returns "Central European Time". 2016-03-30 3:56 GMT+02:00 Kalle Korhonen : > The same th

Re: Hibernate call returns wrong day

The same thread really reads the same value from the database every few seconds and it may come out different? I don't buy it, there must be something else going on at the same time. Are you sure it's the same value? Is there something else writing to it at the same time? Can the system default tim

Re: Hibernate call returns wrong day

Hi guys, First of all, thanks for the answer and the effort you put into writing them. I checked few things and read couple of articles about similar problems and here is my little summary: - my PostgreSQL birthDate column's type is 'birthDate TIMESTAMP WITHOUT TIME ZONE' - the values co

Re: Strange error when trying to deploy update from 5.3 to 5.4

Thank you. Looks like i can't delpoy on same appserver different tapestry wars. Problem solved. On 29 March 2016 at 13:58, Barry Books wrote: > Make sure you don't have the 5.3 and 5.4 jars in your war file. For some > reason this always seems to happen after an upgrade and it produces strange >

Strange error after deploy to jetty with tapestry 5.4.

Greetings. I have strange error after trying to migrate t5.3.8 to 5.4. I using: tapestry-core 5.4.0 tapestry-upload 5.4.0 tapestry-hibernate 5.4.0 tynamo tapestry-security 0.6.2 tynamo tapestry-conversations 0.2.0 tynamo tapestry-routing 0.1.1 On my local machine with jetty:run everything w

Re: Strange error when trying to deploy update from 5.3 to 5.4

Make sure you don't have the 5.3 and 5.4 jars in your war file. For some reason this always seems to happen after an upgrade and it produces strange errors. On Tuesday, March 29, 2016, Pavel Chernyak wrote: > Greetings. > I have strange error after trying to migrate from 5.3.8 to 5.4. > I using:

Strange error when trying to deploy update from 5.3 to 5.4

Greetings. I have strange error after trying to migrate from 5.3.8 to 5.4. I using: tapestry-core 5.4.0 tapestry-upload 5.4.0 tapestry-hibernate 5.4.0 tynamo tapestry-security 0.6.2 tynamo tapestry-conversations 0.2.0 tynamo tapestry-routing 0.1.1 On my local machine with jetty:run everythi

Re: Hiding FormFragment via javascript

I can’t remember all the problems I had when combining FormFragment with Loop with modals, but I do know that I solved them all by moving the FormFragment to above the loop, adding an If, putting the modal inside it and, on submit of the modal, the server-side updated the relevant loop item’s va

Re: Hiding FormFragment via javascript

Hi Dimitris! we are currently running Tapestry 5.3.8. An Upgrade to T5.4 is currently not feasible. Hendrik Am 24.03.2016 um 00:17 schrieb Dimitris Zenios: > hendrk what version of tapestry are you using? > On 23 Mar 2016 16:00, "Hendrik Grewe" wrote: > ---

Tapestry 5.3.7 with Tanuki service wrapper

Hi, Has anyone had success running ioc via the Tanuki Service Wrapper product? I'm having problems with Tapestry instantiating a DAO service that is injected with EntityManager references. Suspect a class loader problem, I'm getting inconsistent results. All works fine from the command line laun