cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robby Pelssers" <>
Subject RE: Understanding Cocoon 2.2 URL Request Handlers
Date Tue, 11 May 2010 16:26:12 GMT
I don't see the problem...

Just create a launch configuration and start debuggin ;-)


-----Original Message-----
From: Mark Diggory [] 
Sent: Tuesday, May 11, 2010 5:55 PM
Subject: Re: Understanding Cocoon 2.2 URL Request Handlers


I have finally uncovered what is happening to cause error in loading
blocks and testing which lead to the previous error.  I've determined
that with the last release of the cocoon-servlet-service-impl (1.1.0
and 1.2.0), that something is just not right with the URL Protocol
Handler resolution in cocoon-jnet.  My solution has been to release
our own version of cocoon-servlet-service-impl with the necessary
fixes and no dependency on this jnet implementation.

However, now I have uncovered that when using Intellij IDEA, because
we are trying to execute blocks that are not packaged in jars, we get
the following error. Can anyone recommend a solution that will allow
blocks to be executed when working with unpackaged maven
target/classes directories such as those in IDEA and Eclipse?  Ideally
it would be great to not have to have everything packaged up into jars
to test/debug the webapplication, this defeats the point of using a
debugging IDE.

org.springframework.beans.factory.BeanCreationException: Error
creating bean with name
Invocation of init method failed; nested exception is
	at Method)


On Sat, May 8, 2010 at 4:01 PM, Mark Diggory <> wrote:
> Likewise,
> I'd like to get advice on the following... Which SitemapServlet should
> we be using in Cocoon 2.2?
> or
> Mark
> On Sat, May 8, 2010 at 3:37 PM, Mark Diggory <> wrote:
>> Cocoon Developers,
>> We continue to have problems utilizing the Cocoon 2.2 block
>> capabilities dues to not being able to resolve cocoon request handlers
>> where necessary.  Could someone please be so kind as to clarify where
>> the following request handlers are defined and how to configure them
>> appropriately now that there is no cocoon.xconf?
>> When we try to enable using cocoon blocks by adding the the cocoon
>> maven plugin to maven and defining our we get the
>> following type of error:
>> unknown protocol: resource
>>        at<init>(
>>        at<init>(
>>        at<init>(
>>        at org.apache.cocoon.core.container.spring.avalon.SourceResource.getURL(
>>        at org.apache.cocoon.core.container.spring.avalon.ConfigurationReader.convertSitemap(
>>        at org.apache.cocoon.core.container.spring.avalon.ConfigurationReader.readSitemap(
>>        at org.apache.cocoon.core.container.spring.avalon.SitemapElementParser.readConfiguration(
>>        at org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.parse(
>>        at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(
>> or in another place...
>> Caused by: org.springframework.beans.factory.BeanDefinitionStoreException:
>> Unable to read Avalon configuration from 'sitemap.xmap'.; nested
>> exception is unknown protocol:
>> resource
>>        at org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.parse(
>>        at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(
>>        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(
>>        at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(
>>        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(
>>        at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(
>>        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(
>>        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.j
>> Is this caused because we are missing a specific "block" for
>> registering Protocol Handlers like"resource" and "blockcontext"?
>> Cheers,
>> Mark Diggory

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message