If you're not using a proxy then you have to give the client the login
credentials to your MarkLogic instance and expose the REST port that will
answer nearly any arbitrary search request. If you're OK with giving the world
unlimited access to the REST API, you can and it will technically work,
Hi, Gnanaprakash:
Good to hear you're making progress.
XML and JSON have fundamentally different models. Some XML cases have no
natural representation in JSON and vice versa. That fundamental mismatch means
that there is no standard transform from XML to JSON. (You can search to see
some of
Hi Erik
Thanks for the help.
I have created the options and it worked fine for me. But I got results which
is slightly deviating from my expectation.
Options: custom-search
http://marklogic.com/appservices/search";>
URL:
http://<>:9000/v1/search?q=&options=custom-search&format=json<
Hi Charles
All the documents I ingested are XML's not JSON. But as our application is
consuming JSON I have to give the response in JSON which is why I explored XML
to JSON Api.
To summarize,
1. I have a schema defined for just to ensure JSON is handling data types
2. I have a Schematron define
