Bug 1002095 - Nonexistent package is used by new process definition
Nonexistent package is used by new process definition
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: jBPM Designer (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Tihomir Surdilovic
Sona Mala
Depends On:
  Show dependency treegraph
Reported: 2013-08-28 09:14 EDT by Sona Mala
Modified: 2013-08-28 09:28 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-28 09:28:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Process definition with Project Explorer and Properties Bar (72.72 KB, image/png)
2013-08-28 09:14 EDT, Sona Mala
no flags Details

  None (edit)
Description Sona Mala 2013-08-28 09:14:50 EDT
Created attachment 791396 [details]
Process definition with Project Explorer and Properties Bar

Description of problem:
If you create new process definition then property "Package" always contains "org.jbpm". No matter in which package you create the process definition or if project contains this package.

See attached screenshot.

Version-Release number of selected component (if applicable):
BPMS 6.0.0 ER2

How reproducible:

Steps to Reproduce:
1. Create a new project "myProject" (org.myproject, 1.0)
2. Check that there is not any package
3. Create new process definition
4. Take a look at property "Package"

Actual results:
Property "Package" contains "org.jbpm".
I do not know WHERE YOU TAKE IT!!! Is it some kind of default value?
No such package in the project!!!

Expected results:
I hope that this property should correspondent with package in which is process definition created. The highlighted areas in screen shot should contain same text. For:
   - default package - this property should be empty or contains some expression for default package as "defaultPackage" or "<default>" etc.
   - org.myproject - this property should be org.myproject

Additional info:

Note You need to log in before you can comment on or make changes to this bug.