<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5921" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=700073607-06082010><FONT face=Arial
color=#0000ff size=2>If the use-case of migrating packages through the
environments holds true I'd expect the meta-data associated with packages to
remain constant.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=700073607-06082010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=700073607-06082010><FONT face=Arial
color=#0000ff size=2>Perhaps I've made an assumption that you don't have
categories called "Production rules", "QA rules" etc.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=700073607-06082010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=700073607-06082010><FONT face=Arial
color=#0000ff size=2>Thinking wider; is there a requirement to allow
export\import to be sliced and diced many different ways:-</FONT></SPAN></DIV>
<UL dir=ltr>
<LI>
<DIV align=left><SPAN class=700073607-06082010><FONT face=Arial color=#0000ff
size=2>Export\import a category</FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=700073607-06082010><FONT face=Arial color=#0000ff
size=2>Export\import a package</FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=700073607-06082010><FONT face=Arial color=#0000ff
size=2>Export\import working set</FONT></SPAN></DIV></LI>
<LI>
<DIV align=left><SPAN class=700073607-06082010><FONT face=Arial color=#0000ff
size=2>etc</FONT></SPAN></DIV></LI></UL><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> rules-dev-bounces@lists.jboss.org
[mailto:rules-dev-bounces@lists.jboss.org] <B>On Behalf Of </B>Michael
Neale<BR><B>Sent:</B> 06 August 2010 08:00<BR><B>To:</B> Rules Dev
List<BR><B>Subject:</B> Re: [rules-dev] Package based import/export in
Guvnor<BR></FONT><BR></DIV>
<DIV></DIV>well for category things - it could be that if a category doesn't
exist in the target "space" then it is created, if not, it is used. There are
other things though, which are interlinked - but the same issue you bring up
applies (which is why this wasn't done a while back).
<DIV><BR></DIV>
<DIV>So a simple JCR partial export won't really do - needs to be a bit more
programmatic than that. </DIV>
<DIV><BR></DIV>
<DIV>The question is - in the target space - do we want to create the missing
things, or remove the links from them as part of the export etc... </DIV>
<DIV><BR></DIV>
<DIV>So if RuleA depends on categoryX and categoryY, but only categoryX (same
name) exists in the target place, then do we create categoryY there, or strip
it? <BR><BR>
<DIV class=gmail_quote>On Fri, Aug 6, 2010 at 4:44 PM, Jervis Liu <SPAN
dir=ltr><<A href="mailto:jliu@redhat.com">jliu@redhat.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<BR><BR>I
am currently evaluating a Guvnor feature request which is to
implement<BR>package based import/export. The idea is to use this feature to
move a<BR>rule package from the DEV repo to QA to Stage to the Prod repo.
For<BR>details please check <A
href="https://jira.jboss.org/browse/GUVNOR-311"
target=_blank>https://jira.jboss.org/browse/GUVNOR-311</A>. My<BR>initial
investigation shows that it is not possible to do a single<BR>package
import/export technically. A single package in Guvnor repository<BR>is never
a self-contained unit. For example, every asset under the<BR>package has a
mandatory attribute which is a reference link to category<BR>information. In
short, package can not be exported/imported as long as<BR>it contains
references to entities outside package.<BR><BR>There are two things I would
like to ask for your opinions. Firstly, can<BR>you think of any way to
implement this import/export feature? Personally<BR>I dont see how this can
be done. This is similar to relational database,<BR>generally it is
impossible to export and import data from/to a single<BR>non-isolated table
in database. Or sometimes it is possible but with<BR>extensive care normally
involved in manual work to deal with dirty data.<BR>In our case, one example
of dirty data is category, but what can we do<BR>with category information,
we discard package information when we do<BR>package
export?<BR><BR>Secondly, if such feature can not be implemented, can we
figure out a<BR>different way to help users to better manage the life cycle
in Guvnor?<BR>The current version of Guvnor is not very strong on this part
yet. If<BR>you are a Guvnor user or you have experience of using similar
products,<BR>how did you manage and how do you want to manage the lifecycle
of assets<BR>in your
repository?<BR><BR><BR>Thanks,<BR><BR>Jervis<BR><BR><BR>_______________________________________________<BR>rules-dev
mailing list<BR><A
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</A><BR><A
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target=_blank>https://lists.jboss.org/mailman/listinfo/rules-dev</A><BR></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>Michael D Neale<BR>home: <A
href="http://www.michaelneale.net">www.michaelneale.net</A><BR>blog: <A
href="http://michaelneale.blogspot.com">michaelneale.blogspot.com</A><BR></DIV></BLOCKQUOTE></BODY></HTML>