Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 8 Jul 2011 15:32:17 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1923567897.11485.1310139137155.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <251700407.11434.1310138296578.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-4198) Bindy Parser not handling Null
 values in KVP
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062017#comment-13062017 ] 

Claus Ibsen commented on CAMEL-4198:
------------------------------------

Do you want to attempt to provide a patch with a fix?

It seems you may have to check the length of the keyValuePair is > 1 to avoid the NPE.

And if possible an unit test would be really good as well.

> Bindy Parser not handling Null values in KVP
> --------------------------------------------
>
>                 Key: CAMEL-4198
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4198
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-bindy
>    Affects Versions: 2.7.1
>         Environment: developement 
>            Reporter: surya
>            Priority: Minor
>             Fix For: 2.9.0
>
>
> Camel Bindy is not handling null values in KVP. It throws ArrayIndexOutOfBounds Exception.
> From the source below if FIX message has a key value pair with null value i.e (eg: 43=1|63=|64=xyz) the key 63 has no value an while parsing it throws exception for keyValuePair[1].
>            // Get KeyValuePair
>             String[] keyValuePair = s.split(getKeyValuePairSeparator());
>             // Extract Key
>             int key = Integer.parseInt(keyValuePair[0]);
>             // Extract key value
>             String value = keyValuePair[1];

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira