Hi Tammo,
Thanks for your valuable response. We'll try that and let you know.
Thanks
Milinda
2010/6/1 Tammo van Lessen
> Hi Milinda,
>
> On 01.06.2010 06:01, Milinda Pathirage wrote:
> > Hi Tammo,
> >
> > Here is what happened in our tests. We are using embedded DB H2 and JPA
> in
> > this sce
Hi Milinda,
On 01.06.2010 06:01, Milinda Pathirage wrote:
> Hi Tammo,
>
> Here is what happened in our tests. We are using embedded DB H2 and JPA in
> this scenario.
>
> When there are about ten or more instances which waits for a human task, we
> can't create anymore instances until several wai
Hi Tammo,
Here is what happened in our tests. We are using embedded DB H2 and JPA in
this scenario.
When there are about ten or more instances which waits for a human task, we
can't create anymore instances until several waiting instance get completed.
And when simple scheduler tries to get a DB
Hi,
sorry, I forgot to answer to the last mail. Let me do this first:
AbstractSyncExtensionOperation is only for implementations that return
(almost) immediately as they block the whole navigation thread (and due
to the instance lock also all further threads). For potentially
long-running transact
Hi Tammo and Rafal,
We are going to try PICK activity like implementation to handle long running
extension activities. We are still working on the implementation. Will that
mechanism allow us to solve this database connection related issue. Will ODE
release db connection
when we go to WAITING like
Hi Tammo and Rafal,
I tried using AbstractAsyncExtensionOperation, but the database connection
problem is still there.
I think that we need to implement run method in AbstractSyncExtensionOperation
to handle async operations.
So that the db connections can be released when we need to. (i.e. after
2010/5/22 Milinda Pathirage
> Hi Tammo and Rafal,
>
> We like to donate BPEL4People extension for ODE and continue development
> inside ODE. I'll start a separate thread on this. Also it'll be great if we
> can get HISE incubator project into ODE project and complete the human task
> implementati
Hi Tammo and Rafal,
We like to donate BPEL4People extension for ODE and continue development
inside ODE. I'll start a separate thread on this. Also it'll be great if we
can get HISE incubator project into ODE project and complete the human task
implementation also inline with BPEL4People extension
Hi Tammo,
2010/5/21 Tammo van Lessen
> Hi Waruna,
>
> On 21.05.2010 13:10, Waruna Ranasinghe wrote:
> >> Which extension operation super class are you using?
> >>
> >
> > extends AbstractSyncExtensionOperation
>
> Ok, the sync extension operation in meant for short running activities
> that ret
Hi Waruna,
On 21.05.2010 13:10, Waruna Ranasinghe wrote:
>> Which extension operation super class are you using?
>>
>
> extends AbstractSyncExtensionOperation
Ok, the sync extension operation in meant for short running activities
that return (almost) immediately. For long-running operations, ple
Hi Tammo,
2010/5/21 Tammo van Lessen
> Hi,
>
> I think it depends on the needs. If you need a quick solution, then I'd
> go with Rafal's suggestion and implement in terms of a BPEL fragment. If
> you want to implement BPEL4People's people activities, the extension
> mechanism is what you want, b
Hi,
I think it depends on the needs. If you need a quick solution, then I'd
go with Rafal's suggestion and implement in terms of a BPEL fragment. If
you want to implement BPEL4People's people activities, the extension
mechanism is what you want, but it is still considered experimental.
AFAIK, long
2010/5/21 Waruna Ranasinghe
> 2010/5/21 Rafal Rusin
>
> > Hello,
> >
> > my suggestion is to use (and possibly extend) external Human Task
> > implementation and connect to it using INVOKEs.
> >
> Yes, I'm using an external Human Task engine.
>
Good.
> If we use INVOKEs, then how are we going
2010/5/21 Rafal Rusin
> Hello,
>
> my suggestion is to use (and possibly extend) external Human Task
> implementation and connect to it using INVOKEs.
>
Yes, I'm using an external Human Task engine.
If we use INVOKEs, then how are we going to correlate messages?
Then we have to add an extra elem
Hello,
my suggestion is to use (and possibly extend) external Human Task
implementation and connect to it using INVOKEs.
This way you will have better separation of components.
You can use Apache HISE for it (http://incubator.apache.org/hise/).
On Thu, May 20, 2010 at 10:25 PM, Waruna Ranasinghe
Hi Rafal,
I'm trying to implement peopleActivity for BPEL4People as an BPEL extension
activity
You may already aware of this and peopleActivity is a blocking activity.
It is quite convenient to use an extension activity rather than a separate
process since we need to correlate messages and etc...
Hello,
is it possible to decompose your extension activity into a process, which
will wait for few hours and invoke only
quick parts of code?
On 12 May 2010 23:51, Waruna Ranasinghe wrote:
> Hi devs,
>
> I have been writing a bpel extension activity which does an external
service
> call and wait
Hi devs,
I have been writing a bpel extension activity which does an external service
call and waits for the response.
The activity itself is a blocking activity. It may have to wait for hours to
get the response, so that it may take hours to complete the activity.
Problem is, If I create few ins
18 matches
Mail list logo
