Errors in contextblock

Mansour Al Akeel <[email protected]>
Newsgroups gmane.text.xml.cocoon.user
Message-ID <CAFvvX=bZYkN61ZCmSGuH+2+8Gv0n_vcXu=pmjvBHv5+PLm=0ew@mail.gmail.com>
A block that was working few weeks ago, now is throwing an exception:

00:31:25.886 [btpool0-1] DEBUG o.a.c.jci.stores.MemoryResourceStore -
reading resource java/lang/ObjectBeanInfo.class
00:31:25.895 [btpool0-1] DEBUG o.a.c.s.DispatcherServlet -
DispatcherServlet: service
servlet=org.apache.cocoon.servlet.XMLSitemapServlet@1d1f967
mountPath=/contents servletPath=/contents
pathInfo=/article/760917/en.xml
00:31:25.900 [btpool0-1] DEBUG o.s.b.f.s.DefaultListableBeanFactory -
Returning cached instance of singleton bean
'org.apache.cocoon.jnet.URLHandlerFactoryCollector'
00:31:25.901 [btpool0-1] DEBUG o.s.b.f.s.DefaultListableBeanFactory -
Returning cached instance of singleton bean
'org.apache.cocoon.configuration.Settings'
00:31:25.909 [btpool0-1] ERROR o.a.cocoon.servlet.XMLSitemapServlet -
Can't initialize the RequestProcessor correctly.
org.apache.cocoon.servlet.RequestProcessor$InvalidBaseUrlException: An
exception occurred while retrieving the base URL from the servlet
context.
        at org.apache.cocoon.servlet.RequestProcessor.initializeBaseURL(RequestProcessor.java:174)
~[cocoon-servlet-3.0.0-beta-1-SNAPSHOT.jar:3.0.0-beta-1-SNAPSHOT]
        at org.apache.cocoon.servlet.RequestProcessor.<init>(RequestProcessor.java:81)
~[cocoon-servlet-3.0.0-beta-1-SNAPSHOT.jar:3.0.0-beta-1-SNAPSHOT]
        at org.apache.cocoon.servlet.XMLSitemapServlet.lazyInitialize(XMLSitemapServlet.java:68)
[cocoon-servlet-3.0.0-beta-1-SNAPSHOT.jar:3.0.0-beta-1-SNAPSHOT]
        at org.apache.cocoon.servlet.XMLSitemapServlet.service(XMLSitemapServlet.java:46)
[cocoon-servlet-3.0.0-beta-1-SNAPSHOT.jar:3.0.0-beta-1-SNAPSHOT]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
[servlet-api-2.5-6.1.7.jar:6.1.7]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[na:1.6.0_37]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
~[na:1.6.0_37]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
~[na:1.6.0_37]

.....

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
[jetty-6.1.7.jar:6.1.7]
	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:828)
[jetty-6.1.7.jar:6.1.7]
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
[jetty-6.1.7.jar:6.1.7]
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
[jetty-6.1.7.jar:6.1.7]
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
[jetty-6.1.7.jar:6.1.7]
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
[jetty-6.1.7.jar:6.1.7]
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
[jetty-util-6.1.7.jar:6.1.7]
Caused by: java.net.MalformedURLException: unknown protocol: blockcontext
	at java.net.URL.<init>(URL.java:574) ~[na:1.6.0_37]
	at java.net.URL.<init>(URL.java:464) ~[na:1.6.0_37]
	at java.net.URL.<init>(URL.java:413) ~[na:1.6.0_37]
	at org.apache.cocoon.servletservice.ServletServiceContext.getResource(ServletServiceContext.java:114)
~[cocoon-servlet-service-impl-1.3.2.jar:1.3.2]
	at org.apache.cocoon.servlet.RequestProcessor.initializeBaseURL(RequestProcessor.java:168)
~[cocoon-servlet-3.0.0-beta-1-SNAPSHOT.jar:3.0.0-beta-1-SNAPSHOT]
	... 55 common frames omitted
00:31:25.910 [btpool0-1] DEBUG o.a.c.jci.stores.MemoryResourceStore -
reading resource org/apache/cocoon/servlet/XMLSitemapServlet.class



This is the bean definition:

        <bean name="ca.example.cms.contents.service"
class="org.apache.cocoon.servlet.XMLSitemapServlet">
                <servlet:context mount-path="/contents"
context-path="blockcontext:/contents/" />
        </bean>



I am not sure if something changed recently, but now it's not
recognizing blockcontext !!!!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.