Anatoly,<br>I see you point too.<br>But you are comparing a clean and high level API the criterias APIs from hibernate, that are also generic.<br>If you want to do with Hibernate a query that creates a relationship between persons and documents, you need to include inside the criteria the person and the document that you want to look for. You don't have something like hibernate.getThePersonAndTheDocumentThatIWant(); <br>
//That's what I see when you ask me about high level apis to get all the waiting work items.<br><br>That's why I think that you need to change the way you think about Drools Flow. I know that you are learning but you don't follow my suggestions. Providing us simple test cases and projects where we can look at and make suggestions.<br>
Now, do you see my point?<br><br><div class="gmail_quote">On Fri, Apr 2, 2010 at 5:44 PM, tolitius <span dir="ltr"><<a href="mailto:webakaunt@gmail.com">webakaunt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
good to get a full response instead of "copy this / yes, you can do that /<br>
etc..".<br>
<br>
actually, I am not sure what I am agreeing with you on :) And it is not<br>
about agreeing, it is about me getting Drools Flow approach, since the<br>
documentation is very high level.<br>
<br>
Where I would really throw forces to make it low-level, that would be<br>
documentation, but not a product APIs.<br>
<br>
That is a definite differences in opinions. Think about other good<br>
frameworks, like Spring and Hibernate for example.<br>
<br>
If I had to do 6 low level calls to get a reference to a bean in Spring, I<br>
would never even consider using it, would go for CDI<br>
<a href="http://jcp.org/en/jsr/detail?id=299" target="_blank">http://jcp.org/en/jsr/detail?id=299</a> right away. (but no, it is as simple<br>
HIGH LEVEL as Autowire or implement a certain (Aware) interface)<br>
<br>
If I had to create 15 queries and write my high level APIs on top of the<br>
Hibernate's low level APIs to make them flexible enough, I would rather use<br>
iBatis, or just GORM (but no I can use a nice HIGH LEVEL Criteria API)<br>
<br>
The point is there should be a healthy balance between the framework and the<br>
client. Now, I am not saying Drools Flow does not have that balance, what I<br>
am saying help me learn Drools Flow in a way that I can use its full power.<br>
And I am SURE that there is a better way in Drools Flow to find all waiting<br>
workitems. Maybe not by a single HIGH LEVEL API call ( not YET :) ), but<br>
surely not through some low level NodeInstance hooks.<br>
<br>
And as far as Java World, Asgard<br>
<a href="http://en.wikipedia.org/wiki/Asgard_%28Stargate%29" target="_blank">http://en.wikipedia.org/wiki/Asgard_%28Stargate%29</a> World, and many other<br>
worlds, clean and simple is always stronger, than weakly-typed, convoluted<br>
and low-level.<br>
<br>
/Anatoly<br>
<font color="#888888">--<br>
View this message in context: <a href="http://n3.nabble.com/Resuming-the-Flow-SESSION-ID-PROCESS-INSTANCE-ID-WORKITEM-ID-tp607507p693769.html" target="_blank">http://n3.nabble.com/Resuming-the-Flow-SESSION-ID-PROCESS-INSTANCE-ID-WORKITEM-ID-tp607507p693769.html</a><br>
</font><div><div></div><div class="h5">Sent from the Drools - User mailing list archive at Nabble.com.<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"><br>-- <br> - <a href="http://salaboy.wordpress.com">http://salaboy.wordpress.com</a><br> - <a href="http://www.jbug.com.ar">http://www.jbug.com.ar</a><br> - Salatino "Salaboy" Mauricio -<br>