Re: Selenium test cases fail building 5.4

2016-02-26 Thread Bob Harner
Yep, sorry we didn't get the docs updated before you ran into that. As you saw, an older Firefox version is needed. (Or, current Firefox versions work with upgraded versions of Selenium (v2.52.0) long as a build.gradle is switched to use Java 1.7 or newer.) Firefox 42 worked On Friday, February 26

Re: Selenium test cases fail building 5.4

2016-02-26 Thread Barry Books
Firefox 42 worked On Friday, February 26, 2016, Barry Books wrote: > I downloaded Firefox version 40 and it at least tries to run the test > cases but crashes. Is there a preferred version? > > On Friday, February 26, 2016, Barry Books > wrote: > >> Now that 5.4 is out I'd like to submit a coup

Re: Selenium test cases fail building 5.4

2016-02-26 Thread Barry Books
I downloaded Firefox version 40 and it at least tries to run the test cases but crashes. Is there a preferred version? On Friday, February 26, 2016, Barry Books wrote: > Now that 5.4 is out I'd like to submit a couple of small patches so I > downloaded 5.4 and followed the instructions here > >

Selenium test cases fail building 5.4

2016-02-26 Thread Barry Books
Now that 5.4 is out I'd like to submit a couple of small patches so I downloaded 5.4 and followed the instructions here https://tapestry.apache.org/building-tapestry-from-source.html everything went smoothly but the following tests fail ActivationContextIntegrationTests. testStartup Act

Re: Calling method after CommitAfter call

2016-02-26 Thread Thiago H de Paula Figueiredo
On Fri, 26 Feb 2016 07:54:47 -0300, g kuczera wrote: But I feel quite ashamed of this solution. It's like forcing the inner mechanism of Tapestry's Hibernate Wrapper (or even the Hibernate by itself, it's flow) to commit the thing before it is appropriate. I disagree. Tapestry-Hibernate i

Re: Calling method after CommitAfter call

2016-02-26 Thread Dmitry Gusev
Hi, The tapestry-jpa-transactions module doesn't use any JPA interceptors, its before/after commit hooks are implemented in the same advice that opens and commits transactions for @CommitAfter. In theory you could do the same for Hibernate too. But in your case you could extract business logic th

Re: Calling method after CommitAfter call

2016-02-26 Thread g kuczera
Thanks for the comprehensive answer. Right now I am testing the HibernateSessionManager usage. I added it as the field in my page: @Inject private HibernateSessionManager hibernateSessionManager; and then I commit it in the onFormSubmit method: public void onFormSubmit(Object observable, Ob

Re: [5.3.7] Application stops working after some time

2016-02-26 Thread Nathan Quirynen
Hi, No index does not persist anything. But it's not a problem with the index page I think. It looks like a more global problem as when trying to access any page I get this error, only it will not say 'Index' in the following, but the name of the page I try to access instead. [ERROR] ioc.Reg

Re: [5.3.7] Application stops working after some time

2016-02-26 Thread Eugen
Hi, do You have some session persistencies in the Index page? Is it the time of SessionTimeout? 2016-02-26 10:47 GMT+01:00 Nathan Quirynen : > Forgot to say that this error is thrown when trying to access any page. > > > > On 26/02/16 10:37, Nathan Quirynen wrote: > >> Hi, >> >> I have a weird pr

Re: [5.3.7] Application stops working after some time

2016-02-26 Thread Nathan Quirynen
Forgot to say that this error is thrown when trying to access any page. On 26/02/16 10:37, Nathan Quirynen wrote: Hi, I have a weird problem where an application stops working after some random time. A restart of Tomcat "fixes" it temporarily. Anyone know where the problem could be? [ERROR

[5.3.7] Application stops working after some time

2016-02-26 Thread Nathan Quirynen
Hi, I have a weird problem where an application stops working after some random time. A restart of Tomcat "fixes" it temporarily. Anyone know where the problem could be? [ERROR] ioc.Registry java.lang.ArrayIndexOutOfBoundsException [ERROR] ioc.Registry Operations trace: [ERROR] ioc.Registry [