I've used Tanuki to wrap various versions of Tapestry webapps and I've also
done plenty of embedded Jetty/Tomcat installations. Never had any major
issues with Tanuki. Any problems are almost always related to classloader
issues, not directly caused by Tanuki.
Kalle
On Wed, Mar 30, 2016 at 12:41
We use JSW (last non-GPL version) + Jetty 9.3/Tomcat 8 + Tapestry 5.4 in
production on various flavors of Windows without issue. The only unusual
thing I have seen is a problem with HikariCP having problems locating
the jTDS driver at system startup. Very weird since the problem does not
occur
I also checked if the changing temporal annotation to "TIMESTAMP" affects
this situation in any way. But there is no change - the fetched data still
appears to be 1982-03-27 23:00:00 after refreshing by ctrl + r for few
times.
Ok, I got it - truncating the date does not change it after all, it onl
Hi Pavel,
please check if you really removed all old JAR (and their all
dependencies). Often such problems appear when 2 different versions of one
JAR (e.g. foo-1.1.jar and foo-1.2.jar) are on the class path.
Best regards,
Cezary
On Tue, Mar 29, 2016 at 12:26 PM, Pavel Chernyak
wrote:
> Greeti
Hi again, guys.
I grepped for the TimeZone in the project directory, but there is nothing
interesting there (at least for me).
If I use
Calendar.getInstance(TimeZone.getTimeZone("GMT"), Locale.ROOT);
to get the calendar, the resulting log looks like this:
30-03-16 16:59:42:797 - {INFO} profil.Pr
Hi,
As I said before, I am pretty sure that your problem is not Tapestry
related, but caused by mismatches in timezone interpretation between values
stored by Postgres and JDBC. I will try to help, but for more information
check more general resources regarding Postgress, JDBC and date/time
handlin
The DATE would make sense, especially that the birth date is chosen from
the calendar (I do not require the user to type their birth time too and do
not store the time in any way). But I got this system as it is, so I do not
really know why the creators defined the column in this way.
2016-03-30 9
A lateral thought - is there a reason the column is declared as TIMESTAMP
instead of DATE?
> On 30 Mar 2016, at 2:50 PM, g kuczera wrote:
>
> 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 :
>
>
