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.
Cheers
Sent from my iPhone
On 5 Aug 2012, at 10:03, Maciej Swiderski <mswiders(a)redhat.com> wrote:
Hi guys,
we have discussed that for quite some time so maybe we could gather
various thoughts, ideas on how to proceed. Just to start the discussion
I have following in mind:
- archetype to create domain specific services - already created but
could require some modification as I think there where some changes in
format that work item was defined (not mvel any more??)
- archetype to create test application - very useful in diagnosing
problems reported by community or when writing blogs, how to's so could
be easily downloaded and executed on readers environment
- archetype that integrates jbpm with spring
- archetype for web applications, there could be several flavors:
* archetype for spring MVC web application
* archetype for regular web application (servlets, jsp)??
There could be different options when generating project based on the
archetypes that should cover:
- JPA version selection (JPA 1 (hibernate 3.x) or JPA2 (hibernate 4.x))
- different data base configuration - we could prepare persistence.xml
files for supported data bases
- human task configuration (local or transport based and properly
configure ht work item handlers for selected ht config)
- ....
Anything that we should have for human task to be exposed as remote service?
And discussion is on...
Maciej
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev