> > Concerning the mentioned "implementation-bpel-jbpm module" (and as I am 
> > still a newbie to Tuscany/ODE):
> > (a) Would such an implementation take a long time?  and
> > (b) Would it be envisioned for these coming days?
> 
> This really depends on the level of understanding you have with JBPM
> internals to create the extension, I'd certainly be able to help on
> the Tuscany/SCA side.

Unfortunately, I never have used jBPM up till now.
But having looked over the main concepts of jBPM, this product wouldn't achieve 
my envisioned goals (w/o any impl extensions), because
(a) its WS-BPEL 2.0 module don't support BPEL4People PeopleActivity, and
(b) a "human task management system" also would be required. Here it obviously 
would be "Tempo" which is not 100% WS-HumanTask conformant. 

Both aspects would already be available using ActiveBPEL as "external Tuscany 
enhancement". 


So, even if the integration of jBPM would be the more proper solution for 
Apache Tuscany, the "external" extension using ActiveBPEL 5.0 with its already 
implemented BPEL4People *and* WS-HumanTask subcomponents would be completely 
sufficient for my case. Here I "only" would be dealing with the incorporation 
of the existing components into Tuscany and less with concrete subsystem 
implementations.

Envisioning the integratation of ActiveBPEL 5.0 as 
"implementation.bpel.activebpel" impl extension, and to ge a better picture of 
the workload to come, could someone please tell me what has to be done to 
achieve this goal as well as point me to the appropriate implemented Tuscany 
components and their documentation documents???
(A global sketching would be very helpful, if possible).

I guess most of the work would be similar to the "implementation.bpel(.ode)" 
artifacts, wouldn't it?

Thanks a lot for your explications.

Best regards,
  Martin  

_______________________________________________________________________
Jetzt 1 Monat kostenlos! WEB.DE FreeDSL - Telefonanschluss + DSL
für nur 17,95 EURO/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K13805B7069a

Reply via email to