Bug 2837 - Internal Servlet Error: NoClassDefFoundError
Summary: Internal Servlet Error: NoClassDefFoundError
Status: CLOSED WONTFIX
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: general (show other bugs)
Version: all
Hardware: PC other
: P3 blocker
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-26 09:30 UTC by Dave Richardson
Modified: 2012-04-01 13:48 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Richardson 2001-07-26 09:30:33 UTC
Hi there,

I'm trying to get the FopServlet class included with the Fop distribution to 
work but I keep getting the above error when I include the ?fo= parameter.

I'm working with a Win 2K Advanced Server with IIS 5, and I've also installed 
the following:

JDK 1.3
Apache 1.3.20 (service working fine, using port 8040)
Jakarta-Tomcat 3.2.3 (service working fine, using port 8041)
Jakarta ISAPI redirector (virtual directory is in IIS and ISAPI filter is up 
and running)
FOP 0.19.0-CVS (works fine when I run it from the command line but *not* when 
I'm using the FopServlet).

I can run the Jakarta examples OK, and I've copied the fop.war file into the 
webapps folder and created a context for fop.  If I fire up my browser and go 
to http://localhost:8041/fop/servlet/fop it says I need the 'fo' parameter so 
it must be running the servlet code, but when I add on the ?fo=... it falls 
over with an internal servlet error:

java.lang.NoClassDefFoundError:org/apache/fop/apps/Driver
at org.apache.fop.tools.servlet.FopServlet.renderFO(FopServlet.java:117)
at org.apache.fop.tools.servlet.FopServlet.doGet(FopServlet.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) etc...

I've checked my .jar files and all the classes directly referenced by the 
Driver appear to be there. That's as far as I've got so far - can someone shed 
light on what might be missing or what I've done wrong?!?

Cheers!

Dave.
Comment 1 J.Pietschmann 2002-04-22 08:02:24 UTC
This kind of problem has always more to do with the servlet
container than FOP.
The prepackaged servlet delivered with FOP 0.20.3 seem to work
well with Tomcat 3 and Tomcat 4 exceptp 4.0.3 (which has known
bugs)
Comment 2 Glenn Adams 2012-04-01 13:48:41 UTC
batch transition to closed remaining pre-FOP1.0 resolved bugs