<div><br></div> Wolfgang,<div><br></div><div> Yes, I agree. We've been careful with that we expose on the knowledge-api, but this is clearly an interface that should be there.</div><div><br></div><div> Will take care of it.</div>
<div><br></div><div> Edson<br><br><div class="gmail_quote">On Tue, Jun 26, 2012 at 5:48 AM, Wolfgang Laun <span dir="ltr"><<a href="mailto:wolfgang.laun@gmail.com" target="_blank">wolfgang.laun@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">@Edson: There is, of course, the fundamental problem of the<br>
pseudo-clock feature being full-bodiedly announced in Drools Fusion<br>
but<br>
SessionPseudoClock remaining absent from the stable API. While the<br>
Fusion manual emphasizes (correctly) that a pseudo-clock is useful in<br>
unit test it's important to note that there are good use cases for<br>
using it in certain production scenarios, both of which warrants that<br>
this feature should not be kept under-the-counter.<br>
<span class="HOEnZb"><font color="#888888"><br>
-W<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 26/06/2012, Edson Tirelli <<a href="mailto:ed.tirelli@gmail.com">ed.tirelli@gmail.com</a>> wrote:<br>
> Cyril,<br>
><br>
> Thank you for reporting and providing a well written test case. It<br>
> really helps.<br>
><br>
> We've all been involved with a number of other tasks, including the<br>
> workshops from last week and JBW this week, that prevented me and others<br>
> from working on tickets. Having said that, because the test case in<br>
> JBRULES-3528 was well written, it allowed me to see the problem and<br>
> identify a solution really quickly (literally between meetings). It is<br>
> committed now to both 5.4.x branch and master branch.<br>
><br>
> To other community members that don't know how to report bugs, take a<br>
> look at Cyril's test case (<a href="https://issues.jboss.org/browse/JBRULES-3528" target="_blank">https://issues.jboss.org/browse/JBRULES-3528</a>).<br>
> It is a good example of how to help us help you. You can attach test cases<br>
> to the tickets or send us a pull request in git hub. There are other<br>
> community users that also usually provide good test cases (Wolfgang, just<br>
> to mention one more), but if you don't know how to do it, I really<br>
> recommend you look at that.<br>
><br>
> Edson<br>
><br>
><br>
> On Mon, Jun 25, 2012 at 5:58 AM, Cyril Sochor<br>
> <<a href="mailto:cyril.sochor@gmail.com">cyril.sochor@gmail.com</a>>wrote:<br>
><br>
>> Hi,<br>
>><br>
>> I created two issues in bugtracker, second one with pull request.<br>
>> JBRULES-3528 Deadlock when using pseudo session clock<br>
>> JBRULES-3529 JMS messenger for JBOSS AS 7.1<br>
>><br>
>> Issues are 20 days without any response. What's wrong?<br>
>><br>
>> Thank you,<br>
>> Cyril Sochor<br>
>><br>
>><br>
>> _______________________________________________<br>
>> rules-users mailing list<br>
>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
>><br>
>><br>
><br>
><br>
> --<br>
> Edson Tirelli<br>
> JBoss Drools Core Development<br>
> JBoss by Red Hat @ <a href="http://www.jboss.com" target="_blank">www.jboss.com</a><br>
><br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br> Edson Tirelli<br> JBoss Drools Core Development<br> JBoss by Red Hat @ <a href="http://www.jboss.com">www.jboss.com</a><br>
</div>