beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Schoettger (JIRA)" <>
Subject [jira] Created: (BEEHIVE-1066) Method signature names may conflict with local variables in generated controls files
Date Mon, 13 Feb 2006 19:54:42 GMT
Method signature names may conflict with local variables in generated controls files

         Key: BEEHIVE-1066
     Project: Beehive
        Type: Bug
  Components: Controls  
    Versions: v1m1    
    Reporter: Chad Schoettger
 Assigned to: Chad Schoettger 

In the velocity templates used to generate controls, it is possible for there to be a name
conflict (which causes a compilation error) if a user created control method contains a parameter
with a name that happens to be the same as a local variable in the template.

For example, 

    * Implements services.UpgradeTypesServerControl.getSetXmlObject
    public org.apache.xmlbeans.XmlObject getSetXmlObject(org.apache.xmlbeans.XmlObject t)
        Object [] argArray = new Object[] { t };
        Throwable thrown = null;
        org.apache.beehive.controls.api.bean.Extensible target =
        org.apache.xmlbeans.XmlObject retval = null;
            preInvoke(_getSetXmlObjectMethod, argArray);
            retval =
            target.invoke(_getSetXmlObjectMethod, argArray)
        catch (Throwable t)
            // All exceptions are caught here, so postInvoke processing has visibility into
            // the exception status. Errors, RuntimExceptions, or declared checked exceptions
            // be rethrown.
            thrown = t;
            if (t instanceof Error) throw (Error)t;
            else if (t instanceof RuntimeException) throw (RuntimeException)t;
            throw new java.lang.reflect.UndeclaredThrowableException(t);
            Object rv = retval;
            postInvoke(_getSetXmlObjectMethod, argArray, rv, thrown);
        return retval;

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message