Hi. Thanks for the clarification. I've edited my stack overflow question. But that still misses the point I think.
Now, my 2 cents :P. My SO question still supports the point that the Java client API can do regular CRUD, but search functionality, while indeed supported, is only done so via obsolete classes or XML/JSON querying options. In summation, I accept the fact that structured search can and does work with the Java client API; but it is cumbersome. A much better approach would be to provide a fluent querying API similar to LINQ or QueryDSL. I'd be interested in knowing the reasons for dropping the Query builder classes of the Java client API since they more or less provided the aforementioned functionality. Hence my initial question here. I hope the Marklogic team is listening and are able to measure how much adoption has the Java client API received among their user base. In my case, if it were on me to make a technical decision about using this client API, I'd currently give it a no go. Thanks again for your time and help! JZM ------------------------------------ Jesús Zazueta M. On Thu, Aug 29, 2013 at 10:57 AM, Geert Josten <[email protected]>wrote: > 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 > >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
