cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <gkossakow...@apache.org>
Subject Re: [test] Cocoon 2.2-RC1 & others (take 2)
Date Sat, 23 Jun 2007 16:55:11 GMT
xweber pisze:
> Hi,
> 
> I tried to follow the tutorials with latest rc1 files.
> (http://cocoon.zones.apache.org/daisy/cdocs/g2/g2/g1/1291.html)
> 
> On the connecting example (Connect two blocks) I receive an error like
> 
> java.lang.RuntimeException: Cannot invoke listener
> org.springframework.web.context.ContextLoaderListener@1d5b883
> ..
> Unable to read spring configurations from classpath
> ..
> 
> on mvn jetty:run startup 
> 
> Maybe it is related to the rc1 build.

I think you found little trap in our current setup. When two blocks containing demo classes
are connected they define exactly the same 
Spring component (same package and same component id) twice. In my setup this does not lead
to exception, just first Java class and last 
declaration of component is used. Try to change a class name/package and Spring Id of the
component (don't forget to change in flowscript 
too) and everything should be working fine.
Please report if it's the case.

I don't think it's show-stopper for release, we just should put an information about work-around
in docs and fix it in RC2 that would follow 
RC1 quickly (I hope you all remember independent release cycles).

As regards the fix, do you have a good idea how to make demo beans unique? Do you think that
appending block's name (artifact Id) is a good 
idea? Is artifact Id strict enough to not brake name of class?

-- 
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/

Mime
View raw message