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 running extension activities have not yet been implemented with it, but I'd appreciate any kind of comments to improve it so that it fully supports this scenarios. We'd also appreciate a code donation of the BPEL4People implementation of course (I'm pretty sure that it needs additional extensions to ODE, besides the extension activity) ;)
Which extension operation super class are you using? Best, Tammo On 21.05.2010 07:25, Waruna Ranasinghe wrote: > 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... > > So do you think that I should drop the extension and go for a separate > process? > WDYT? > > > Thanks, > Waruna > > On 21 May 2010 10:19, Rafal Rusin <[email protected]> wrote: > >> 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 <[email protected]> wrote: >>> 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 instances from this process, after sometime >> it >>> will complain about getting database connections saying that "No >>> ManagedConnections available within configured blocking timeout ( 30000 >> [ms] >>> ) for pool >>> org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor" >>> >>> I think this happens due to the Extension activity which takes hours to >> get >>> completed, so that the db connection also holds on to it until the >> activity >>> get completed >>> >>> Therefore, If we can close the connection after external service call, I >>> think we can fix this issue. >>> >>> Any body aware of how to close the db connection within an extension >>> activity or any other work around?? >>> >>> >>> Thanks, >>> Waruna >>> >>> >>> -- >>> ----------------------------------------------------- >>> Regards, >>> Waruna Ranasinghe >>> BLOG: http://warunapw.blogspot.com >>> >> >> -- >> Regards, >> Rafał Rusin >> http://rrusin.blogspot.com >> > > > -- Tammo van Lessen - http://www.taval.de
