yes, I know that - but if you don't try and export/import via JCR then you can do what you want. <div><br></div><div>The "correct" JCR way to have multiple regions (QA, DEV etc) is actually Workspaces if you read the JCR spec - it is designed for this in mind (and allows this to some extent) - but not sure how that helps with per-package stuff. </div>
<div><br></div><div>IS this exporting and importing a package to a completely separate guvnor instance? </div><div><br></div><div>if so - JCR will not be able to be used - it will have to be a custom file format which can be imported in the other and and adjusted. <br>
<br><div class="gmail_quote">On Fri, Aug 6, 2010 at 5:12 PM, Jervis Liu <span dir="ltr"><<a href="mailto:jliu@redhat.com">jliu@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Michael Neale wrote:<br>
> well for category things - it could be that if a category doesn't<br>
> exist in the target "space" then it is created, if not, it is used.<br>
> There are other things though, which are interlinked - but the same<br>
> issue you bring up applies (which is why this wasn't done a while back).<br>
><br>
> So a simple JCR partial export won't really do - needs to be a bit<br>
> more programmatic than that.<br>
><br>
> The question is - in the target space - do we want to create the<br>
> missing things, or remove the links from them as part of the export<br>
> etc...<br>
><br>
> So if RuleA depends on categoryX and categoryY, but only categoryX<br>
> (same name) exists in the target place, then do we create categoryY<br>
> there, or strip it?<br>
><br>
</div>Things are a little bit more complex than this. The category (and other<br>
things like status etc) attribute is not a plain text value, its a<br>
reference type, essentially its a UUID point to the category nodes. This<br>
UUID value is always invalid in another repository.<br>
<div class="im"><br>
<br>
> On Fri, Aug 6, 2010 at 4:44 PM, Jervis Liu <<a href="mailto:jliu@redhat.com">jliu@redhat.com</a><br>
</div><div><div></div><div class="h5">> <mailto:<a href="mailto:jliu@redhat.com">jliu@redhat.com</a>>> wrote:<br>
><br>
> Hi,<br>
><br>
> I am currently evaluating a Guvnor feature request which is to<br>
> 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<br>
> 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<br>
> 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.<br>
> Firstly, can<br>
> you think of any way to implement this import/export feature?<br>
> Personally<br>
> I dont see how this can be done. This is similar to relational<br>
> 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<br>
> 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<br>
> products,<br>
> how did you manage and how do you want to manage the lifecycle of<br>
> assets<br>
> in your repository?<br>
><br>
><br>
> Thanks,<br>
><br>
> Jervis<br>
><br>
><br>
> _______________________________________________<br>
> rules-dev mailing list<br>
</div></div>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a> <mailto:<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>><br>
<div class="im">> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Michael D Neale<br>
</div>> home: <a href="http://www.michaelneale.net" target="_blank">www.michaelneale.net</a> <<a href="http://www.michaelneale.net" target="_blank">http://www.michaelneale.net</a>><br>
> blog: <a href="http://michaelneale.blogspot.com" target="_blank">michaelneale.blogspot.com</a> <<a href="http://michaelneale.blogspot.com" target="_blank">http://michaelneale.blogspot.com</a>><br>
> ------------------------------------------------------------------------<br>
<div><div></div><div class="h5">><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>
><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>
</div></div></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>