Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345106 - Not possible to delete Projects from the embedded database
Summary: Not possible to delete Projects from the embedded database
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P2 blocker (vote)
Target Milestone: Indigo RC3   Edit
Assignee: Zeb Ford-Reitz CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
: 345131 346835 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-05-09 05:04 EDT by Tim Winselmann CLA
Modified: 2011-06-01 03:59 EDT (History)
3 users (show)

See Also:


Attachments
Log when delete project (1.29 KB, application/octet-stream)
2011-05-17 07:50 EDT, Felix Ziesel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Winselmann CLA 2011-05-09 05:04:48 EDT
It is not possible to delete projects from the embeddedDB in Jubula EPP. This behavior occurs just in Jubula EPP, not in the Bredex Jubula.

Maybe this is caused by the used Eclipse Link 2.3 (because the Indigo Release of Eclipse) in Jubula EPP. In the Bredex Jubula we are using Eclipse Link 2.2.
Comment 1 Felix Ziesel CLA 2011-05-17 07:50:13 EDT
Created attachment 195840 [details]
Log when delete project
Comment 2 Zeb Ford-Reitz CLA 2011-05-17 08:17:50 EDT
I was unable to reproduce the error by simply creating and then deleting a Project. After looking at the log file, it is apparent that a database constraint on a parent-child relationship (essentially, a Test Case that contains a Test Case Reference) is violated.

Here are some steps to reproduce the error:
 1. Create (and open) a new Project.
 2. Create two new Test Cases ("TC1" and "TC2").
 3. Open TC1 and add a Reference to TC2.
 4. Close the editor for TC1.
 5. Delete TC1.

An error occurs (complete with error dialog), and the Test Case is not successfully deleted.
Comment 3 Zeb Ford-Reitz CLA 2011-05-17 08:41:30 EDT
This indeed appears to be caused by the switch from EclipseLink 2.2 to EclipseLink 2.3. I am unable to reproduce the problem with a Jubula that uses EclipseLink 2.2, but i am able to reproduce the problem with a Jubula that uses EclipseLink 2.3.
Comment 4 Tim Winselmann CLA 2011-05-23 02:41:05 EDT
Also occurred with Jubula as Plugin in the Eclipse Indigo Release RC1.
Comment 5 Markus Knauer CLA 2011-05-23 03:00:14 EDT
(In reply to comment #4)
> Also occurred with Jubula as Plugin in the Eclipse Indigo Release RC1.

Good (from an EPP's point of view...) - I couldn't think of a relationship between this error and the Testing EPP package.
Comment 6 Zeb Ford-Reitz CLA 2011-05-23 05:04:45 EDT
*** Bug 346835 has been marked as a duplicate of this bug. ***
Comment 7 Zeb Ford-Reitz CLA 2011-05-24 12:26:15 EDT
Definitely a bug in EclipseLink (bug 347010), and not database-, platform-, or packing-specific. I've marked that bug as blocking this one.
Comment 8 Zeb Ford-Reitz CLA 2011-05-27 08:38:53 EDT
fixed with the workaround implemented in http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=965bb3103fb80a431d49cee870887794288a1459
Comment 9 Tim Winselmann CLA 2011-05-31 08:54:37 EDT
The steps from comment 3 does not led to the error message anymore. In addition projects are now deletable from the embedded database.
Comment 10 Zeb Ford-Reitz CLA 2011-06-01 03:59:38 EDT
*** Bug 345131 has been marked as a duplicate of this bug. ***