Giovanni,
I agree completely. But we want to make sure that the ones we publish there are verified
and documented, so it simply takes some time.
About an open API, we definitely want to provide an "open process". A wizard
that allows you to define and upload your service tasks is probably the best solution, but
maybe using JIRA in a similar way (and having this process documented) might be acceptable
as the next best thing?
Kris
----- Oorspronkelijk bericht -----
Van: "Giovanni Marigi" <gmarigi(a)redhat.com>
Aan: "Kris Verlaenen" <kverlaen(a)redhat.com>
Cc: jbpm-dev(a)lists.jboss.org
Verzonden: Dinsdag 13 maart 2012 20:31:02
Onderwerp: Re: [jbpm-dev] [JBPM 5.x] service task repository
Kris,
I was wondering why the workitems included in the jbpm-workitems module are not in the
repo :-) some of them are really useful and I took inspiration from the java handler to
create a EJB work item.
I don't know if it's too much risky but opening it to the community with a kind of
"open" API to publish servie tasks, maybe can give even more enthusiasm to jbpm
5.x
Another point; I think the old jbpm 3 suffered from the lack of "adapters"; if
there is a maintained and public repo with service tasks I think even the integration
between jbpm and external systems can be easier.
Giovanni
----- Original Message -----
From: "Kris Verlaenen" <kverlaen(a)redhat.com>
To: "Giovanni Marigi" <gmarigi(a)redhat.com>
Cc: jbpm-dev(a)lists.jboss.org
Sent: Tuesday, March 13, 2012 8:23:32 PM
Subject: Re: [jbpm-dev] [JBPM 5.x] service task repository
Giovanni,
You are right, the current repo hasn't been extended to include the other service
tasks that are already implemented in the jbpm-workitems module. Some of them have
already been configured, documented and tested and should just be uploaded, I'll try
to do that asap. We have made it an action item that every team member contributes a
service task to the repository once in a while.
We would also welcome contributions. There is no predefined automated process there, but
we would like to evaluate if JIRA might be used for this purpose (where the necessary
files are attached, we review and add to the repository). But we welcome any feedback.
The service repository integration currently is based on a defined directory structure
that allows us to figure out which services are available. If you set up your own
repository (local or HTTP), you can easily control access to it. At this point, we
don't have a management process to automate this, since developing service tasks like
this is probably a job for developers, and they usually don't have any problems to
upload completed service tasks to a directory somewhere. But again, feel free to provide
feedback.
Kris
----- Oorspronkelijk bericht -----
Van: "Giovanni Marigi" <gmarigi(a)redhat.com>
Aan: jbpm-dev(a)lists.jboss.org
Verzonden: Dinsdag 13 maart 2012 17:08:11
Onderwerp: [jbpm-dev] [JBPM 5.x] service task repository
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
--
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