Hi, Gnana:

This could be a bug, but it's hard to be sure without more detail.

Would I be right in assuming that you have created a custom snippeting 
transform?  v7 did include some work on snippeting for JSON.  Can you provide 
specifics about the input to the transform, the transform code, and the output 
from the transform?


Erik Hennum

________________________________
From: general-boun...@developer.marklogic.com 
[general-boun...@developer.marklogic.com] on behalf of 
gnanaprakash.bodire...@cognizant.com [gnanaprakash.bodire...@cognizant.com]
Sent: Tuesday, November 26, 2013 2:04 AM
To: general@developer.marklogic.com
Subject: [MarkLogic Dev General] JSON issue in MarkLogic 7

Hi

I recently updated my MarkLogic server from v6 to v7 and I got an issue with 
json conversion.

Details:
MarkLogic 6:
As part of REST-API, when we supply the parameter format=json, the entire 
response was getting converted into JSON irrespective of what we have in 
content node.

i.e. By default we get search suggestions but I used transformation to get the 
full document and converted them to JSON which ensured I get results in JSON 
format.

MarkLogic 7:
We now additionally have mimetype and format in JSON response which I believe 
are coming from REST decorator.

Even though when I supply format=json, the decorator is searching for document 
type and making it as xml format because of which raw content node is treated 
as string.

Is there any way we can fix this or is this what we need to live with?

Another question,
My assumption is whenever REST API is updated, MarkLogic will use version 
numbers like /v1/, /v2/…/LATEST to ensure we are not losing the old REST API. 
Is this not available now?

Gnana(GP)

Gnanaprakash Bodireddy | Sr. Associate – Projects | IME | Cognizant Technology 
Solutions.
Address: Manyata Embassy Business Park, Outer Ring Road, Rachenahalli, 
Bangalore, Karnataka, Pin :560045
O: +91 (80) 66808000 extn: 502406| Mobile: +91 8197558899

This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful.
_______________________________________________
General mailing list
General@developer.marklogic.com
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to