Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Message-ID: <11792058.202161292758984060.JavaMail.jira@thor>
Date: Sun, 19 Dec 2010 06:43:04 -0500 (EST)
From: "Samisa Abeysinghe (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Subject: [jira] Updated: (AXIS2-4570) Remove optimizeContent objects and
 arguments from ADB-generated stubs?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samisa Abeysinghe updated AXIS2-4570:
-------------------------------------

    Fix Version/s:     (was: 1.5.1)
                   1.6

> Remove optimizeContent objects and arguments from ADB-generated stubs?
> ----------------------------------------------------------------------
>
>                 Key: AXIS2-4570
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4570
>             Project: Axis2
>          Issue Type: Improvement
>          Components: adb
>    Affects Versions: 1.5.1
>            Reporter: Glen Mazza
>            Priority: Minor
>             Fix For: 1.6
>
>
> Axis2 1.4.1 and 1.5.1 (and probably all older versions) are providing an opNameArray object and optimizeContent method that serve no purpose within the ADB-generated stubs:
>     private javax.xml.namespace.QName[] opNameArray = null;
>     private boolean optimizeContent(javax.xml.namespace.QName opName) {  // *always* returns false
>         if (opNameArray == null) {
>             return false;
>         }
>         for (int i = 0; i < opNameArray.length; i++) {
>             if (opName.equals(opNameArray[i])) {
>                 return true;   
>             }
>         }
>         return false;
>     }
> Also, the toOM() and toEnvelope() methods generated in the stubs take an optimizeContent argument that both method implementations ignore.  Further, all callers to those methods just call the above optimizeContent() method, which invariably returns false.
> These methods are adding unnecessarily to processing overhead and make the generated code more confusing.  To simplify things it would be good if you could remove the optimizeContent() method above, the opNameArray object, and the optimizeContent boolean arguments from the generated toOM() and toEnvelope() methods.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org