# Alternatives to JSON output, XML?

**URL:** <https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470>\
**Category:** Elasticsearch\
**Created:** [January 23, 2013, 11:18am UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470 "2013-01-23T11:18:27Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dominic\_Watson\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dominic_watson_2/32/2517_2.png) [@Dominic\_Watson\_2](https://discuss.elastic.co/u/Dominic_Watson_2)\
**Post date:** [January 23, 2013, 11:18am UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470/1 "2013-01-23T11:18:27Z")

</div>

Hi there, we have some legacy applications that are running on a platform  
with appalling JSON deserialization performance. Does anyone know of any  
plugins / options for returning alternative outputs, i.e. XML?

This is for _responses_ coming from the REST api.

Thanks in advance,

D

--

---

<div class="post-metadata">

**Author:** ![Tanguy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy1/32/1749_2.png) [@Tanguy1](https://discuss.elastic.co/u/Tanguy1)\
**Post date:** [January 23, 2013, 11:35am UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470/2 "2013-01-23T11:35:58Z")

</div>

Hi Dominic,

The following plugin can be found to return simple text, HTML, XML or  
whatever you want:

> **[Blog Zenika](https://blog.zenika.com/?post%2F2012%2F12%2F20%2FIntroducing-the-ElasticSearch-View-Plugin)**
>
> \#CodeTheWorld

-- Tanguy  
@tlrx

Le mercredi 23 janvier 2013 12:18:27 UTC+1, Dominic Watson a écrit :

> Hi there, we have some legacy applications that are running on a platform  
> with appalling JSON deserialization performance. Does anyone know of any  
> plugins / options for returning alternative outputs, i.e. XML?
> 
> This is for _responses_ coming from the REST api.
> 
> Thanks in advance,
> 
> D

--

---

<div class="post-metadata">

**Author:** ![Dominic\_Watson\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dominic_watson_2/32/2517_2.png) [@Dominic\_Watson\_2](https://discuss.elastic.co/u/Dominic_Watson_2)\
**Post date:** [January 23, 2013, 11:55am UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470/3 "2013-01-23T11:55:49Z")

</div>

Hi Tanguy, thanks for the response.

I did find that but, from what I understand, this will only render  
documents and _pre-defined_ search queries. Is that not the case? What I  
would like is to have _all_ responses from ES be returned in some other  
format.

Dominic

On Wednesday, 23 January 2013 11:35:58 UTC, Tanguy wrote:

> Hi Dominic,
> 
> The following plugin can be found to return simple text, HTML, XML or  
> whatever you want:
> 
> [Blog Zenika – #CodeTheWorld](http://blog.zenika.com/index.php?post/2012/12/20/Introducing-the-ElasticSearch-View-Plugin)
> 
> -- Tanguy  
> @tlrx
> 
> Le mercredi 23 janvier 2013 12:18:27 UTC+1, Dominic Watson a écrit :
> 
> > Hi there, we have some legacy applications that are running on a platform  
> > with appalling JSON deserialization performance. Does anyone know of any  
> > plugins / options for returning alternative outputs, i.e. XML?
> > 
> > This is for _responses_ coming from the REST api.
> > 
> > Thanks in advance,
> > 
> > D

--

---

<div class="post-metadata">

**Author:** ![egaumer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/egaumer/32/2365_2.png) [@egaumer](https://discuss.elastic.co/u/egaumer)\
**Post date:** [January 23, 2013, 1:04pm UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470/4 "2013-01-23T13:04:56Z")

</div>

There's a plugin that mocks the Solr interfaces so you can use Solr based  
tools (Nutch, SolrJ, etc.) against elasticsearch. That plugin provides the  
Solr XML request/response formats.

> **[GitHub - mattweber/elasticsearch-mocksolrplugin: Use Solr clients/tools with...](https://github.com/mattweber/elasticsearch-mocksolrplugin)**
>
> Use Solr clients/tools with ElasticSearch. Contribute to mattweber/elasticsearch-mocksolrplugin development by creating an account on GitHub.

If that won't work, it wouldn't be terribly difficult to write a plugin  
that returns a custom response format.

On Wednesday, January 23, 2013 6:18:27 AM UTC-5, Dominic Watson wrote:

> Hi there, we have some legacy applications that are running on a platform  
> with appalling JSON deserialization performance. Does anyone know of any  
> plugins / options for returning alternative outputs, i.e. XML?
> 
> This is for _responses_ coming from the REST api.
> 
> Thanks in advance,
> 
> D

--

---

<div class="post-metadata">

**Author:** ![Dominic\_Watson\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dominic_watson_2/32/2517_2.png) [@Dominic\_Watson\_2](https://discuss.elastic.co/u/Dominic_Watson_2)\
**Post date:** [January 23, 2013, 2:09pm UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470/5 "2013-01-23T14:09:41Z")

</div>

Brilliant, thanks for that. I'll take a look.

On 23 January 2013 13:04, egaumer [egaumer@gmail.com](mailto:egaumer@gmail.com) wrote:

> There's a plugin that mocks the Solr interfaces so you can use Solr based  
> tools (Nutch, SolrJ, etc.) against elasticsearch. That plugin provides the  
> Solr XML request/response formats.
> 
> [GitHub - mattweber/elasticsearch-mocksolrplugin: Use Solr clients/tools with ElasticSearch](https://github.com/mattweber/elasticsearch-mocksolrplugin)
> 
> If that won't work, it wouldn't be terribly difficult to write a plugin  
> that returns a custom response format.
> 
> On Wednesday, January 23, 2013 6:18:27 AM UTC-5, Dominic Watson wrote:
> 
> > Hi there, we have some legacy applications that are running on a platform  
> > with appalling JSON deserialization performance. Does anyone know of any  
> > plugins / options for returning alternative outputs, i.e. XML?
> > 
> > This is for _responses_ coming from the REST api.
> > 
> > Thanks in advance,
> > 
> > D
> 
> --

--  
Pixl8 Interactive, 3 Tun Yard, Peardon Street, London  
SW8 3HT, United Kingdom

T: +44 [0] 845 260 0726• W: [www.pixl8.co.uk](http://www.pixl8.co.uk)• E: [info@pixl8.co.uk](mailto:info@pixl8.co.uk)  
Follow us on: Facebook [http://www.facebook.com/pixl8](http://www.facebook.com/pixl8)  
Twitter[http://www.twitter.com/pixl8](http://www.twitter.com/pixl8)  
LinkedIn [http://www.linkedin.com/pixl8](http://www.linkedin.com/pixl8)CONFIDENTIAL AND PRIVILEGED - This  
e-mail and any attachment is intended solely for the addressee, is strictly  
confidential and may also be subject to legal, professional or other  
privilege or may be protected by work product immunity or other legal  
rules. If you are not the addressee please do not read, print, re-transmit,  
store or act in reliance on it or any attachments. Instead, please email it  
back to the sender and then immediately permanently delete it. Pixl8  
Interactive Ltd Registered in England. Registered number: 04336501.  
Registered office: 8 Spur Road, Cosham, Portsmouth, Hampshire, PO6 3EB

--

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 24, 2013, 1:51pm UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470/6 "2013-01-24T13:51:24Z")

</div>

What language are you using?

I have Java code available to render XML, for example for XSL stylesheet  
transformations in a Java App server front-end. Please give me an info if  
you would like a release, it is using the XContent API.

Best regards,

Jörg

--

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:54am UTC](https://discuss.elastic.co/t/alternatives-to-json-output-xml/10470/7 "2017-07-06T02:54:46Z")

</div>


