Hi Jesús,
In your stackoverflow you are talking about Java API and about XCC, but you may have missed that when we talk about Java API we really mean the Java Client API that is a convenient and new Java library on top of the REST Client API. For both you can find documentation on http://docs.marklogic.com . XCC on the other hand is a quite a lot older Java library for connecting to MarkLogic, and is much more low-level. CRUD functionality should be supported by both the Java and REST Client API out of the box.. Kind regards, Geert *Van:* [email protected] [mailto: [email protected]] *Namens *Jesús Zazueta *Verzonden:* donderdag 29 augustus 2013 17:23 *Aan:* [email protected] *Onderwerp:* [MarkLogic Dev General] Current state of the Java API Hello everyone. Another Marklogic neophyte here. Recently, I've been trying to implement a simple CRUD prototype to teach myself the inner workings of MarkLogic using the Java API. However, I have found that the Java API isn't as robust, complete or documented as the XQuery/XSLT and REST API's. Specifically, my reasons for thinking this are within this stack overflow question. "Document XPath searching with Marklogic's Java search API vs XQuery/XSLT API" http://stackoverflow.com/questions/18496468/document-xpath-searching-with-marklogics-java-search-api-vs-xquery-xslt-api I think my only option would be to use XCC or the REST apis. Since the query builder part of the Java API is deprecated, are there any plans to bring fluent querying capabilities back to the Java API? Pretty much like what QueryDSL (http://www.querydsl.com/) provides? Thank you. ------------------------------------ Jesús Zazueta M.
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
