cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jakob Praher <jpra...@yahoo.de>
Subject Re: [headsup!] NPE in sitemap reloading (the first time!)
Date Thu, 24 Apr 2003 22:45:36 GMT
interesting as when I cvs -z3 co update CocoonComponentManager.java,
line 456 looks something like:

449:    /**
450:     * Releases a resolved resource
451:     */
453:    public void release( final Source source ) {
454:        this.sourceResolver.release( source );
455:    }
456:
457:}

my CocoonComponentManager has Revision: 1.50, what's your revision ?

-- Jakob

Am Don, 2003-04-24 um 19.04 schrieb Stefano Mazzocchi:
> Running the latest and gretest CVS HEAD today, everytime I modify the
> sitemap and it gets reloaded, I get the following:
> 
> java.lang.NullPointerException
> 	at
> org.apache.cocoon.components.CocoonComponentManager.resolveURI(CocoonComponentManager.java:456)
> 	at
> org.apache.cocoon.environment.AbstractEnvironment.resolveURI(AbstractEnvironment.java:490)
> 	at
> org.apache.cocoon.environment.AbstractEnvironment.resolveURI(AbstractEnvironment.java:480)
> 	at org.apache.cocoon.generation.FileGenerator.setup(FileGenerator.java:104)
> 	at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:378)
> 	at
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:651)
> 	at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:505)
> 	at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:467)
> 	at
> org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:150)
> 	at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
> 	at
> org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164)
> 	at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
> 	at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:162)
> 	at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108)
> 	at
> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:162)
> 	at
> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:325)
> 	at
> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:307)
> 	at org.apache.cocoon.Cocoon.process(Cocoon.java:640)
> 	at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1103)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
> 	at
> org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
> 	at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
> 	at
> org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:507)
> 	at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
> 	at org.mortbay.http.HttpServer.service(HttpServer.java:863)
> 	at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
> 	at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
> 	at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
> 	at
> org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
> 	at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
> 	at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)
> 
> It seems that the source resolver is set to null when the sitemap is
> cleaned up but its set back only *after* the first request.
> 
> i don't have time to go there and fix it, but it should be pretty
> trivial, yet a pretty serious issue.


Mime
View raw message