<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.E-MailFormatvorlage18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=DE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Okay, and what is the situation now? Waiting for the perfect
world ;-) <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Or maybe having something on top to be dependent on the app
server? Or move that part to the ESB integration?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think especially in the Repository, this is an enterprise
feature where all these questions get more interesting (than with the “plain”
rule engine which is more easily embeddable). Actually I cannot judge the philosophy
of Drools Guvnor and the connection to SOA-P here, but from my personal point
of view a good integration in the JBoss AS and EJB3 world would be really nice.
Maybe this could be on top and the Guvnor core could still be deployable on
other environments?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
rules-dev-bounces@lists.jboss.org [mailto:rules-dev-bounces@lists.jboss.org] <b>Im
Auftrag von </b>Michael Neale<br>
<b>Gesendet:</b> Donnerstag, 4. März 2010 23:12<br>
<b>An:</b> Rules Dev List<br>
<b>Betreff:</b> Re: [rules-dev] Accessing JCR repository directly<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>yes that was exactly my point.
at that time we weren't prepared or willing to create app specific wars/sars.
In a perfect world the war would work in all containers (that isn't really
possible it seems) but also be able to work in non EE containers (that may be a
JNDI issue? eg with jetty can be a hassle). <o:p></o:p></p>
<div>
<p class=MsoNormal>On Fri, Mar 5, 2010 at 8:16 AM, Bernd Rücker <<a
href="mailto:bernd.ruecker@camunda.com">bernd.ruecker@camunda.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'>I think JNDI Deployment
always require an application server (or not?). For JBoss the best way would be
to provider a sar… But from a war you could register it manually as well I
think, but this could get app server specific…</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>Von:</span></b><span style='font-size:10.0pt'> <a
href="mailto:rules-dev-bounces@lists.jboss.org" target="_blank">rules-dev-bounces@lists.jboss.org</a>
[mailto:<a href="mailto:rules-dev-bounces@lists.jboss.org" target="_blank">rules-dev-bounces@lists.jboss.org</a>]
<b>Im Auftrag von </b>Michael Neale<br>
<b>Gesendet:</b> Donnerstag, 4. März 2010 04:35</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
<b>An:</b> Rules Dev List<br>
<b>Betreff:</b> Re: [rules-dev] Accessing JCR repository directly<o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>right
yes - the JNDI binding of JCR would make sense - but I wasn't sure how that
could be delivered as a self contained war to "drop in" and not
require significant container specific integration (correct me if wrong). <o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
Wed, Mar 3, 2010 at 8:08 PM, Bernd Rücker <<a
href="mailto:bernd.ruecker@camunda.com" target="_blank">bernd.ruecker@camunda.com</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hmm,
okay REST is one option. But I still would prefer to bind the JCR<br>
Repository in the JNDI (which is easily possible). This is an option we<br>
used already a couple of times for JackRabbit applications. By doing so,<br>
everybody in the app server can access it via JNDI, like any other<br>
datasource as well (and basically that's what a JCR Repository is).<br>
<br>
The only dependency is to have JCR on the classpath, ok.<br>
<br>
I think for the moment I will create a Servlet which reads it from Seam<br>
and binds the Repository to JNDI. What do you think?<br>
<br>
Having a REST or Webdav API INSIDE of the Appserver to talk from Java to<br>
Java just sounds technically unnecessary complicated to me...<br>
<br>
-----Ursprüngliche Nachricht-----<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Von:
<a href="mailto:rules-dev-bounces@lists.jboss.org" target="_blank">rules-dev-bounces@lists.jboss.org</a><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>[mailto:<a
href="mailto:rules-dev-bounces@lists.jboss.org" target="_blank">rules-dev-bounces@lists.jboss.org</a>]
Im Auftrag von Jervis Liu<br>
Gesendet: Mittwoch, 3. März 2010 08:55<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>An:
Rules Dev List<br>
Betreff: Re: [rules-dev] Accessing JCR repository directly<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Bernd
Rücker wrote:<br>
><br>
> Hi Michael.<br>
><br>
> Thanks for the quick answer!<br>
><br>
> Our use case at the moment is, that we maintain the HEAD version of<br>
> the rules in an own table locally in the app, where we have a<br>
> specialized GUI for authoring. As soon as they get released we<br>
> leveraged the RuleTemplate to generate a DRL file, which we want to<br>
> check in Guvnor, from where the deployment snapshots are created,<br>
> versioned and so on. So we have to access Guvnor programmatically<br>
> (doesn’t have to be JCR).<br>
><br>
> A second nice use case we face is to hang in the Drools Repository<br>
> into a bigger JCR-Content-Tree (in the area of ModeShape), so there<br>
> JCR would be nice. Then we could use the JCR Explorer, written from<br>
> one of my colleagues, to have a look at the repos as well. But okay,<br>
> this is why we want to use JCR.<br>
><br>
> But the most important issue is to access the Repository<br>
> programmatically from an EJB3. Maybe we could get around classloading<br>
> isolation and just access some static stuff for that. Or making the<br>
> ServiceImplementation really more generic usable, that would be<br>
> wonderful as well. But as it sounds it will take some time and will<br>
> not be released pretty soon? Then we have to find another way for now,<br>
> since if avoidable I don’t want to patch drools. So you mean I should<br>
> use the internal Remote Interface the GWT GUI is using? Where can I<br>
> find that and how can I create a correct reference?<br>
><br>
> Or I have to use Webdav, but this looks pretty cumberstone to use it<br>
> internally in one JBoss server instead of pure Java mechanisms?<br>
><br>
> Thanks and cheers<br>
><br>
> Bernd<br>
><br>
<br>
Hi Bernd, this might be related:<br>
*<a
href="http://lists.jboss.org/pipermail/rules-users/2009-December/011618.html"
target="_blank">http://lists.jboss.org/pipermail/rules-users/2009-December/011618.html</a><br>
<br>
*Basically the idea is that you expose ServiceImplementation as a remote<br>
service. As far as how the remote service is implemented, one way to go<br>
is to expose ServiceImplementation as RESTful service. Guvnor already<br>
has some Atom/Pub capabilities.It may not match your request yet, but if<br>
you have a concrete requirement on what methods in ServiceImplementation<br>
you want to expose remotely, we can look into it and get it addressed<br>
either by extending Atom/Pub capabilities that Guvnor already has (for<br>
this, take a look at<br>
<a
href="http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-guvnor/sr%0d%0ac/main/java/org/drools/guvnor/server/files/"
target="_blank">http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-guvnor/sr<br>
c/main/java/org/drools/guvnor/server/files/</a>)<br>
or by providing a truly RESTful service layer on top of Guvnor server.<br>
<br>
Cheers,<br>
Jervis<br>
><br>
> *Von:* <a href="mailto:rules-dev-bounces@lists.jboss.org" target="_blank">rules-dev-bounces@lists.jboss.org</a><br>
> [mailto:<a href="mailto:rules-dev-bounces@lists.jboss.org" target="_blank">rules-dev-bounces@lists.jboss.org</a>]
*Im Auftrag von *Michael<br>
Neale<br>
> *Gesendet:* Montag, 1. März 2010 00:27<br>
> *An:* Rules Dev List<br>
> *Betreff:* Re: [rules-dev] Accessing JCR repository directly<br>
><br>
> Hi Bernd. yes you have it correctly - seam starts things up.<br>
><br>
> IN terms of accessing JCR directly, this came up before and one idea<br>
> was to use the "remote" JCR interface - that means some
refactoring I<br>
> guess.<br>
><br>
> So the basic design is that there is a JCR server that starts up, and<br>
> the "clients" connect remotely (a client in this case is also
the<br>
> Guvnor server side).<br>
><br>
> That way you can access it from multiple places. However, it may be a<br>
> bit too low level for this - the question is what do you want to<br>
> access JCR for from your external app?<br>
><br>
> A better approach, is to make the ServiceImplementation a true remote<br>
> interface (at the moment it is, but for GWT clients only) - so ANY<br>
> sort of client can connect and access the guvnor services, without<br>
> messing with low level data structures - I am thinking the latter is<br>
> the superior approach (and someone else was looking at it).<br>
><br>
> Michael.<br>
><br>
> On Sun, Feb 28, 2010 at 4:53 AM, Bernd Rücker<br>
> <<a href="mailto:bernd.ruecker@camunda.com" target="_blank">bernd.ruecker@camunda.com</a>
<mailto:<a href="mailto:bernd.ruecker@camunda.com" target="_blank">bernd.ruecker@camunda.com</a>>>
wrote:<br>
><br>
> Hey guys.<br>
><br>
> I thought I better ask that question on the dev list, correct me if<br>
> that was a bad choice ;-)<br>
><br>
> I want to programmatically access the JCR repository from another<br>
> application (basically to author rules). I understood the<br>
> RulesRepository (which is a nice interface by the way). I tried to<br>
> understand how the JCR Session is created and can be accessed. As far<br>
> as I found it, it seems that a Seam Bean just starts everything<br>
> (RulesRepositoryManager). Now the question is: How can I access this<br>
> from another application? Because the workspace is locked, I cannot<br>
> create another Session from there.<br>
><br>
> Wouldn’t it be nice to bind the stuff in JNDI correctly or something<br>
> like that? Or if I do that, can I inject it into the Seam application?<br>
> Or maybe I can access the seam bean somehow from external?<br>
><br>
> I think it would be the easiest and best to access the JCR repos<br>
> instead of using WebDav or whatever if I am in another EJB3 application…<br>
><br>
> Thanks a lot for any hint<br>
><br>
> Cheers<br>
><br>
> Bernd<br>
><br>
> --<br>
><br>
> Blog: _<a href="http://www.bpm-guide.de" target="_blank">www.bpm-guide.de</a>
<<a href="http://www.bpm-guide.de" target="_blank">http://www.bpm-guide.de</a>>_<br>
><br>
> ---------------------------------------------<br>
><br>
> camunda services GmbH - The Business Process Company<br>
><br>
> Zossener Straße 55-58 - 10961 Berlin<br>
><br>
> <a href="http://www.camunda.com" target="_blank">www.camunda.com</a> <<a
href="http://www.camunda.com" target="_blank">http://www.camunda.com</a>> - <a
href="mailto:info@camunda.com" target="_blank">info@camunda.com</a><br>
> <mailto:<a href="mailto:info@camunda.com" target="_blank">info@camunda.com</a>><br>
><br>
> ---------------------------------------------<br>
><br>
> Bernd Rücker<br>
><br>
> Geschäftsführer<br>
><br>
> Telefon +49 30 664040 901<br>
><br>
> Mobil +49 171 1473461<br>
><br>
> <a href="mailto:bernd.ruecker@camunda.com" target="_blank">bernd.ruecker@camunda.com</a>
<mailto:<a href="mailto:bernd.ruecker@camunda.com" target="_blank">bernd.ruecker@camunda.com</a>><br>
><br>
> ---------------------------------------------<br>
><br>
> Amtsgericht Charlottenburg: HRB 113230 B<br>
><br>
> Geschäftsführer: Jakob Freund, Bernd Rücker<br>
><br>
> ---------------------------------------------<br>
><br>
> BPMN-Buch: <a href="http://www.hanser.de/buch.asp?isbn=978-3-446-41768-7"
target="_blank">http://www.hanser.de/buch.asp?isbn=978-3-446-41768-7</a><br>
><br>
> EJB-3-Buch: <a href="http://www.ejbbuch.de/" target="_blank">http://www.ejbbuch.de/</a><br>
><br>
><br>
> _______________________________________________<br>
> rules-dev mailing list<br>
> <a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a>
<mailto:<a href="mailto:rules-dev@lists.jboss.org" target="_blank">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>
><br>
> --<br>
> Michael D Neale<br>
> 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>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> rules-dev mailing list<br>
> <a href="mailto:rules-dev@lists.jboss.org" target="_blank">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" target="_blank">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>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">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><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>
<br clear=all>
<br>
-- <br>
Michael D Neale<br>
home: <a href="http://www.michaelneale.net" target="_blank">www.michaelneale.net</a><br>
blog: <a href="http://michaelneale.blogspot.com" target="_blank">michaelneale.blogspot.com</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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><o:p></o:p></p>
</div>
<p class=MsoNormal><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><o:p></o:p></p>
</div>
</body>
</html>