| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Bryan Varner <bvarner(at)polarislabs(dot)com> |
| Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL XAResource & GlassFish 3.1.2.2 |
| Date: | 2013-02-13 20:23:57 |
| Message-ID: | 1360787037.52062.YahooMailNeo@web162904.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
> I think it's more like the JTA authors expect there to be methods
> in the underlying FE/BE protocol to associate/disassociate a
> transaction from the physical connection.
It does seem like we could implement more of the JTA features if an
XAConnection actually managed its own small pool of database
connections when necessary. Whether there is enough demand to
merit the work involved is a whole different question.
If someone wanted it enough to pay for the work, I bet it could be
done. :-)
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryan Varner | 2013-02-13 21:29:12 | Re: PostgreSQL XAResource & GlassFish 3.1.2.2 |
| Previous Message | Heikki Linnakangas | 2013-02-13 17:55:28 | Re: PostgreSQL XAResource & GlassFish 3.1.2.2 |