Bug 777495 (SOA-7) - Migration scenario - from jBPM PROJECT to SOA PLATFORM - we need to define, document, and verify/test
Summary: Migration scenario - from jBPM PROJECT to SOA PLATFORM - we need to define, d...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-7
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CR3
Assignee: Mike Brock
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA-7
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-21 15:34 UTC by Len DiMaggio
Modified: 2013-06-17 05:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-14 21:36:42 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-7 0 None Closed Migration scenario - from jBPM PROJECT to SOA PLATFORM - we need to define, document, and verify/test 2012-06-12 01:10:37 UTC

Description Len DiMaggio 2007-08-21 15:34:04 UTC 
Date of First Response: 2007-09-24 15:34:22
project_key: SOA

The discussion of this migration scenario started in the SOA Platform test plan - http://intranet.corp.redhat.com/ic/intranet/SOAplatformQEPlan.html#migration

Migration scenario - from jBPM to SOA Platform - we need to define, document, and verify/test the process by which users can migrate - including users running jBPM with database releases older than the releases supported by the SOA Platform.
Comment 1 Len DiMaggio 2007-08-23 19:21:33 UTC 
The test execution for this task will be tracked in Testify.
Comment 2 Len DiMaggio 2007-08-28 19:16:10 UTC 
Link: Added: This issue is a dependency of JBQA-926
Comment 3 Mike Brock 2007-09-24 19:34:22 UTC 
We need to speak about this.  I am going to bring this up at the meeting.
Comment 4 Mike Brock 2007-11-14 21:36:42 UTC 
We're assuming we will not be providing this in 1.0
Note You need to log in before you can comment on or make changes to this bug.