Announcement Announcement Module
Collapse
No announcement yet.
AbstractTransactionalSpringContextTests Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • AbstractTransactionalSpringContextTests

    I have gotten a lot of mileage out of using AbstractTransactionalSpringContextTests to manage the transaction lifecycles of my tests.

    For some of my tests I would like to manage lifecycles for additional resources, and I was hoping to extend AbstractTransactionalSpringContextTests to create test cases that manage the additional resources.

    However, I have been frustrated by the fact that both onSetUp() and onTearDown() are declared final. Is there a good reason for these methods to be final?

    If there is no compelling reason, I will submit a JIRA request to have the final declaration removed in a future rev.

    Thanks,
    Corby

  • #2
    Corby,

    did you consider using onSetUpInTransaction / onTearDownInTransaction?

    HTH

    Comment


    • #3
      Ah, yes, well... I guess that's what those methods are there for.

      Thanks for the help,
      Corby

      Comment

      Working...
      X