Thomas,<br><br>Thanks for putting your ideas clearly in a document. It helps me to understand some things you&#39;ve been saying. <br><br>There are points in the document that deserve discussion.However, I do get the impression that you see the ideal jBPM as a &#39;standalone service&#39;. ie you signal a process to start and then poll the service until you get a response. This is a valid use case, ie the JBoss server + the enterprise jbpm EJBs come close to this idea (altough the are some flaws, that is true). <br>
<br>But I think that you are forgetting that many (or almost every, altough in my experience) use jBPM in an embedded way. Many use cases see a process engine call as an integral part of some business logic unit of work that has to run in the same transaction. For example a save to the database of a domain model (employee for example) is only valid when the enlisting process is started correctly.<br>
<br>This is the great strength of jBPM, compared to other products (mostly exposing BPM as a service that can be queried through some (remote) api), that jBPM can easily be embedded in any technology: I&#39;ve used jBPM with Spring, with EJBs (MDB, statelss SB), as a webservice, etc. Many vendors provide monolithic BPM service products. I think jBPM has become popular with developers because it is exactly the opposite.<br>
<br>Please clarify if I&#39;m seeing this all wrong! But the opinion I got when I read your document was not that of an embeddable BPM engine.<br><br>If I see the level of the dicussion going on nowadays, I&#39;m really looking forward to next week!<br>
<br>Regards<br><br>Joram<br><br><div class="gmail_quote">On Tue, Oct 28, 2008 at 3:21 PM, Tom Baeyens <span dir="ltr">&lt;<a href="mailto:tbaeyens@redhat.com">tbaeyens@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks !<br>
This preparation will make the discussions a lot more effective/productive.<br>
<br>
regards, tom.<br>
<br>
ps. for the third time, please don&#39;t involve Kris in this before synchronizing with me. &nbsp;It will be hard enough for our team to synchonize internally. &nbsp;Kris&#39; opinion differs at even completely other aspects. &nbsp;And I didn&#39;t see yet the necessary flexibility from him to get him involved. &nbsp;For the time being, I&#39;ll deal with that. &nbsp;And I&#39;ll get him involved when there is a chance of unification of the two efforts.<div class="Ih2E3d">
<br>
<br>
<br>
Thomas Diesler wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Folks,<br>
<br>
in preparation for the meeting in Antwerp, here a few design considerations<br>
<br>
<a href="http://www.jboss.org/community/docs/DOC-12855" target="_blank">http://www.jboss.org/community/docs/DOC-12855</a><br>
<br>
Thanks for your feedback and look forward to meeting you next week.<br>
<br>
cheers<br>
-thomas<br>
<br>
</blockquote>
<br>
-- <br></div>
regards, tom.<div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
jbpm-dev mailing list<br>
<a href="mailto:jbpm-dev@lists.jboss.org" target="_blank">jbpm-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbpm-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a><br>
</div></div></blockquote></div><br>