<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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>
</body></html>