On Mon, 06 Jun 2005 20:17:38 +0200, Shinobu Kawai
<[EMAIL PROTECTED]> wrote:
Hi max,
Any particular reason why velocity only do Class.forName() where
it should first look in thread context classloader and THEN do
Class.forName() ?
(it gives some issues when running in environments with changing
classloaders, like
J2EE and Eclipse)
Are we talking about the ClasspathResourceLoader? Then it's fixed in
the latest repository.
http://issues.apache.org/bugzilla/show_bug.cgi?id=22419
For the latest in the repository:
http://cvs.apache.org/snapshots/velocity/
I'm talking about
FieldMethodizer
RuntimeInstance
LogManager
ResourceManagerImpl
ResourceLoaderFactory
Generator
While on the subject of things that "messes" up J2EE/Eclipse environments.
Why is so much stuff logged as WARN/ERROR in Velocity ?
Like:
"ERROR: ResourceManager : unable to find resource 'VM_global_library.vm'
in any resource loader."
That should at least only be a WARN and it should be in a ResourceManager
category so you could disable it.
And:
"Warning! The iterative is an Iterator in the #foreach() loop at [0,0] in
template pojo/javaclass.vm. Because it's not resetable, if used in more
than once, this may lead to unexpected results."
Again, I undestand why this is there - but it should only be done on
objects that is directly in the context (if at all). Printing out this
warning
for every iterator is simply not very usefull... e.g. printing this
warning for a methodcall that does someList.iterator() is just noise.
I removed this last one by providing my own UberSpectImpl, but it should
not be necessary IMO.
/max
Best regards,
-- Shinobu
--
Shinobu Kawai <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
