Is anybody out there using iBATIS 3 as their persistence framework inside an
EJB container? I recently started building a new system for which I choose
EJB 3.1 (the version of EJB is actually irrelevant to this question) as my
app framework and iBATIS 3 (this version is relevant!) as my persistence
Clinton,
On Sun, Apr 18, 2010 at 2:45 PM, Clinton Begin wrote:
> You did the right thing... iBATIS transaction managers are meant to be easy
> to implement yourself.
>
Yes, they are easy to implement!
That said, this was a matter of constant debate back in the good old days
> when none of the s
On Mon, Apr 19, 2010 at 8:15 AM, Clinton Begin wrote:
> Thanks Adinath.
>
> This will all help. Let's figure this out together.
>
> The odd thing for me is this. A typical transaction lifecycle (be it
> global or otherwise would be:
>
> * Open Connection
> *
On Mon, Apr 19, 2010 at 10:33 AM, Guy Rouillier wrote:
> I haven't been following this thread closely, but with JBoss at least, you
> have the option of configuring datasources as no-transaction:
> no-tx-datasource. With this type of datasource, you are free to call commit
> and rollback yourself
Clinton,
On Tue, Apr 20, 2010 at 7:48 PM, Clinton Begin wrote:
> Okay, I've looked around. It is really hard to find the way it's
> "supposed" to work, but I don't think it matters. There's more than enough
> empirical evidence (both in iBATIS 2 and Adinath's custom implementation).
> So I've a
