Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Tue, 14 Aug 2012 12:43:53 -0700 (PDT)
From: ychawla <premiergeneration@yahoo.com>
To: users@camel.apache.org
Message-ID: <1344973433733-5717347.post@n5.nabble.com>
In-Reply-To: <1344968822385-5717341.post@n5.nabble.com>
References: <1344968822385-5717341.post@n5.nabble.com>
Subject: Re: JSON - Jackson return list rather than POJO
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

A simple workaround for this is a custom bean processor like so:

	public void processPersonSearchResponseJSON(Exchange exchange) throws
JsonParseException, JsonMappingException, IOException
	{
		ObjectMapper mapper = new ObjectMapper();
		 
		List<PersonSearchResponse> personSearchResponses =
mapper.readValue(exchange.getIn().getBody(String.class), new
TypeReference<List&lt;PersonSearchResponse>>() { });
		  
		exchange.getIn().setBody(personSearchResponses);

	}

and in the camel context:

<camel:to uri="JSONEndpoint"/>
			
<camel:convertBodyTo type="java.lang.String"/>
			
<camel:log message="This is the JSON Response: ${body}" />
			
<camel:to
uri="bean:personSearchResponseJSONProcessor?method=processPersonSearchResponseJSON"/>


--
View this message in context: http://camel.465427.n5.nabble.com/JSON-Jackson-return-list-rather-than-POJO-tp5717341p5717347.html
Sent from the Camel - Users mailing list archive at Nabble.com.