Bug 778717 (SOA-1181)

Summary:	PersistenceDbServiceTest and PersistenceServiceDbTest are dependent
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Jiri Pechanec <jpechane>
Component:	JBPM - within SOA	Assignee:	Alejandro Guizar <alex.guizar>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP01	CC:	dlesage
Target Milestone:	---
Target Release:	4.3 CP04 ER1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1181
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-25 09:33:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Pechanec 2009-02-18 06:49:19 UTC

Date of First Response: 2009-03-10 05:41:02
project_key: SOA

See JBPM-2047

Comment 1 Jiri Pechanec 2009-02-18 06:49:35 UTC

Link: Added: This issue depends JBPM-2047

Comment 2 Thomas Diesler 2009-03-10 09:41:02 UTC

Tom, could you please reassign appropriately.

Comment 3 Alejandro Guizar 2010-01-14 09:18:41 UTC

Resolving platform issue as JBPM-2047 is resolved.

Comment 4 David Le Sage 2010-02-25 03:15:15 UTC

Please review following.  Draft of the  Resolved Issues section of Release Notes states:


https://jira.jboss.org/jira/browse/JBPM-2047

    PersistenceDbServiceTest and PersistenceServiceDbTest could fail, depending
    upon the order in which they are run. If PersistenceDbServiceTest was run first, it
    set the session factory to MockSessionFactory. This configuration was then retained by                                                                                           
    subsequent jbpmContexts. Unfortunately, the PersistenceServiceDbTest requires
    that the session factory be null. This led to calls to operations that were not supported by the
    MockSessionFactory.

    To resolve this problem, the PersistenceDbServiceTest and all other tests that use custom
    configurations now explicitly close on tearDown. As a result, these tests now all work as
    intended.

Comment 5 Jiri Pechanec 2010-03-25 09:33:38 UTC

Verified in ER1