Bug 1055693 - Data modeler doesn't register a renamed pojo/object
Summary: Data modeler doesn't register a renamed pojo/object
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Data Modeler
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.0.1
Assignee: Walter Medvedeo
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-20 18:41 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:03:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1001561 0 high CLOSED Changes to data model not picked up 2021-02-22 00:41:40 UTC

Internal Links: 1001561

Description Zuzana Krejčová 2014-01-20 18:41:07 UTC
Description of problem:
While other changes done through external means (as in not through DM but pushed from outside through Git) are visible in the DM, renaming a pojo is not reflected.

By renaming, I mean renaming the file and substituting the new name in all relevant places in the file (class name, constructors).


Version-Release number of selected component (if applicable):
BPMS 6.0 CR1


Steps to Reproduce:
1. Create a new Data Object in the Data modeler.
2. Clone the git repository, rename the file, replace all occurrences of old class name in the file, commit and push.
3. In the Data modeler, change something on the old Data object/class and save.


Additional info:
And this time I'm even using ssh when cloning the repository (bug 1001561 comment 27).


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