Subject | Re: [Firebird-Java] Removing JCA support with Jaybi rd 5 |
---|---|
Author | Mark Rotteveel |
Post date | 2018-11-18T11:07:13Z |
On 18-11-2018 11:20, Arioch The ariochthe@... [Firebird-Java] wrote:
releases of Jaybird starting at 1.0.1; not sure what happened with 1.0.0
;)), but I'm not going to actively advertise it.
And of course, Jaybird 4 is not even released yet, and Jaybird 5 is
still far away, so JCA will be with us for the time being.
As far as I can tell, no one is actively using the JCA implementation
itself (judging by (lack of) issues in the tracker and activity on this
list and elsewhere), but as the JDBC driver itself relies on it, it is
one of the primary causes of questions about using Jaybird because
people either forget to include the connector-api jar, or deploy the
jaybird-full jar instead of the jaybird jar to a Java EE implementation,
which then refuses to load the jar because it contains javax.* packages.
It is also a roadblock for me, because I'm hesitant to touch code in
those parts for fear of breaking JCA.
If people actively expressed interest in the JCA implementation and are
actually using it, I will have no problem restructuring Jaybird so the
JDBC implementation no longer directly relies on JCA, and a provide a
separated JCA implementation. But given the lack of said interest, I
think my time will be better spent just removing JCA and removing some
warts in Jaybird to support use as a plain JDBC driver and as a JCA
implementation.
Mark
--
Mark Rotteveel
> I met talks when people had to implement JCA and could not find a singleThe code and builds will remain available (you can still download all
> example.
>
> So it would be great if last JCA-supporting JayBird remained published
> forever and maybe even was advertized as production read JCA impl example
releases of Jaybird starting at 1.0.1; not sure what happened with 1.0.0
;)), but I'm not going to actively advertise it.
And of course, Jaybird 4 is not even released yet, and Jaybird 5 is
still far away, so JCA will be with us for the time being.
As far as I can tell, no one is actively using the JCA implementation
itself (judging by (lack of) issues in the tracker and activity on this
list and elsewhere), but as the JDBC driver itself relies on it, it is
one of the primary causes of questions about using Jaybird because
people either forget to include the connector-api jar, or deploy the
jaybird-full jar instead of the jaybird jar to a Java EE implementation,
which then refuses to load the jar because it contains javax.* packages.
It is also a roadblock for me, because I'm hesitant to touch code in
those parts for fear of breaking JCA.
If people actively expressed interest in the JCA implementation and are
actually using it, I will have no problem restructuring Jaybird so the
JDBC implementation no longer directly relies on JCA, and a provide a
separated JCA implementation. But given the lack of said interest, I
think my time will be better spent just removing JCA and removing some
warts in Jaybird to support use as a plain JDBC driver and as a JCA
implementation.
Mark
--
Mark Rotteveel