Re: Hosting Apache Tapestry5.1 on GAE (Google Application Engine)

2010-02-19 Thread Kalle Korhonen
No, I haven't had issues with static assets but then again, the current example is pretty bare bones. I've certainly noticed that GAE is dog slow though. I read about how GAE scales and it's evident in our example as well that GAE just spawns new JVMs rather the new threads for additional instance

[Tapestry Central] Evolving the Meta Programming in Tapestry 5

2010-02-19 Thread Howard
I've set a goal of removing Javassist from Tapestry 5 and I've made some nice advances on that front. Tapestry uses Javassist inside the web framework layer to load and transform component classes. All that code is now rewritten to updated APIs that no longer directly expose Javassist technology. I

Re: Hosting Apache Tapestry5.1 on GAE (Google Application Engine)

2010-02-19 Thread Alex Kotchnev
Kalle, do you have any issues w/ static assets not being served from GAE ? I'm prepping an app to be deployed in production on GAE, and in its development state (http://zadachite-dev.appspot.com), I'm a bit discouraged : often, when the app is loaded, I often get missing assets and I have to rel

Re: T5: logging statements logged twice using Log4j

2010-02-19 Thread kamiseq
set log4j.additivity.org.tuckey=false pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski@gmail.com __ On 19 February 2010 13:39, britske wrote: > > Hi, > > I'm having the problem (always had as far as I remember, but it starts to > bug me now) that when using Log4j

Re: exceptions sometimes are omitted completely

2010-02-19 Thread Yury Luneff
> maybe some kind of service catches all of your > Exceptions maybe a Tapestry filter or dispatcher? > obviously RuntimeExceptions make it through we have spring-security here and Timing filter from default tapestry app. > we also have a large T5 application and never > experienced your pro

T5: logging statements logged twice using Log4j

2010-02-19 Thread britske
Hi, I'm having the problem (always had as far as I remember, but it starts to bug me now) that when using Log4j with Tapestry every log-statement is logged twice to the console. For example, the last few lines before the tapestry is initialized look like this: INFO - ApplicationContext.log(646

Re: exceptions sometimes are omitted completely

2010-02-19 Thread Kristian Marinkovic
maybe some kind of service catches all of your Exceptions maybe a Tapestry filter or dispatcher? obviously RuntimeExceptions make it through we also have a large T5 application and never experienced your problems. except someone added some bugs to our exception reporter :). i'd do a search

Re: exceptions sometimes are omitted completely

2010-02-19 Thread Yury Luneff
right now i have exception stacktrace in log, but none on page: Caused by: java.lang.RuntimeException: Bean editor model for does not contain a property named 'route'. Available properties: carmodel, drivername, endDate, mileage, passengersInsideVehicle, passengersTransported, registrationnum

Re: exceptions sometimes are omitted completely

2010-02-19 Thread Yury Luneff
> configuration.add(SymbolConstants.PRODUCTION_MODE, "false"); so it is definetely not production mode. Actually, code posting here is difficult -- the project is large. As for now I can tell about some problems. I had with model of string like "00:00,00:30,..." for all the day. The bi

Re: [T5.1] Log4j and Application Development/Production Mode

2010-02-19 Thread Peter Stavrinides
> There is any T5 Elegant way so I can automatically switch between > distincts Log4J configurations Yes, I simply place mine side by side in src/main/resources and then just supply a JVM argument to choose the correct one in production, i.e.: -Dlog4j.configuration=log4j_prod.xml if you suppl

Re: exceptions sometimes are omitted completely

2010-02-19 Thread Kristian Marinkovic
hi, can you post some code. i guess you are in tapestry production mode g, kris Yury Luneff 19.02.2010 04:42 Bitte antworten an "Tapestry users" An "Tapestry users" Kopie Thema exceptions sometimes are omitted completely Hello! I'm fighting with my app for features now. Th

Re: [T5.1] Log4j and Application Development/Production Mode

2010-02-19 Thread Igor Drobiazko
Just put your log4j.properties into src/test/resources. This way the config file will be on the classpath of the dev environment and is not shipped inside the war. In production put the config file into the container. 18.02.2010, в 19:13, Everton Agner написал(а): Hi, There is any T5