[
http://jira.jboss.com/jira/browse/JBRULES-1109?page=all ]
Michael Neale closed JBRULES-1109.
----------------------------------
Resolution: Won't Fix
This is a feature of JCR.
If in future it is desired to be able to import history - this will be considered - but
that is a much bigger task, as it is more of a backup and restore (which you can do with
files/database at the moment).
Have created a feature request JIRA for this: JBRULES-1161
Exported BRMS repositories lose version history
-----------------------------------------------
Key: JBRULES-1109
URL:
http://jira.jboss.com/jira/browse/JBRULES-1109
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-brms
Affects Versions: 4.0.0.GA
Environment: Windows XP SP2, SUN JRE 1.5_09
Reporter: Shahad Ahmed
Assigned To: Michael Neale
Fix For: FUTURE
I've come across an issue with exporting and importing a BRMS repository backup,
which I'm not sure is a feature or a bug. I have a package that contains a bunch of
rules I've developed. I've modified and saved rules, so that most of the rules
have a fairly long history when you select the Version History in the rule view. If I
export the repository in the Admin/Manage Backups section and then import the repository
into a clean BRMS installation, all the version history of the rules seems to be lost. The
rules still have the correct version attribute (e.g. version: 8 etc), but when you click
on the View History link it just says No History.
If you actually export and then re-import the rules into the same BRMS installation, then
the History is maintained - however, I suspect that is purely by chance as the underlying
repository is not being cleaned up by the import option?
Here's how to replicate the problem for a clean BRMS install:
1. Create a new category called test.
2. In the defaultPackage create a new technical rule called test as shown below:
when
eval(true)
then
System.out.println("Hello");
3. Save the test rule
4. Modify test rule e.g. by changing "Hello" to "Hello World" and
Save the rule agin to get a version 2 of the rule.
5. Click on the View History option to verify that the rule has a single historical
version 1 in the repository.
6. From Admin/Manage Backups save the repository.
7. In a new clean BRMS install import the previously exported repository (I guess if you
do not want to reinstall the BRMS you can shutdown the original and remove the repository
directory, the repository.xml and derby.log files, and then restart to get an empty
repository).
8. Open the test rule created previously. It should show up with version 2. Click on the
View History option and it says No History. The conclusion is that the back feaure does
not back up the full repository i.e. history is lost.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira