Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A6F04EFCF for ; Fri, 1 Feb 2013 12:04:16 +0000 (UTC) Received: (qmail 24573 invoked by uid 500); 1 Feb 2013 12:04:14 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 23452 invoked by uid 500); 1 Feb 2013 12:04:13 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 23323 invoked by uid 99); 1 Feb 2013 12:04:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2013 12:04:13 +0000 Date: Fri, 1 Feb 2013 12:04:13 +0000 (UTC) From: "Philippe Le Berre (JIRA)" To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AXIS2-5482) getOMElement fails to properly set the counts on null/nil items MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIS2-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philippe Le Berre updated AXIS2-5482: ------------------------------------- Description: When there is a series of null/nil arguments in a call, getOMElement fails to increase the item count when it should leading to an "invalid value ... for " Fault on the server side. The fix is pretty simple : add ++argCount before the continue int the arg == null test in getOMElement (see patch). Example without the patch, the 4 item 1 are in fact 4 different arguments ! -- false false reference desc 1 -- With the fix, it's all clean :-) false 34 false origin asc 1 Patch is attached --- BeanUtil.java.orig 2013-02-01 13:01:30.000000000 +0100 +++ BeanUtil.java 2013-02-01 13:01:50.000000000 +0100 @@ -838,6 +838,7 @@ objects.add(partName); } objects.add(arg); + ++argCount; continue; } was: When there is a series of null/nil arguments in a call, getOMElement fails to increase the item count when it should leading to an "invalid value ... for " Fault on the server side. The fix is pretty simple : add ++argCount before the continue int the arg == null test in getOMElement (see patch). Example without the patch, the 4 item 1 are in fact 4 different arguments ! -- false false reference desc 1 -- With the fix, it's all clean :-) false 34 false origin asc 1 Patched is attached --- BeanUtil.java.orig 2013-02-01 13:01:30.000000000 +0100 +++ BeanUtil.java 2013-02-01 13:01:50.000000000 +0100 @@ -838,6 +838,7 @@ objects.add(partName); } objects.add(arg); + ++argCount; continue; } > getOMElement fails to properly set the counts on null/nil items > --------------------------------------------------------------- > > Key: AXIS2-5482 > URL: https://issues.apache.org/jira/browse/AXIS2-5482 > Project: Axis2 > Issue Type: Bug > Components: adb > Affects Versions: 1.6.2 > Reporter: Philippe Le Berre > Priority: Blocker > Labels: patch > Attachments: patch2.diff > > > When there is a series of null/nil arguments in a call, getOMElement fails to increase the item count when it should leading to an "invalid value ... for " Fault on the server side. > The fix is pretty simple : add ++argCount before the continue int the arg == null test in getOMElement (see patch). > Example without the patch, the 4 item 1 are in fact 4 different arguments ! > -- > > false > > > > > false > reference > desc > 1 > -- > With the fix, it's all clean :-) > > false > 34 > > > > false > origin > asc > 1 > > Patch is attached > --- BeanUtil.java.orig 2013-02-01 13:01:30.000000000 +0100 > +++ BeanUtil.java 2013-02-01 13:01:50.000000000 +0100 > @@ -838,6 +838,7 @@ > objects.add(partName); > } > objects.add(arg); > + ++argCount; > continue; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org