You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Gabriel Sidler <si...@teamup.ch> on 2002/04/21 17:50:08 UTC
[VelTools ] FYI: ant build bug for jakarta-velocity-tools
Geir, can you comment on the following two issues?
Thanks
Gabe
Tim Colson wrote:
...
> This isn't important at all...but do you know how to shut up the DVSL
> error?
> [dvsl] [error] ResourceManager : unable to find resource
> 'VM_global_library.vm' in any resource loader.
>
> Like I said, not important - I'm just curious.
This unproblematic error message confuses people. How can we
avoid it?
...
> First roadblock of the evening, some Tomcat 3.2.1 errors. I backed up my
> somewhat hacked version of Tomcat (we have some odd path settings so it
> mimics our production servers), and expanded a fresh copy from zip (I'm
> running on Win XP Pro with JDK 1.3.1_02).
>
> Smells like an error with JAXP... thoughts?
>
> Resolving to alternate DTD
> 'jar:file:D:\java\jakarta-tomcat-3.2.1\webapps\velstruts\WEB-INF\lib\str
> uts.jar!/org/apache/struts/resources/web-app_2_2.dtd'
> Call
> org.apache.struts.action.ActionServlet.addServletMapping(action/java.lan
> g.String,*.do/java.lang
> .String)
> Call
> org.apache.struts.action.ActionServlet.addServletMapping(velocity/java.l
> ang.String,*.vm/java.la
> ng.String)
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/xml/sax/XMLReader
> at
> org.apache.velocity.tools.view.servlet.ServletToolboxManager.<init>(Serv
> letToolboxManager
> .java:222)
> at
> org.apache.velocity.tools.view.servlet.VelocityViewServlet.init(Velocity
> ViewServlet.java:
> 186)
> at
> org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
> at org.apache.tomcat.core.Handler.init(Handler.java:215)
> at
> org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296)
> at
> org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnSta
> rtupInterceptor.j
> ava:130)
> at
> org.apache.tomcat.core.ContextManager.initContext(ContextManager.java:49
> 1)
> at
> org.apache.tomcat.core.ContextManager.init(ContextManager.java:453)
> at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:195)
> at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
> D:\java\jakarta-tomcat-3.2.1\bin>
>
...
> Upgrading to JAXP 1.1 (i.e. update jaxp.jar, add crimson.jar, remove
> parser.jar) seems to solve the issue.
>
> Fortunately (although not at TC 4.x) our production environment has TC
> 3.2.3 and JAXP 1.1 - so I'm okay with this; however, is this something
> that can be fixed for other folks who might not be so lucky?
> Are you aware of what might be causing the depend on JAXP 1.1?
>
> Cheers,
> Tim
--
Gabriel Sidler
Software Engineer, Eivycom GmbH, Zurich, Switzerland
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VelTools ] FYI: ant build bug for jakarta-velocity-tools
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 4/21/02 11:50 AM, "Gabriel Sidler" <si...@teamup.ch> wrote:
> Geir, can you comment on the following two issues?
>
> Thanks
> Gabe
>
>
> Tim Colson wrote:
> ...
>
>> This isn't important at all...but do you know how to shut up the DVSL
>> error?
>> [dvsl] [error] ResourceManager : unable to find resource
>> 'VM_global_library.vm' in any resource loader.
>
>>
>
>> Like I said, not important - I'm just curious.
>
>
> This unproblematic error message confuses people. How can we
> avoid it?
>
>
There actually two issues I have with this. I don't like how the DVSL ant
task logs now - too confusing to see the vel log stream by default - so I am
going to start there.
I also might just snuff it out in vel proper as it confuses people.
>
> ...
>
>> First roadblock of the evening, some Tomcat 3.2.1 errors. I backed up my
>> somewhat hacked version of Tomcat (we have some odd path settings so it
>> mimics our production servers), and expanded a fresh copy from zip (I'm
>> running on Win XP Pro with JDK 1.3.1_02).
>>
>> Smells like an error with JAXP... thoughts?
>>
>> Resolving to alternate DTD
>> 'jar:file:D:\java\jakarta-tomcat-3.2.1\webapps\velstruts\WEB-INF\lib\str
>> uts.jar!/org/apache/struts/resources/web-app_2_2.dtd'
>> Call
>> org.apache.struts.action.ActionServlet.addServletMapping(action/java.lan
>> g.String,*.do/java.lang
>> .String)
>> Call
>> org.apache.struts.action.ActionServlet.addServletMapping(velocity/java.l
>> ang.String,*.vm/java.la
>> ng.String)
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> org/xml/sax/XMLReader
>> at
>> org.apache.velocity.tools.view.servlet.ServletToolboxManager.<init>(Serv
>> letToolboxManager
>> .java:222)
>> at
>> org.apache.velocity.tools.view.servlet.VelocityViewServlet.init(Velocity
>> ViewServlet.java:
>> 186)
>> at
>> org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
>> at org.apache.tomcat.core.Handler.init(Handler.java:215)
>> at
>> org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296)
>> at
>> org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnSta
>> rtupInterceptor.j
>> ava:130)
>> at
>> org.apache.tomcat.core.ContextManager.initContext(ContextManager.java:49
>> 1)
>> at
>> org.apache.tomcat.core.ContextManager.init(ContextManager.java:453)
>> at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:195)
>> at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
>> D:\java\jakarta-tomcat-3.2.1\bin>
>>
> ...
>> Upgrading to JAXP 1.1 (i.e. update jaxp.jar, add crimson.jar, remove
>> parser.jar) seems to solve the issue.
>>
>> Fortunately (although not at TC 4.x) our production environment has TC
>> 3.2.3 and JAXP 1.1 - so I'm okay with this; however, is this something
>> that can be fixed for other folks who might not be so lucky?
>> Are you aware of what might be causing the depend on JAXP 1.1?
I'll take a look...
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
POC lives!
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>