DO NOT REPLY [Bug 10998] New: - Backwards compatability lost on templates with 1.3

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10998>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10998

Backwards compatability lost on templates with 1.3

           Summary: Backwards compatability lost on templates with 1.3
           Product: Velocity
           Version: 1.3-rc1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Source
        AssignedTo: velocity-dev@jakarta.apache.org
        ReportedBy: stu@cuyahoga.co.uk


With the latest 1.3 download, some templates are failing (with 
ReferenceExceptions) that were working perfectly under 1.2, an example of which 
follows. 

I have a method in a utility class which is placed onto the context;

  public static String createMethodLine(String visibility, String methodName, 
List params, Map colData, String returnType, boolean throwsSQLException, 
boolean retrieveByParams);


In the template, I have the following;

  $TGUtils.createMethodLine("public", "retrieve", $index.getIndexColumns(), 
$tableData.get($tableName).getColumnData(), "boolean", false, true)

where $index.getIndexColumns() is a java.util.ArrayList and $tableData.get
($tableName).getColumnData() is a java.util.TreeMap.

Works under 1.2 but throws ReferenceExceptions under 1.3 :(

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>