velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Khamkar <rkham...@gmail.com>
Subject Re: Using Velocity tools with Velocity Engine
Date Mon, 28 Jun 2010 17:20:41 GMT
Yes, you are correct. It is the class not found exception. The module
that I used to fire my instance never had a reference of the velocity
tools jar - build however did, no never realized that was the case.
Thanks for pointing me in the correct direction.


On Mon, Jun 28, 2010 at 10:16 AM, Nathan Bubna <nbubna@gmail.com> wrote:
> On Mon, Jun 28, 2010 at 9:56 AM, Rohit Khamkar <rkhamkar@gmail.com> wrote:
>> Different from the standard out i meant. So in case there were any
>> exception, I should see them in the logs.
>
> standard out is the final fallback.  it will try to use log4j,
> commons-log, or jdk15 logging before resorting to that.
>
>> Well my environment is WebSphere app server, with java 1.5
>>
>> I am using Velocity engine and trying to use Velocity Tools in
>> standalone fashion. Not sure what else you need to know for velocity
>> in a standalone environment.
>
> i've never used websphere, but are you sure that VelocityTools is
> present in the classpath?  i'm pretty much certain that the only way
> "new NumberTool()" could halt code execution is a
> ClassNotFoundException.
>
>
>> On Mon, Jun 28, 2010 at 9:28 AM, Nathan Bubna <nbubna@gmail.com> wrote:
>>> On Mon, Jun 28, 2010 at 8:39 AM, Antonio Petrelli
>>> <antonio.petrelli@gmail.com> wrote:
>>>> 2010/6/28 Rohit Khamkar <rkhamkar@gmail.com>:
>>>>> Not even a single line of stacktrace. Does Velocity log under a
>>>>> different file?
>>>
>>> different file from what?
>>>
>>>> I don't think so.
>>>>
>>>>> I would hope to see anything under such case written
>>>>> to standard error. Is there a different approach in doing this?
>>>>
>>>> Well, I must admit that Velocity Tools (probably Velocity too) have a
>>>> bad habit in ignoring or swallowing exceptions. At this point your
>>>> only way to discover your problem is by debugging.
>>>
>>> sorry, but the NumberTool and ToolManager constructors do not catch
>>> any exceptions.  heck, the NumberTool class has no explicit
>>> constructor, just the default one.  and if they did catch exceptions,
>>> the code would continue running rather than stop.  you're gonna have
>>> to tell us about your environment, because you have something funky.
>>> if i had to guess, i would bet that your setup is swallowing
>>> ClassNotFoundExceptions.  this looks for all the world like
>>> VelocityTools is not in the classpath at runtime and you are somehow
>>> not seeing the CNFEs.
>>>
>>>
>>>> Antonio
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
>>>> For additional commands, e-mail: user-help@velocity.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
>>> For additional commands, e-mail: user-help@velocity.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: user-help@velocity.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Mime
View raw message