<p>Hi Mark,</p>
<p>I was meaning the SPI is in Expert/Core/Knowledge-API/whatever. </p>
<p>So I can use a KJAR containing, for example, a .smurf file from Java (i.e. no Guvnor) provided I have registered a handler that can generate DRL from a .smurf.</p>
<p>Guvnor would simply register those it needs for it's persistent formats.</p>
<p>sent on the move</p>
<p>On 17 Dec 2012 06:37, "Mark Proctor" <<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Agreed. Guvnor should just define an spi for incremental compilers and result messages integration. Then a thin plugin just delegates to the existing kie infrastructure.<div><div><br></div>
<div>M<span></span><br><br>On Sunday, 16 December 2012, Michael Anstis wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>I was thinking over the weekend.</p>
<p>Guvnor has many different file types it uses to store rule definitions.</p>
<p>Currently Guvnor builds DRL before passing this to KieBuilder via KieStorage (erm, will do this).</p>
<p>Any thoughts on moving the conversion to DRL from Guvnor to pluggable builders within Kie that accept defined file-types (you have DRL and XLS at the moment).</p>
<p>This further makes Guvnor just the "rule management" component having knowledge base building (from any resource type) within Expert.</p>
<p>Guvnor would obviously provide all the pluggable builders it needs for 6.0.</p>
<p>Just a thought...</p>
<p>sent on the move</p>
</blockquote></div></div>
</div><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></blockquote></p>