false.
> > > <http://?auth=DQAAAHcAAABRNsIxA9tiVL3uczzey-x8FmU4gCUONPWKQAnlvhxhlFsCgDWBe2vo5cADP4RK1n0C-wf599ttpb3KuVGEQ1juQ4qqo7J7q47y0qAH12dW5DBAfbWjNSE-kzSN7uva1VddYFgwsvDPJHEKd2xLegIlVRPoMUsCpGd8rccaRUkjtg&shva=1>
> > > Ex: true
> > >
> > > d) We
service author can retrieve
> it and call commit, rollback etc.
>
> e) We can create an XASession instead of a normal session based on
> configuration, provided the JMS provider supports it.
> Ex. true
>
> Comments are very much appreciated.
>
> Regards,
>
> Rajith
>
&g
Hi,
I've been unable to find anything on the topic in Nabble, so I thought I'd
ping you all, and Asankha in particular regarding transactions in the JMS
transport implementation.
In ODE we'd like to be able to consume/send messages through AXIS' JMS
transport. That in itself is not a problem. Howe
