RE: Handling Ajax requests when decorating the RequestExceptionHandler

2014-06-26 Thread Davide Vecchi
I believe I'm actually decorating; this is a trimmed version of the code: --- In AppModule.java : @Match(RequestExceptionHandler) public static RequestExceptionHandler decorateRequestExceptionHandler(final Logger logger, final

Re: Handling Ajax requests when decorating the RequestExceptionHandler

2014-06-26 Thread Thiago H de Paula Figueiredo
On Thu, 26 Jun 2014 04:35:52 -0300, Davide Vecchi d...@amc.dk wrote: I believe I'm actually decorating; this is a trimmed version of the code: --- In AppModule.java : @Match(RequestExceptionHandler) public static

RE: Handling Ajax requests when decorating the RequestExceptionHandler

2014-06-26 Thread Davide Vecchi
Is this method invoking super.handleRequestException()? If yes, you don't have to do anything. Actually no, the method is not invoking super.handleRequestException() . I coded it along the lines of Version 3: Decorating the RequestExceptionHandler at

@Persist objects that reference IoC services

2014-06-26 Thread Mihkel Jõhvik
Hi Maybe someone can help alleviate my confusion. I gather (from reading https://tapestry.apache.org/service-serialization.html) that IoC services, when persisted, are done so using tokens. If a service is passed to a POJO and that POJO stored in a session using the @Persist annotation, that

Re: @Persist objects that reference IoC services

2014-06-26 Thread Cezary Biernacki
Do you use proxied service, i.e. one defined as an interface (e.g. via binder.bind(MyService.class, MyServiceImpl.class), not a concrete class? If your service is defined as a concrete class, its instance is used directly. In such case it will be serialised using normal Java rules. Best regards,

Javascript appears as one long line in client; it's hard to debug.

2014-06-26 Thread Claude Andrew
When I try to debug javascript in a client, the whole script appears as a single long line; all the whitespace and comments are missing. I'd like to see my javascript in all its bulky, multi-line, commented glory - at least while I'm debugging. It used to be so but of course I can't figure out

Re: Javascript appears as one long line in client; it's hard to debug.

2014-06-26 Thread Claude Andrew
d'oh. I fixed it myself. It turns out that setting the app.properties setting tapestry.production-mode = false did not work but the following did: AppModule.contributeApplicationDefaults(...){ configuration.add(SymbolConstants.PRODUCTION_MODE, false); ... } I don't know what made me

Re: Javascript appears as one long line in client; it's hard to debug.

2014-06-26 Thread Geoff Callender
It's usually better to supply this as a system property (eg. -Dtapestry.production-mode = false) at runtime. For Jetty in Eclipse, put it in VM Arguments, for Tomcat put it in CATALINA_OPTS, for JBOSS put it in JAVA_OPTS, etc. Geoff On 27 Jun 2014, at 3:01 pm, Claude Andrew