Re: [jbpm-dev] [JBPM 5.x] service task repository
I don't think it's about one or the other, I believe both are valid options and
have their pros and cons. The current approach, using a simple directory structure (on
disk or over HTTP) was selected as the best option for the prototype as it is very easy to
set up and maintain (you don't need to run Guvnor to have a service repo). Note that
guvnor can be exposed as a file system using WebDAV, so you can use the same approach
already but store the services on Guvnor to take benefit of versioning, import/export in
Eclipse, etc.
Longer-term, Guvnor is being extended to act as a repository for all different types of
data, and having a section for service tasks would definitely make sense. As part of
making the management of the life cycle more flexible, we're looking at supporting
configurable life cycles (for example using a process), in which case this could also be
leveraged to specify how new service tasks could be added to the repository, etc. But
that is probably a longer-term feature.
Kris
----- Oorspronkelijk bericht -----
Van: "Mauricio Salatino" <salaboy(a)gmail.com>
Aan: "Giovanni Marigi" <gmarigi(a)redhat.com>
Cc: jbpm-dev(a)lists.jboss.org
Verzonden: Dinsdag 13 maart 2012 17:11:18
Onderwerp: Re: [jbpm-dev] [JBPM 5.x] service task repository
At some point those definitions should be stored in guvnor right? Until now I think
it's just a folder with some meta-data files to define what is in there, but I think
that it really make sense to put that functionality inside guvnor that is a fully fledged
repository right?
Guvnor already provide the APIs to push resources, and we definitely need to add a kind of
workflow for resources.. but it's not there yet.
Cheers
On Tue, Mar 13, 2012 at 4:08 PM, Giovanni Marigi < gmarigi(a)redhat.com > wrote:
Hi,
I would like to know the status of service task repository;
I really appreciate the idea behind it and delivering some POC, customers were really
enthusiastic about this feature (especially its integration with jbpm designer and BRMS)
but it seems that the actual repo doesn't have some new effort.
Will we provide API to push service tasks to the repository? I think it should be useful
to provide some mechanism to approve a new service task before to make it public.
Thanks,
Giovanni
--
Giovanni Marigi
Red Hat - JBoss Consultant -
email: gmarigi(a)redhat.com
Mobile: +39 3423175986
Office: +39 0687502315
Red Hat Italy
Via Andrea Doria 41m
00192 Roma - Italy
www.redhat.com
Prima di stampare, pensa all'ambiente ** Think about the environment before printing
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev
--
- MyJourney @ http://salaboy.wordpress.com
- Co-Founder @ http://www.jugargentina.org
- Co-Founder @ http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev