The transaction is needed by the ProcessStore in order to persist the
process information.
I will research and see if there are any workarounds.
On Tue, May 27, 2008 at 2:21 PM, Mike Edwards
<[EMAIL PROTECTED]> wrote:
> Luciano Resende wrote:
>>
>> Very good news Mike !!! I hope to start working on the db issues as
>> soon as I get some free cycles.
>>
>
> Luciano,
>
> There is something that you might be able to help me with right away.
>
> I am running into intermittent problems with transactions in the
> registration of a BPEL process with the ODE server. The transaction causing
> the problem seems to be the one in the BPELImplementationProvider start()
> method.
>
> What is this transaction for?
>
> try {
> txMgr.begin();
> odeServer.registerTuscanyRuntimeComponent(implementation.getProcess(),
> component);
>
> odeServer.deploy(new ODEDeployment(deploymentDir), implementation );
> txMgr.commit();
> } catch (Exception e) {
> e.printStackTrace();
> txMgr.rollback();
> }
>
>
> Will it cause a problem if I remove this transaction? To me it does not
> seem to provide any value when the Process is being supplied by Tuscany. I
> can't see any requirement for it in the ODE documentation.
>
>
> Yours, Mike.
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
