You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ilia Naryzhny (JIRA)" <ji...@apache.org> on 2014/01/08 03:20:51 UTC

[jira] [Created] (WICKET-5465) WicketTester.newFormTester() should work within RequestCycle

Ilia Naryzhny created WICKET-5465:
-------------------------------------

             Summary: WicketTester.newFormTester() should work within RequestCycle
                 Key: WICKET-5465
                 URL: https://issues.apache.org/jira/browse/WICKET-5465
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 6.12.0
            Reporter: Ilia Naryzhny


Application is using JPA for working with database.
Transaction/EntityManager is opened and closed with the aid of RequestCycle listener.

But there is a place when WicketTester can initiate working with JPA/DB not with in transaction. That is there:

WicketTester.newFormTester() invokes "new FormTester" and there is following place within FormTester constructor:

String[] values = getInputValue(formComponent);  //(line number 399 for wicket 6.12.0)

Ofcause, finally, this leads to DB invocation out of transaction and lots of other bad stuff.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)