On Tue, Feb 10, 2009 at 2:33 AM, Martin Meyers <[email protected]> wrote: > >> > 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'd recommend starting with Extension Guide [1] and check some of the extension samples (e.g implementation.pojo) In this case, you could share the same model/processor being used by current implementation.bpel, or develop your own (see. BPELImplementationProcessor). The next thing is to look into the ImplementationProviderFactory and ImplementationProvider, this is where we currently start the Embedded ODE server and deploy the BPEL process. Then there is the invoker, that is responsible to intercept the calls and process the communication/invocation with the BPEL engine. One thing to keep in mind is that, in order to support the ability to have BPEL partnerLinks wired to sca components (what we call Reference Support), you will need to be able to put some kind of invocation interceptor in the ActiveBPEl side, so you can make the invocation to the sca reference. Well, this is probably a very high level description of the Tuscany side of the BPEL extension, There is also the ODE Embedded server, but you are probably not very interested on this piece. The BPEL Implementation processor is located in the implementation-bpel module, the rest of the code is available in implementation-bpel-ode module in tuscany. [1] http://tuscany.apache.org/sca-java-extension-development-guide.data/ExtendingTuscany1.pdf > 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 > > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
