You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org> on 2007/03/08 01:04:33 UTC

[jira] Closed: (VELOCITY-159) Not possible to get Velocity to log stack traces.

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

Henning Schmiedehausen closed VELOCITY-159.
-------------------------------------------


> Not possible to get Velocity to log stack traces.
> -------------------------------------------------
>
>                 Key: VELOCITY-159
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-159
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 1.4
>         Environment: Operating System: All
> Platform: All
>            Reporter: Victor Wiewiorowski
>            Priority: Minor
>             Fix For: 1.5
>
>
> I am trying to get velocity to log stack traces, 
> However setting the VelocityEngine.RUNTIME_LOG_ERROR_STACKTRACE does
> not cause the stack traces to be printed, because 
> RuntimeInstance.showStackTrace() first checks configuration.isInitialized(),
> which always seems to return false. :(
> Is there a problem with ExtendedProperties? Looking at the 2.1
> ExtendedProperties source the isInitialized flag is never set, 
> unless I am missing something.

-- 
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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org