+1 to have maven archetypes. Creating a jbpm project with persistence and human tasks from the scratch is really annoying.<div>I would go to maven first and then to forge. I'm not 100% sure about what forge is and the real benefits it has. Its CLI resembles Spring ROO and that makes me shivers :). But of course, the most frameworks come with jBPM integration, the better!</div>
<div><br></div><div>Best Regards, <br clear="all"><br>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br><br>Esteban Aliverti<br>- Blog @ <a href="http://ilesteban.wordpress.com" target="_blank">http://ilesteban.wordpress.com</a><br>
<br><br><div class="gmail_quote">On Sun, Aug 5, 2012 at 12:51 PM, Salaboy <span dir="ltr"><<a href="mailto:salaboy@gmail.com" target="_blank">salaboy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A project that may become useful is jboss forge, I met one of the leaders and he told me that jbpm should have somethere as well, we should look at that option as well and analyZe if there is an overlap with our archetypes proposals.<br>
Cheers<br>
<br>
Sent from my iPhone<br>
<div class="HOEnZb"><div class="h5"><br>
On 5 Aug 2012, at 10:03, Maciej Swiderski <<a href="mailto:mswiders@redhat.com">mswiders@redhat.com</a>> wrote:<br>
<br>
> Hi guys,<br>
><br>
> we have discussed that for quite some time so maybe we could gather<br>
> various thoughts, ideas on how to proceed. Just to start the discussion<br>
> I have following in mind:<br>
> - archetype to create domain specific services - already created but<br>
> could require some modification as I think there where some changes in<br>
> format that work item was defined (not mvel any more??)<br>
> - archetype to create test application - very useful in diagnosing<br>
> problems reported by community or when writing blogs, how to's so could<br>
> be easily downloaded and executed on readers environment<br>
> - archetype that integrates jbpm with spring<br>
> - archetype for web applications, there could be several flavors:<br>
> * archetype for spring MVC web application<br>
> * archetype for regular web application (servlets, jsp)??<br>
><br>
> There could be different options when generating project based on the<br>
> archetypes that should cover:<br>
> - JPA version selection (JPA 1 (hibernate 3.x) or JPA2 (hibernate 4.x))<br>
> - different data base configuration - we could prepare persistence.xml<br>
> files for supported data bases<br>
> - human task configuration (local or transport based and properly<br>
> configure ht work item handlers for selected ht config)<br>
> - ....<br>
><br>
><br>
> Anything that we should have for human task to be exposed as remote service?<br>
><br>
> And discussion is on...<br>
> Maciej<br>
> _______________________________________________<br>
> jbpm-dev mailing list<br>
> <a href="mailto:jbpm-dev@lists.jboss.org">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>
<br>
_______________________________________________<br>
jbpm-dev mailing list<br>
<a href="mailto:jbpm-dev@lists.jboss.org">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></div>