Problem after trunk update

2008-04-25 Thread Robin Rigby 
Updated trunk.  Rebuild OK.  Then

mvn jetty:run 

gives this first

ERROR [main] (ContextLoader.java:214) - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: 
Unexpected exception parsing XML document from ServletContext resource
[/WEB-INF/applicationContext.xml]; 
nested exception is java.lang.VerifyError: (class:
org/apache/cocoon/generation/ServerPagesGenerator, method: generate
signature: ()V) 
Incompatible object argument for function call 

and more like it, then 

[INFO] Started Jetty Server

But the browser returns a 500 error.

Is this just me?

How do I identify which of the many /WEB-INF/applicationContext.xml in the
blocks referenced by cocoon-webapp is causing the problem?  The stack trace
indicates Spring was loading bean definitions (ServerPagesGenerator?) but
not which block.

Thanks

Robin



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem after trunk update

2008-04-27 Thread Joerg Heinicke 

On 25.04.2008 07:33, Robin Rigby wrote:

Updated trunk.  Rebuild OK.  Then

mvn jetty:run 


gives this first

ERROR [main] (ContextLoader.java:214) - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: 
Unexpected exception parsing XML document from ServletContext resource
[/WEB-INF/applicationContext.xml]; 
nested exception is java.lang.VerifyError: (class:

org/apache/cocoon/generation/ServerPagesGenerator, method: generate
signature: ()V) 
Incompatible object argument for function call 


Just a guess: Something in the ServerPagesGenerator has changed and it 
is not binary compatible. The hierarchy is now inconsistent if not 
everything has been recompiled. Does "mvn clean install" fix this?


Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]