<?xml version="1.0" encoding="utf-8"?>

<feed xmlns="http://www.w3.org/2005/Atom">

<title><![CDATA[Jon's Blog]]></title>

<link href="http://JonCook.github.com/atom.xml" rel="self"/>

<link href="http://JonCook.github.com/"/>

<updated>2014-01-13T23:36:36+01:00</updated>

<id>http://JonCook.github.com/</id>

<author>

<name><![CDATA[Jon Cook]]></name>

</author>

<generator uri="http://octopress.org/">Octopress</generator>

<entry>

<title type="html"><![CDATA[XML Processing with Scala]]></title>

<link href="http://JonCook.github.com/blog/2013/11/03/xml-processing-with-scala/"/>

<updated>2013-11-03T08:33:00+01:00</updated>

<id>http://JonCook.github.com/blog/2013/11/03/xml-processing-with-scala</id>

<content type="html"><![CDATA[<p>Given scala&rsquo;s built-in support for XML and its more concise syntax for dealing with iterables and collections I was interested to see what some of our java xml parsing code written using Dom4j could look like in the Scala world.</p>

]]></content>

</entry>

<entry>

<title type="html"><![CDATA[Some Bash Fu with Curl, Grep, Awk and Pipes]]></title>

<link href="http://JonCook.github.com/blog/2012/04/30/some-bash-fu-with-curl/"/>

<updated>2012-04-30T01:15:00+02:00</updated>

<id>http://JonCook.github.com/blog/2012/04/30/some-bash-fu-with-curl</id>

<content type="html"><![CDATA[<p>I wanted to test out the HTTP response codes from a number of our API endpoints. There is numerous ways to approach this but I thought it would be fun to use the command line and it turned out pretty straight forward.</p>

]]></content>

</entry>

<entry>

<title type="html"><![CDATA[Creating a HTTP Response Version Provider with Apache CXF Filters]]></title>

<link href="http://JonCook.github.com/blog/2012/04/07/creating-a-http-response-version-provider-with-apache-cxf-filters/"/>

<updated>2012-04-07T22:16:00+02:00</updated>

<id>http://JonCook.github.com/blog/2012/04/07/creating-a-http-response-version-provider-with-apache-cxf-filters</id>

<content type="html"><![CDATA[<p>I&rsquo;ve been using <a href="http://cxf.apache.org/">Apache CXF</a> which has some nice support for building JSR-311 compliant JAX-RS Services and recently had a requirement for sending back a custom version header as part of our API Responses.</p>

]]></content>

</entry>

<entry>

<title type="html"><![CDATA[Useful XQuery]]></title>

<link href="http://JonCook.github.com/blog/2012/03/15/useful-xquery/"/>

<updated>2012-03-15T13:58:00+01:00</updated>

<id>http://JonCook.github.com/blog/2012/03/15/useful-xquery</id>

<content type="html"><![CDATA[<p>As I mentioned in my previous <a href="http://joncook.github.com/blog/2012/02/12/evaluating-mark-logic-xquery-performance/">blog post</a> I&rsquo;ve recently been doing some work building RESTFul API&rsquo;s backed by a Mark Logic XML Content Store utilising XQuery for document retrieval which has led me come up with the following useful snippets of XQuery that I thought I would share. They could easily be altered to work with slightly different requirements.</p>

]]></content>

</entry>

<entry>

<title type="html"><![CDATA[Evaluating Mark Logic XQuery Performance]]></title>

<link href="http://JonCook.github.com/blog/2012/02/12/evaluating-mark-logic-xquery-performance/"/>

<updated>2012-02-12T19:36:00+01:00</updated>

<id>http://JonCook.github.com/blog/2012/02/12/evaluating-mark-logic-xquery-performance</id>

<content type="html"><![CDATA[<p>I&rsquo;ve recently been doing some work building RESTFul API&rsquo;s backed by a Mark Logic XML Content Store utilising XQuery for document retrieval. This post details the steps involved in tuning what was deemed to be the most simplest of queries for optimum performance using some useful Mark Logic extensions for profiling.</p>

]]></content>

</entry>

</feed>