Re: exceptions sometimes are omitted completely
> 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 problems. except someone > added some bugs to our exception reporter :). i'd like that too > i'd do a search for try/catch blocks and analyze > them. i guess it is not a Tapestry problem. nothing of that is here. at least in our code. the suspicion is to spring-security and tapestry-spring-security from nu.localhost.tapestry - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: exceptions sometimes are omitted completely
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 for try/catch blocks and analyze them. i guess it is not a Tapestry problem. g, kris Yury Luneff 19.02.2010 12:03 Bitte antworten an "Tapestry users" An "Tapestry users" Kopie Thema Re: exceptions sometimes are omitted completely 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, registrationnumber, startDate. at org.apache.tapestry5.internal.beaneditor.BeanModelImpl.get(BeanModelImpl.java:152) at org.apache.tapestry5.internal.beaneditor.BeanModelImpl.reorder(BeanModelImpl.java:213) at org.apache.tapestry5.internal.beaneditor.BeanModelUtils.reorder(BeanModelUtils.java:100) at org.apache.tapestry5.internal.beaneditor.BeanModelUtils.modify(BeanModelUtils.java:46) at org.apache.tapestry5.corelib.components.Grid.getDataModel(Grid.java:502) at org.apache.tapestry5.corelib.components.GridColumns.setupRender(GridColumns.java:113) at org.apache.tapestry5.corelib.components.GridColumns.setupRender(GridColumns.java) at org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.invokeComponent(ComponentPageElementImpl.java:184) at org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.run(ComponentPageElementImpl.java:164) at org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:933) ... 125 more [ERROR] InternalModule.PagePool Page Page[waybill/List ru] is dirty, and will be discarded (rather than returned to the page pool). i mean, it is something not quite right if tapestry doesn't do its exception reports. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: exceptions sometimes are omitted completely
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, registrationnumber, startDate. at org.apache.tapestry5.internal.beaneditor.BeanModelImpl.get(BeanModelImpl.java:152) at org.apache.tapestry5.internal.beaneditor.BeanModelImpl.reorder(BeanModelImpl.java:213) at org.apache.tapestry5.internal.beaneditor.BeanModelUtils.reorder(BeanModelUtils.java:100) at org.apache.tapestry5.internal.beaneditor.BeanModelUtils.modify(BeanModelUtils.java:46) at org.apache.tapestry5.corelib.components.Grid.getDataModel(Grid.java:502) at org.apache.tapestry5.corelib.components.GridColumns.setupRender(GridColumns.java:113) at org.apache.tapestry5.corelib.components.GridColumns.setupRender(GridColumns.java) at org.apache.tapestry5.internal.structure.ComponentPageElementImpl$SetupRenderPhase.invokeComponent(ComponentPageElementImpl.java:184) at org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.run(ComponentPageElementImpl.java:164) at org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:933) ... 125 more [ERROR] InternalModule.PagePool Page Page[waybill/List ru] is dirty, and will be discarded (rather than returned to the page pool). i mean, it is something not quite right if tapestry doesn't do its exception reports. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: exceptions sometimes are omitted completely
> 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 binded property was of type Time (, java.sql.Time time. Of course, it leads to some kind of exception while the form submits. But I don't receive any of it. I change "time" type to String (it will work too for me) and everything is ok. But I had to guess the reason of just blank page. As I remember, even in production mode tapestry can say something about "internal server error" :) - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: exceptions sometimes are omitted completely
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. There is a problem about valueencoders and such and i guess this problem should report as any kind of exception - either the beautiful one done by tapestry or at least stacktrace in log window. But tapestry chooses neither. Just empty page and that's all. Sometime ago this also happened a lot - one mistake in property binding and you get the right exception sometimes, but sometimes you get completely nothing. "Debug" in log4j doesn't quite help here. Did anyone meet that behavior? It is very unpleasant to debug something with empty pages and no exceptions (log4j, btw, is set for error level as default which should do exceptions). - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
exceptions sometimes are omitted completely
Hello! I'm fighting with my app for features now. There is a problem about valueencoders and such and i guess this problem should report as any kind of exception - either the beautiful one done by tapestry or at least stacktrace in log window. But tapestry chooses neither. Just empty page and that's all. Sometime ago this also happened a lot - one mistake in property binding and you get the right exception sometimes, but sometimes you get completely nothing. "Debug" in log4j doesn't quite help here. Did anyone meet that behavior? It is very unpleasant to debug something with empty pages and no exceptions (log4j, btw, is set for error level as default which should do exceptions). - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
