[
https://issues.apache.org/jira/browse/ODE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882944#action_12882944
]
Milinda Lakmal Pathirage commented on ODE-841:
----------------------------------------------
While implementing BPEL4People extension on top of current extension
infrastructure, I noticed that we must give the extension developer the
advantage of JACOB and Channels.
For example, let's take BPEL4People scenario. Once BPEL engine invoke the task
engine to create a task, BPEL process must go to a state where it waits for the
response task engine without blocking any threads. And when the task is
completed and when task engine send the notification to the process, process
should start from the place where it waits for a response from task engine.
this situation is same as one-way <invoke> followed by a <receive>. But we let
the extension developer the chance to handle the selection of correct process
instance.
After a quick hack, I was able to facilitate this by adding some extra
attributes to deploy.xml provide configurations, changing integration layer,
introducing new Channel and couple of other hacks to the
BpelRuntimecontextImpl. But it's a very ugly hack and we should provide a
better way of handling this situation by making the extension development and
deployment mechanism more flexible.
We are still working on figuring out a better solution for this. It's really
helpful if community can tell what they think about providing this kind of
flexibility for BPEL extension development and if you guys have better
alternative please feel free to comment on this.
> Migrating BPEL Extension support to ODE trunk
> ---------------------------------------------
>
> Key: ODE-841
> URL: https://issues.apache.org/jira/browse/ODE-841
> Project: ODE
> Issue Type: New Feature
> Components: BPEL Runtime
> Affects Versions: 1.3.4
> Reporter: Milinda Lakmal Pathirage
> Assignee: Milinda Lakmal Pathirage
> Fix For: 1.3.5
>
> Attachments: ODE-841.patch
>
>
> Current trunk doesn't have BPEL extension support even though extension
> support is there on 2.x-experimental branch. Also when dealing with long
> running extensions like BPEL4People, it's hard implement that type of
> extensions with the current support provided by ODE 2.x-experimental branch.
> First we need to port extension support in 2.x-experimental branch to trunk
> and then improve the support for long running extensions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
