Re: [T5.4 build 22] Exception in ExceptionReport.tml

Noticed you had asked the same question on Stackoverflow ( http://stackoverflow.com/questions/31477722/tapestry-5-4-exception-in-exceptionreport-tml/31598497) so I replied there. The problem is related to GAE's restrictions on spawning new threads. Kalle On Sat, Jul 18, 2015 at 8:00 AM, Michał Wi

Re: Ajaxformloop add row link max size.

I'd just like to close the loop a little bit as in the end I asked this on SO also. Here is a link to the same question with an answer. It's not ideal, but for my use case it's ok. http://stackoverflow.com/questions/31518944/tapestry5-ajaxformloop-limit-number-of-rows/31619004#31619004 On 15 July

Re: Advanced transaction support for tapestry JPA applications

Hi Kalle, In JPA 2.1 it's BeanManager that is responsible for creating objects of entity listeners. BeanManager implementation from this library uses ObjectLocator.autobuild() to create these instances, so you may @Inject pretty much everything as you do with regular tapestry services. As for con

Re: Advanced transaction support for tapestry JPA applications

Thanks Dmitry, looks excellent. Even so that I don't see any reason we shouldn't merge this to tapestry's core JPA integration at some point. I didn't read the code that carefully, but do the injectable JPA entitylisteners also support (totally non-spec) constructor injection? Do you know if the co

Re: Zone event, new client id

Sorry, this is the submit of a zone event. Here is all of the relevant code. I did check, afterRender is not called in the chain. The log line that is generated with this code is: [INFO] components.EmailForm tinymce.execCommand('mceAddEditor',true,'null'); Thanks again for any help. @InjectC

Re: Zone event, new client id

Hi Tony, In which render phase are trying to access the client id? It may help if you post parts of your code. Injecting the component to access the client id works for me (for the following common pattern): @Environmental private JavaScriptSupport javaScriptSupport; @Component private Select

Zone event, new client id

I have a small form in a zone. When an error occurs in the event handler, I need to execute some javascript, which I’m adding with the ajaxResponseRender. I can’t figure out how to access the clientId of the component that will be rendered. If I try to use the Injected component, I get NULL fo

Re: Advanced transaction support for tapestry JPA applications

Hi Tony, I think so, but new TransactionalUnitWorker works the same as default one ( CommitAfterWorker). It won't start a transaction unless you have @CommitAfter on execution path. Maybe you're talking about starting transactions if no DB calls were made from method annotated with @CommitAfter?

Re: Forms created in a loop - problem with validation

I think this is caused by the field being reused in the loop. You might need to recordError with a FieldSnapshot. Example here http://t5stitch-lazan.rhcloud.com/mapbindingdemo

Re: Advanced transaction support for tapestry JPA applications

This does look very interesting. A while back, Howard built a custom commit handler for me, that delays creating the transaction until a method with @CommitAfter is seen. Does your library have a similar side effect, of not starting the transaction because only methods marked with @CommitAfter

Re: Forms created in a loop - problem with validation

These examples might help... If you’re not using AJAX then it probably makes more sense to put the Form around the Loop: T5.4: http://jumpstart.doublenegative.com.au/jumpstart7/examples/tables/editableloop1

Forms created in a loop - problem with validation

Hello,   I have a loop that creates a few forms and I have implemented the onValidate method to validate the input. If an error occours in the textarea of the first form, the textareas of all other forms are marked as erroneous too, although the forms and textareas have different IDs. Whats wro