Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » tomcat-juli.jar not on classpath in tomcat6
tomcat-juli.jar not on classpath in tomcat6 [message #211752] Thu, 03 April 2008 16:19 Go to next message
Eclipse UserFriend
Originally posted by: adam.hardy.no.spam.cyberspaceroad.spam

I have a project which uses the Tomcat Jasper code to precompile JSPs. Jasper is
currently on the classpath via the Apache Tomcat 6 plugin.

However, I run into this when using it:

java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
at org.apache.jasper.servlet.JspServlet.<init>(JspServlet.java:60)

and I checked what's what and my tomcat installation has tomcat-juli.jar in its
/bin directory and the jar doesn't make it into the classpath available to the
project.

It's OK running in-container, this is fine - however I would like to use tomcat
running just as a dependency of a JUnit test.

As a work-around, I copied the tomcat-juli.jar from tomcat/bin to tomcat/lib. It
seems to accept the duplication of the jar.

What about future? Is it probable that the tomcat plugin will have to
incorporate the tomcat/bin dir into the classpath?

Thanks
Adam
Re: tomcat-juli.jar not on classpath in tomcat6 [message #211761 is a reply to message #211752] Thu, 03 April 2008 16:37 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry IsaacsFriend
Messages: 1310
Registered: July 2009
Senior Member
adam hardy wrote:
> I have a project which uses the Tomcat Jasper code to precompile JSPs.
> Jasper is currently on the classpath via the Apache Tomcat 6 plugin.
>
> However, I run into this when using it:
>
> java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
> at org.apache.jasper.servlet.JspServlet.<init>(JspServlet.java:60)
>
> and I checked what's what and my tomcat installation has tomcat-juli.jar
> in its /bin directory and the jar doesn't make it into the classpath
> available to the project.
>
> It's OK running in-container, this is fine - however I would like to use
> tomcat running just as a dependency of a JUnit test.
>
> As a work-around, I copied the tomcat-juli.jar from tomcat/bin to
> tomcat/lib. It seems to accept the duplication of the jar.
>
> What about future? Is it probable that the tomcat plugin will have to
> incorporate the tomcat/bin dir into the classpath?
>
> Thanks
> Adam

When using the WTP Tomcat support, tomcat-juli.jar will automatically be
included on the "classpath" due to its presence in the Class-Path
attribute found in the MANIFEST.MF file in Tomcat 6's bootstrap.jar. If
you launch Tomcat in a way that doesn't honor this Class-Path attribute,
then you would need to add it, and possibly others in that list, manually.

Cheers,
Larry
Re: tomcat-juli.jar not on classpath in tomcat6 [message #211781 is a reply to message #211761] Fri, 04 April 2008 10:03 Go to previous message
Eclipse UserFriend
Originally posted by: adam.hardy.no.spam.cyberspaceroad.spam

Larry Isaacs on 03/04/08 17:37, wrote:
> adam hardy wrote:
>> I have a project which uses the Tomcat Jasper code to precompile JSPs.
>> Jasper is currently on the classpath via the Apache Tomcat 6 plugin.
>>
>> However, I run into this when using it:
>>
>> java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory
>> at org.apache.jasper.servlet.JspServlet.<init>(JspServlet.java:60)
>>
>> and I checked what's what and my tomcat installation has
>> tomcat-juli.jar in its /bin directory and the jar doesn't make it into
>> the classpath available to the project.
>>
>> It's OK running in-container, this is fine - however I would like to
>> use tomcat running just as a dependency of a JUnit test.
>>
>> As a work-around, I copied the tomcat-juli.jar from tomcat/bin to
>> tomcat/lib. It seems to accept the duplication of the jar.
>>
>> What about future? Is it probable that the tomcat plugin will have to
>> incorporate the tomcat/bin dir into the classpath?
>>
>> Thanks
>> Adam
>
> When using the WTP Tomcat support, tomcat-juli.jar will automatically be
> included on the "classpath" due to its presence in the Class-Path
> attribute found in the MANIFEST.MF file in Tomcat 6's bootstrap.jar. If
> you launch Tomcat in a way that doesn't honor this Class-Path attribute,
> then you would need to add it, and possibly others in that list, manually.

OK, I will follow that. Thanks alot.
Adam
Previous Topic:projects missing from J2EE module dependencies
Next Topic:MalformedInputException on tag files
Goto Forum:
  


Current Time: Thu Nov 27 04:49:48 GMT 2014

Powered by FUDForum. Page generated in 0.02052 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software