1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Java API JCA / CAJ DBR_LONG |
From: | [email protected] |
To: | [email protected] |
Date: | Wed, 31 Jan 2018 09:08:53 +0100 |
Hi,
I do not know JCAE. Quickly looking at the code it is a wrapper around JCA. I was funded by PSI to write “ca”. I reused stable CAJ core but ditched old JCA interfaces and replaced them with modern Java 8 interfaces. Afterwards PSI took over and added more features. One thing I note is that it appears that JCAE has a client *and* a server implementation, while ca has just a client. Is that right? Are there plans to add a server implementation to ca? I do not know. However, CAJ server side interfaces are more modern than JCA (but CAJS still use JCA DBR classes instead of generics). I would go with ca client + CAJ server.Would JCAE still be a sound choice for a new project that needed a client *and* a server implementation, or even a sound choice for a project that needed just a server implementation? Or would it be better to avoid it because it's being phased out, instead going with ca for the client and CAJ (even though dated) for the server? Cheers, Matej |