cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <j...@socialchange.net.au>
Subject Re: JRun 3.0 with 1.8.2 - jar hell
Date Sun, 25 Feb 2001 06:40:26 GMT
On Sat, Feb 24, 2001 at 02:59:34PM +0100, Torsten Curdt wrote:
> > On Fri, Feb 23, 2001 at 06:20:28PM +0100, Torsten Curdt wrote:
> > > > I just tried to upgrade our site from 1.8 to 1.8.2.
> > > > We are running on JRun 3.0. Everything worked fine
> > > > before, but now as soon as I place the w3c.jar or the xml.jar
> > > > into the classpath JRun won't come up.
> > > > 
> > > > I guess it's something about a collision in the org.w3c.*
> > > > packages somewhere...
> > > > 
> > > > The latest installation instruction obviously don't work.
> > > > Can anyone give me a hint who has gone through this before?
> > > 
> > > Ok, found it... the w3c.jar was corrupt (the META-INF was missing)
> > > Could someone please doublecheck and commit a correct jar to the CVS!?
> > > (Robin? Shall I send the jar to you?)
> > 
> > You're right, lib/w3c.jar is missing a manifest. Does that necessarily make it
> > corrupt? 'jar tvf' works fine. What error was JRun giving?
> 
> error (JRun) JRun Aborting! [javax.servlet.ServletException: Could not instantiate allaire.jrun.jsp.JSPServlet]
> javax.servlet.ServletException: Could not instantiate allaire.jrun.jsp.JSPServlet
> javax.servlet.ServletException: Could not instantiate allaire.jrun.jsp.JSPServlet
> 	at allaire.jrun.servlet.JRunServletLoader.loadServletInstance(JRunServletLoader.java:242)
> 	at allaire.jrun.servlet.JRunSE.initServices(JRunSE.java:620)
> 	at allaire.jrun.servlet.JRunSE.init(JRunSE.java:187)
> 	at allaire.jrun.ServletService.init(ServletService.java:66)
> 	at allaire.jrun.ServletService.init(ServletService.java:31)
> 	at allaire.jrun.servlet.JRunServletLoader.loadServletInstance(JRunServletLoader.java:236)
> 	at allaire.jrun.servlet.JRunSE.initServices(JRunSE.java:620)
> 	at allaire.jrun.servlet.JvmContext.initServices(JvmContext.java:96)
> 	at allaire.jrun.servlet.JRunSE.init(JRunSE.java:187)
> 	at allaire.jrun.servlet.JvmContext.init(JvmContext.java:35)
> 	at allaire.jrun.ServletService.init(ServletService.java:66)
> 	at allaire.jrun.ServletService.init(ServletService.java:31)
> 	at JRun.main(JRun.java:130)

That confirms what I've experienced before.. the JRun developers seem to have
the following annoying habit:

try {
	...
} catch (UsefulException e) {
	throw CrappyJRunException("An error occurred");
}

In this case, something like:

try {
	..
	Map m = new JarFile("w3c.jar").getManifest().getEntries();
	..
} catch (NPE) {
	throw new ServletException("JRun Aborting!");
}

Though I'm quite probably wrong.

Anyway, can we get w3c.jar fixed?

--Jeff

> This was really strange... I never thought a missing manifest could be the
> problem. Anyway, this was the only difference to the other jars.
> 
> Now it works!
> --
> Torsten
> 
> 
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
> For additional commands, e-mail: <cocoon-users-help@xml.apache.org>

-- 

Mime
View raw message