This rings a bell - but I can't remember why... I know it was on the
turbine list, so you also might look there.
Velocity per se doesn't give a hoot about the size of a template.
Can you use a nightly build of Velocity and see what happens? It won't
solve anything (as I don't recall this being a vel issue) but I recently
changed the log message for a MIE to give more useful output.
Also, what version of torque?
geir
Ken Helmes wrote:
>
> Velocity version: 1.1
>
> When parsing Velocity db control templates in torque the following exception
> is thrown:
>
> C:\VC\Core30\build\torque\torque.xml:193: Exception thrown by
> 'generator.parse'.
> For more information consult the velocity log.
> --- Nested Exception ---
> org.apache.velocity.exception.MethodInvocationException: Invocation of
> method '
> parse' in class org.apache.velocity.texen.Generator threw exception class
> org.apache.velocity.exception.MethodInvocationException
> at org.apache.velocity.runtime.parser.node.ASTMethod.
> execute(ASTMethod.java:307)
> at org.apache.velocity.runtime.parser.node.ASTReference.
> execute(ASTReference.java:197)
> ...
>
> Velocity log:
> Thu Jul 26 18:01:26 EEST 2001 [info] ResourceManager :
> found ./sql/base/solid/columns.vm with loader org.apache.velocity.runtime.
> resource.loader.FileResourceLoader
> Thu Jul 26 18:01:26 EEST 2001 [error] Method get threw exception for
> reference
> $dbprops in template ./sql/base/solid/columns.vm at [2,20]
>
> When the size of the torque project-schema.xml or the .vm db control files
> are
> decreased, the parsing proceeds farther - or even succeeds depending on how
> much
> is removed, suggesting that there is a size limitation somewhere in the
> template
> parser ie. the problem does not seem to be in the db.props file as the above
> log suggests.
>
> Is this a known problem?
>
> /Ken
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
Be well, do good work, and keep in touch.
