You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Nathan Bubna <na...@esha.com> on 2003/01/24 20:02:47 UTC
Re: [veltools] struts 1.1
Richard said:
> I coded the ActionMessage support for Struts 1.1, but i dont know if i
have
> to do it for the generation of javascript in the stuts 1.1 validator
support
> ? I guess the future release is planned with the release of the struts 1.1
> final ...
This is a subject I've been meaning to bring up at some point. I do hope to
add (uncommented) support for struts 1.1 to the vel-struts library. At this
point, I too have modified my local copy to support 1.1 and no longer use
Struts 1.0. I've been watching struts-dev and it looks like a final release
may very well happen soon (maybe next month).
It would be good to get a feel for what Velocity-Struts users are
doing/wanting. Is it important for people to continue being able to
build/use vel-struts with Struts 1.0? Or would people be ok with moving
right ahead to 1.1?
Nathan Bubna
nathan@esha.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [veltools] struts 1.1
Posted by Nathan Bubna <na...@esha.com>.
Tim said:
...
> > ah, yes, releases... some people like those, don't they? :)
> Indeed. I just like the symmetry of version numbers 1.0/1.0 and 1.1/1.1
> ...heck, maybe we should quickly release Veltools 1.0 and then in quick
> succession do 1.1b-1, 1.1b-2, 1.1-b3.
heh. and monkeys might... eh, nevermind. :)
> > anyway, this sounds reasonable. maybe we should get a thread
> > going on the dev list about release(s)/features/fixes/roadmap stuff.
> Ha. Sure. (Didn't you try that a few months ago?)
yeah, but i'm a slow learner. besides, this time i have some power to do
something about those things.
...
> > i think we do have a working lib for it, right? i haven't
> > been made aware of any bugs at least. but i presume you want
> > some sort of tagged/built/maintained/whatever branch, right?
> Oh, I'm using the Veltools 0.whatever_is_in_CVS version right now and it
> works without any major issues for me. :-)
good, but feel free to post notice of minor issues too.
> But an 'official' 1.0 release would prolly make other folks more warm
> and fuzzy toward the code.
it's true. and it also tends to generate
visibility/publicity/sense-of-value for a project.
Nathan Bubna
nathan@esha.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [veltools] struts 1.1
Posted by Tim Colson <tc...@cisco.com>.
> ah, yes, releases... some people like those, don't they? :)
Indeed. I just like the symmetry of version numbers 1.0/1.0 and 1.1/1.1
...heck, maybe we should quickly release Veltools 1.0 and then in quick
succession do 1.1b-1, 1.1b-2, 1.1-b3.
> anyway, this sounds reasonable. maybe we should get a thread
> going on the dev list about release(s)/features/fixes/roadmap stuff.
Ha. Sure. (Didn't you try that a few months ago?)
> release dates are only set after the fact
> around here. :)
:-)
> i think we do have a working lib for it, right? i haven't
> been made aware of any bugs at least. but i presume you want
> some sort of tagged/built/maintained/whatever branch, right?
Oh, I'm using the Veltools 0.whatever_is_in_CVS version right now and it
works without any major issues for me. :-)
But an 'official' 1.0 release would prolly make other folks more warm
and fuzzy toward the code.
Tim
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Velocity in WAS 3.5 not loading default properties
Posted by Kevin Baynes <kb...@seagullsw.com>.
Note:
I started this thread about Velocity in WebSphere 3.5 on OS/390, and am
finishing it for public record. My hope is that it will help another
deveoper in a similar situation. See my other emails for details of errors:
ResourceManager, etc.
--------------------
I was having trouble getting Velocity to run in WebSphere 3.5, and kept
finding that I needed to set additional properties to pass to
VelocityEngine.init(Properties p).
I eventually copied the velocity.properties from the /runtime/defaults/ src
folder into my application and then loaded it myself :
Properties p = new Properties();
p.load(new FileInputStream(propertiesFile));
p.setProperty(....); // my overrides
ve.init(p);
In WAS 3.5 on OS/390, Velocity cannot load the default properties
(RuntimeInstance.setDefaultProperties() fails). The developer must load them
explicitly. The examples in the developer's guide about using Velocity in
applications assume that Velocity can load the default properties... this
assumption is often correct, but not in WAS 3.5.
~akb
-----Original Message-----
From: Kevin Baynes [mailto:kbaynes@seagullsw.com]
Sent: Tuesday, January 28, 2003 9:39 AM
To: Velocity Users List
Subject: ResourceManager.getResource() Exception
The below email details how I added logging and specified ResourceManager
classes.
This worked on WinXP && Tomcat4 && JDK 1.3.0.
However, on OS/390 2.1.0 && WAS 3.5.0 && JDK 1.3.1, I'm geting the below
error.
I'm using velocity-1.3.jar and commons-collection.jar 1.0.
I am pretty much stumped as to the cause or how to address this one. The
JDK's are _almost_ identical, and both platforms are using the same
velocity/commons jars.
~akb
ERROR :
2003-01-28 08:10:36,750 ERROR: ResourceManager.getResource() exception
new: java.util.NoSuchElementException:
'directive.foreach.counter.initial.value' doesn't map to an existing
object
2003-01-28 08:10:36,763 FATAL: Administrator.doGet() Exception in
doAction
java.util.NoSuchElementException:
'directive.foreach.counter.initial.value' doesn't map to an existing
object
at
org.apache.commons.collections.ExtendedProperties.getInteger(ExtendedPropert
ies.java(Inlined
Compiled Code))
at
org.apache.commons.collections.ExtendedProperties.getInt(ExtendedProperties.
java(Compiled
Code))
at
org.apache.velocity.runtime.RuntimeInstance.getInt(RuntimeInstance.java(Inli
ned
Compiled Code))
at
org.apache.velocity.runtime.directive.Foreach.init(Foreach.java(Inlined
Compiled Code))
at
org.apache.velocity.runtime.parser.node.ASTDirective.init(ASTDirective.java(
Inlined
Compiled Code))
at
org.apache.velocity.runtime.parser.node.SimpleNode.init(SimpleNode.java(Inli
ned
Compiled Code))
at org.apache.velocity.Template.initDocument(Template.java(Inlined
Compiled Code))
at org.apache.velocity.Template.process(Template.java(Inlined Compiled
Code))
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(Resour
ceManagerImpl.java(Inlined
Compiled Code))
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(Resourc
eManagerImpl.java(Inlined
Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java
(Inlined
Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java
(Inlined
Compiled Code))
at
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java(Inlin
ed
Compiled Code))
at com.seagullsw.swm.Administrator.doGet(Administrator.java(Compiled
Code))
-----Original Message-----
From: Kevin Baynes [mailto:kbaynes@seagullsw.com]
Sent: Tuesday, January 28, 2003 8:28 AM
To: Velocity Users List
Subject: RE: ResourceManager not found exception
Update:
Adding my logger in properties caused ResourceManager error, which caused me
to have to explicitly name the ResourceManager class and the ResourceCache
class. Is this by design?
~akb
I began with these properties and all worked well :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
ve.init(p);
I added the next two properties and got the ResourceManager error below
(logging to my log worked) :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
ve.init(p);
I then added the final two properties and everything started working :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
p.setProperty("resource.manager.class","org.apache.velocity.runtime.resource
.ResourceManagerImpl");
p.setProperty("resource.manager.cache.class","org.apache.velocity.runtime.re
source.ResourceCacheImpl");
ve.init(p);
-----Original Message-----
From: Kevin Baynes [mailto:kbaynes@seagullsw.com]
Sent: Monday, January 27, 2003 5:18 PM
To: Velocity Users List
Subject: ResourceManager not found exception
I'm getting the below error from Velocity.
I believe that my configuration was working fine until I added log4j as the
logger in my properties.
I think the below properties look right... am I missing something?
~akb
PROPERTIES :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
ve.init(p);
ERROR :
2003-01-27 14:21:15,655 DEBUG: Administrator.init() VelocityEngine.Init()
Begin
2003-01-27 14:21:15,722 DEBUG: SimpleLog4JLogSystem using category
'com.seagullsw.swm.Administrator'
2003-01-27 14:21:15,722 INFO :
**************************************************************
2003-01-27 14:21:15,722 INFO : Starting Jakarta Velocity v1.3
2003-01-27 14:21:15,722 INFO : RuntimeInstance initializing.
2003-01-27 14:21:15,722 INFO : Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
2003-01-27 14:21:15,723 INFO : Trying to use logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 INFO : Using logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 ERROR: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
2003-01-27 14:21:15,749 FATAL: Fatal Exception in Administrtor constructor
java.lang.Exception: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
at
org.apache.velocity.runtime.RuntimeInstance.initializeResourceManager(Runtim
eInstance.java(Inlined Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java(Inlined
Compiled Code))
at com.seagullsw.swm.Administrator.init(Administrator.java(Compiled Code))
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org
ResourceManager.getResource() Exception
Posted by Kevin Baynes <kb...@seagullsw.com>.
The below email details how I added logging and specified ResourceManager
classes.
This worked on WinXP && Tomcat4 && JDK 1.3.0.
However, on OS/390 2.1.0 && WAS 3.5.0 && JDK 1.3.1, I'm geting the below
error.
I'm using velocity-1.3.jar and commons-collection.jar 1.0.
I am pretty much stumped as to the cause or how to address this one. The
JDK's are _almost_ identical, and both platforms are using the same
velocity/commons jars.
~akb
ERROR :
2003-01-28 08:10:36,750 ERROR: ResourceManager.getResource() exception
new: java.util.NoSuchElementException:
'directive.foreach.counter.initial.value' doesn't map to an existing
object
2003-01-28 08:10:36,763 FATAL: Administrator.doGet() Exception in
doAction
java.util.NoSuchElementException:
'directive.foreach.counter.initial.value' doesn't map to an existing
object
at
org.apache.commons.collections.ExtendedProperties.getInteger(ExtendedPropert
ies.java(Inlined
Compiled Code))
at
org.apache.commons.collections.ExtendedProperties.getInt(ExtendedProperties.
java(Compiled
Code))
at
org.apache.velocity.runtime.RuntimeInstance.getInt(RuntimeInstance.java(Inli
ned
Compiled Code))
at
org.apache.velocity.runtime.directive.Foreach.init(Foreach.java(Inlined
Compiled Code))
at
org.apache.velocity.runtime.parser.node.ASTDirective.init(ASTDirective.java(
Inlined
Compiled Code))
at
org.apache.velocity.runtime.parser.node.SimpleNode.init(SimpleNode.java(Inli
ned
Compiled Code))
at org.apache.velocity.Template.initDocument(Template.java(Inlined
Compiled Code))
at org.apache.velocity.Template.process(Template.java(Inlined Compiled
Code))
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(Resour
ceManagerImpl.java(Inlined
Compiled Code))
at
org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(Resourc
eManagerImpl.java(Inlined
Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java
(Inlined
Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java
(Inlined
Compiled Code))
at
org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java(Inlin
ed
Compiled Code))
at com.seagullsw.swm.Administrator.doGet(Administrator.java(Compiled
Code))
-----Original Message-----
From: Kevin Baynes [mailto:kbaynes@seagullsw.com]
Sent: Tuesday, January 28, 2003 8:28 AM
To: Velocity Users List
Subject: RE: ResourceManager not found exception
Update:
Adding my logger in properties caused ResourceManager error, which caused me
to have to explicitly name the ResourceManager class and the ResourceCache
class. Is this by design?
~akb
I began with these properties and all worked well :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
ve.init(p);
I added the next two properties and got the ResourceManager error below
(logging to my log worked) :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
ve.init(p);
I then added the final two properties and everything started working :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
p.setProperty("resource.manager.class","org.apache.velocity.runtime.resource
.ResourceManagerImpl");
p.setProperty("resource.manager.cache.class","org.apache.velocity.runtime.re
source.ResourceCacheImpl");
ve.init(p);
-----Original Message-----
From: Kevin Baynes [mailto:kbaynes@seagullsw.com]
Sent: Monday, January 27, 2003 5:18 PM
To: Velocity Users List
Subject: ResourceManager not found exception
I'm getting the below error from Velocity.
I believe that my configuration was working fine until I added log4j as the
logger in my properties.
I think the below properties look right... am I missing something?
~akb
PROPERTIES :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
ve.init(p);
ERROR :
2003-01-27 14:21:15,655 DEBUG: Administrator.init() VelocityEngine.Init()
Begin
2003-01-27 14:21:15,722 DEBUG: SimpleLog4JLogSystem using category
'com.seagullsw.swm.Administrator'
2003-01-27 14:21:15,722 INFO :
**************************************************************
2003-01-27 14:21:15,722 INFO : Starting Jakarta Velocity v1.3
2003-01-27 14:21:15,722 INFO : RuntimeInstance initializing.
2003-01-27 14:21:15,722 INFO : Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
2003-01-27 14:21:15,723 INFO : Trying to use logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 INFO : Using logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 ERROR: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
2003-01-27 14:21:15,749 FATAL: Fatal Exception in Administrtor constructor
java.lang.Exception: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
at
org.apache.velocity.runtime.RuntimeInstance.initializeResourceManager(Runtim
eInstance.java(Inlined Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java(Inlined
Compiled Code))
at com.seagullsw.swm.Administrator.init(Administrator.java(Compiled Code))
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: ResourceManager not found exception
Posted by Kevin Baynes <kb...@seagullsw.com>.
Update:
Adding my logger in properties caused ResourceManager error, which caused me
to have to explicitly name the ResourceManager class and the ResourceCache
class. Is this by design?
~akb
I began with these properties and all worked well :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
ve.init(p);
I added the next two properties and got the ResourceManager error below
(logging to my log worked) :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
ve.init(p);
I then added the final two properties and everything started working :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
p.setProperty("resource.manager.class","org.apache.velocity.runtime.resource
.ResourceManagerImpl");
p.setProperty("resource.manager.cache.class","org.apache.velocity.runtime.re
source.ResourceCacheImpl");
ve.init(p);
-----Original Message-----
From: Kevin Baynes [mailto:kbaynes@seagullsw.com]
Sent: Monday, January 27, 2003 5:18 PM
To: Velocity Users List
Subject: ResourceManager not found exception
I'm getting the below error from Velocity.
I believe that my configuration was working fine until I added log4j as the
logger in my properties.
I think the below properties look right... am I missing something?
~akb
PROPERTIES :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
ve.init(p);
ERROR :
2003-01-27 14:21:15,655 DEBUG: Administrator.init() VelocityEngine.Init()
Begin
2003-01-27 14:21:15,722 DEBUG: SimpleLog4JLogSystem using category
'com.seagullsw.swm.Administrator'
2003-01-27 14:21:15,722 INFO :
**************************************************************
2003-01-27 14:21:15,722 INFO : Starting Jakarta Velocity v1.3
2003-01-27 14:21:15,722 INFO : RuntimeInstance initializing.
2003-01-27 14:21:15,722 INFO : Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
2003-01-27 14:21:15,723 INFO : Trying to use logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 INFO : Using logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 ERROR: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
2003-01-27 14:21:15,749 FATAL: Fatal Exception in Administrtor constructor
java.lang.Exception: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
at
org.apache.velocity.runtime.RuntimeInstance.initializeResourceManager(Runtim
eInstance.java(Inlined Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java(Inlined
Compiled Code))
at com.seagullsw.swm.Administrator.init(Administrator.java(Compiled Code))
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
ResourceManager not found exception
Posted by Kevin Baynes <kb...@seagullsw.com>.
I'm getting the below error from Velocity.
I believe that my configuration was working fine until I added log4j as the
logger in my properties.
I think the below properties look right... am I missing something?
~akb
PROPERTIES :
p.setProperty("resource.loader","file");
p.setProperty("file.resource.loader.class","org.apache.velocity.runtime.reso
urce.loader.FileResourceLoader");
p.setProperty("file.resource.loader.path",vmFolder.getPath());
p.setProperty("file.resource.loader.cache","true");
p.setProperty("file.resource.loader.modificationCheckInterval","0");
p.setProperty("runtime.log.logsystem.class","org.apache.velocity.runtime.log
.SimpleLog4JLogSystem");
p.setProperty("runtime.log.logsystem.log4j.category","com.seagullsw.swm.Admi
nistrator");
ve.init(p);
ERROR :
2003-01-27 14:21:15,655 DEBUG: Administrator.init() VelocityEngine.Init()
Begin
2003-01-27 14:21:15,722 DEBUG: SimpleLog4JLogSystem using category
'com.seagullsw.swm.Administrator'
2003-01-27 14:21:15,722 INFO :
**************************************************************
2003-01-27 14:21:15,722 INFO : Starting Jakarta Velocity v1.3
2003-01-27 14:21:15,722 INFO : RuntimeInstance initializing.
2003-01-27 14:21:15,722 INFO : Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
2003-01-27 14:21:15,723 INFO : Trying to use logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 INFO : Using logger class
org.apache.velocity.runtime.log.SimpleLog4JLogSystem
2003-01-27 14:21:15,723 ERROR: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
2003-01-27 14:21:15,749 FATAL: Fatal Exception in Administrtor constructor
java.lang.Exception: It appears that no class was specified as the
ResourceManager. Please ensure that all configuration information is
correct.
at
org.apache.velocity.runtime.RuntimeInstance.initializeResourceManager(Runtim
eInstance.java(Inlined Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java(Inlined
Compiled Code))
at com.seagullsw.swm.Administrator.init(Administrator.java(Compiled Code))
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Velocity in WAS 3.5.0 on OS/390
Posted by Kevin Baynes <kb...@seagullsw.com>.
I'm running Velocity 1.3 in Websphere 3.5.0 on OS/390 inside a Web
application and am receiving the below exception on initialization.
WAS 3.5.0 is not J2EE compliant and it unpacks WAR files into it's own
directory structure, which does not follow the SUN spec. For example, it
creates a WEB-INF directory but not a classes or lib directory under it.
I've been correcting path issues and have a suspicion that this error is
also a path issue. Any ideas are much appreciated. Looking at the LogManager
source, I can't see what could be null to generate NPE in the
createLogSystem() method.
Thanks,
Kevin
Error Message:
2003-01-27 11:01:02,897 FATAL: Fatal Exception in Administrtor constructor
java.lang.NullPointerException
at
org.apache.velocity.runtime.log.LogManager.createLogSystem(LogManager.java(I
nlined Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.initializeLogger(RuntimeInstance
.java(Inlined Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java(Inline
d Compiled Code))
at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java(Inlined
Compiled Code))
at com.seagullsw.swm.Administrator.init(Administrator.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletManager.ja
va(Inlined Compiled Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(StrictLifecycleSe
rvlet.java(Inlined Compiled Code))
at
com.ibm.servlet.engine.webapp.PreInitializedServletState.init(StrictLifecycl
eServlet.java(Inlined Compiled Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(StrictLifecycleSer
vlet.java(Inlined Compiled Code))
at
com.ibm.servlet.engine.webapp.ServletInstance.init(ServletManager.java(Inlin
ed Compiled Code))
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [veltools] struts 1.1
Posted by Nathan Bubna <na...@esha.com>.
Teemu said:
> I have just recently started using the velocity-struts framework or
> whatever you wanna call it. With this debate, I'm now wondering
> whats all this about. Anyways can someone explain to me what has
> changed so much in struts1.1 that it would break 1.0 support
> in velocity-struts? I thought at least versions with .1 jump would be
> backwards compatible :) ?
the debate is mostly concerned with adding support for features that are new
in struts 1.1. adding support for those features would at the least mean
that you could no longer compile the velocity-struts code against Struts
1.0. You should still be able to use an already compiled velocity-struts
jar with struts 1.0, but you would have to make sure you didn't try to use
any new things that required struts 1.1.
at this point, not much 1.1-dependent code for velocity-struts has been
either written or suggested. the only thing i've added support for in my
local struts code is ActionMessages, and that is easily avoided. more
incompatible changes would be things like using the new Globals class
(things like Globals.MESSAGE_KEY instead of Action.MESSAGE_KEY). of course,
the Action keys are still there, but they've been deprecated. so, if we are
really concerned with keeping things backwards compatible (even though we
haven't had a release here), we'd have to keep using the deprecated code.
> Anyways if i move to 1.1 in both when they are released, will my old stuff
> still work without changes? Its no problem for me to move to the latest
> stuff but I dont wanna need to be making any changes to my code for it..
well, i'm not sure what number our first release will be given, but yes, i
believe you should be able to use your struts 1.0 code with struts 1.1
without making any changes. you will probably get deprecation warnings when
you compile your code against 1.1, but afaik, nothing should break.
Nathan Bubna
nathan@esha.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [veltools] struts 1.1
Posted by Teemu Kanstrén <te...@mail.student.oulu.fi>.
I have just recently started using the velocity-struts framework or
whatever you wanna call it. With this debate, I'm now wondering
whats all this about. Anyways can someone explain to me what has
changed so much in struts1.1 that it would break 1.0 support
in velocity-struts? I thought at least versions with .1 jump would be
backwards compatible :) ?
Anyways if i move to 1.1 in both when they are released, will my old stuff
still work without changes? Its no problem for me to move to the latest
stuff but I dont wanna need to be making any changes to my code for it..
THanks..
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [veltools] struts 1.1
Posted by Nathan Bubna <na...@esha.com>.
Tim said:
...
> Howabout the 1.0 release of the veltools support 1.0 Struts, and release
> 1.1.x supports Struts 1.1.x? :-)
ah, yes, releases... some people like those, don't they? :) anyway, this
sounds reasonable. maybe we should get a thread going on the dev list about
release(s)/features/fixes/roadmap stuff.
> I will jump onto Struts 1.1 as soon as I can...but that might be 6
> months out.
who knows? so could a Struts 1.1 release (not to mention a veltools
release). release dates are only set after the fact around here. :)
> > then it will have to
> > become their responsibility to speak up and demonstrate their
> > existence, continued need for 1.0 support, and willingness to
> > participate in that.
>
> I exist. I may be in the minority... but I'm loud and obnoxious! :-)
:)
> BTW - I don't want to support or focus primarily on the 1.0 Struts
> stuff... just want enough support/focus to have a working veltools lib
> for it.
i think we do have a working lib for it, right? i haven't been made aware
of any bugs at least. but i presume you want some sort of
tagged/built/maintained/whatever branch, right?
Nathan Bubna
nathan@esha.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [veltools] struts 1.1
Posted by Tim Colson <tc...@cisco.com>.
> new features/fixes to the Velocity-Tools libraries and yet
> continue building it against Struts 1.0,
Howabout the 1.0 release of the veltools support 1.0 Struts, and release
1.1.x supports Struts 1.1.x? :-)
I will jump onto Struts 1.1 as soon as I can...but that might be 6
months out.
> then it will have to
> become their responsibility to speak up and demonstrate their
> existence, continued need for 1.0 support, and willingness to
> participate in that.
I exist. I may be in the minority... but I'm loud and obnoxious! :-)
BTW - I don't want to support or focus primarily on the 1.0 Struts
stuff... just want enough support/focus to have a working veltools lib
for it.
Thanks,
Tim
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [veltools] struts 1.1
Posted by Nathan Bubna <na...@esha.com>.
Bill said:
...
> Nathan Bubna wrote:
> > Richard said:
> > It would be good to get a feel for what Velocity-Struts users are
> > doing/wanting. Is it important for people to continue being able to
> > build/use vel-struts with Struts 1.0? Or would people be ok with moving
> > right ahead to 1.1?
>
> It's rather inevitable that some users will not be able to move to 1.1
> right away. To support both versions, maybe the Ant build.xml could be
> structured such that one could build either version.
hmm. that might be difficult, or at least more work than it's worth. we
haven't released these libraries yet, and i don't presently anticipate a
future where we're maintaining two branches. sooner or later, we're gonna
make the switch. my feeling is that once 1.1 final is released, legitimate
reasons to hold off on supporting it quickly disappear. if there is enough
of a community that wants to benefit from new features/fixes to the
Velocity-Tools libraries and yet continue building it against Struts 1.0,
then it will have to become their responsibility to speak up and demonstrate
their existence, continued need for 1.0 support, and willingness to
participate in that. i don't think many people will be interested in
putting in time to support theoretical users, especially if it holds back on
development that helps the majority of users.
Nathan Bubna
nathan@esha.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [veltools] struts 1.1
Posted by Bill Burton <bi...@progress.com>.
Hello,
Nathan Bubna wrote:
> Richard said:
> It would be good to get a feel for what Velocity-Struts users are
> doing/wanting. Is it important for people to continue being able to
> build/use vel-struts with Struts 1.0? Or would people be ok with moving
> right ahead to 1.1?
It's rather inevitable that some users will not be able to move to 1.1
right away. To support both versions, maybe the Ant build.xml could be
structured such that one could build either version.
-Bill
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [veltools] struts 1.1
Posted by Tim Colson <tc...@cisco.com>.
> It would be good to get a feel for what Velocity-Struts users
> are doing/wanting. Is it important for people to continue
> being able to build/use vel-struts with Struts 1.0? Or would
> people be ok with moving right ahead to 1.1?
I'd love to ditch 1.0, but unfortunately one environment I run stuff in
is still Tomcat 3.2.x and supposedly Struts 1.1 isn't happy there.
So that means my vote is to keep 1.0 compatability in there somehow. :-(
Sorry,
Tim
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [veltools] struts 1.1
Posted by Richard Lamuette <tu...@laposte.net>.
As far as I am concerned, i think Struts1.1 beta is advanced enough to
migrate ...
-----Message d'origine-----
De : Nathan Bubna [mailto:nathan@esha.com]
Envoyé : vendredi 24 janvier 2003 20:03
À : Velocity Users List
Objet : Re: [veltools] struts 1.1
Richard said:
> I coded the ActionMessage support for Struts 1.1, but i dont know if i
have
> to do it for the generation of javascript in the stuts 1.1 validator
support
> ? I guess the future release is planned with the release of the struts 1.1
> final ...
This is a subject I've been meaning to bring up at some point. I do hope to
add (uncommented) support for struts 1.1 to the vel-struts library. At this
point, I too have modified my local copy to support 1.1 and no longer use
Struts 1.0. I've been watching struts-dev and it looks like a final release
may very well happen soon (maybe next month).
It would be good to get a feel for what Velocity-Struts users are
doing/wanting. Is it important for people to continue being able to
build/use vel-struts with Struts 1.0? Or would people be ok with moving
right ahead to 1.1?
Nathan Bubna
nathan@esha.com
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>