Yes, I agree, XQJ seems to be a much more intriguing manner of abstracting the program logic code from the database connection.
you are right, of course. i am sorry, sometimes I use the wrong english words. the project has not seen any much activity lately. the latest news on it was 2003. the working draft was published in 2001 and never seemed to get ratified.
And! it is used by great projects like eXist and works really well. i use it in my java code as well and for eXist it is extremely reliable. i do not mean to say it is not good at what it does. i just am interested i knowing about the new exciting stuff like XQJ and how to use them (and if anyone really is yet?)
xMonkeyOn Fri, Mar 30, 2012 at 9:17 AM, Patrick Bosek <firstname.lastname@example.org> wrote:
I use XMLDB quite a bit as an abstraction. I don't know that I'd consider it dead, but I may well be wrong. Either way, it has it's problems, and like you, I'd like to see a better interface.
Patrick--On Fri, Mar 30, 2012 at 9:03 AM, Xma Monkey <email@example.com> wrote:
i have done a little testing with it (build a db driver, ran some queries). i also joined the XQJ mailing list and the XQJ bug tracker. i see that there are definitely bugs open, and seems like the code-owner is working on them.
i have not checked back in a while on the project (2 weeks now) but i should.
i really like the idea of XQJ as the next replacement for XMLDB. from reading the eXist mailing lists logs, everything is based on XMLDB which looks to be a dead standard.
i would be really interested to know how other users are thinking of XQJ and what they are doing with it (if anything). I wanted to start writing production modules on the driver, but then decided to wait a bit and watch the project and see if the bugs were getting fixed in a timely fashion.
Cell (585) 820 9634
Office (877) 492 2960