Yes, IIRC, this exception happen when the root element (the "beans" tag) in your xml has a wrong namespace. Allowed namespace for this element are: "" "http://xbean.apache.org/schemas/spring/1.0";
The usual way is to use the empty namespace. For example the following definition is bad: <beans xmlns="http://activemq.org/config/1.0";> <broker ... </beans> It used to work before spring rc2 or rc3 iirc. On 9/29/06, William Blackburn <[EMAIL PROTECTED]> wrote:
I finally got around to updating my app from a June snapshot to the 3.0 release. I can no longer deploy my servicemix webapp due to: http-8080-Processor24 2006-09-29 09:10:42,383 ERROR [ContextLoader:initWebApplicationContext] Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/activemq.xml]; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Failed to load type: beans. Reason: java.lang.ClassNotFoundException: beans; nested exception is java.lang.ClassNotFoundException: beans Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Failed to load type: beans. Reason: java.lang.ClassNotFoundException: beans; nested exception is java.lang.ClassNotFoundException: beans Caused by: java.lang.ClassNotFoundException: beans Normally I'd just find my missing dependency, but 'beans' isn't much to go on, so I'm stumped. The only thing thats changed between successful deployment and failure is I moved from the 6/16/06 snapshot to the 3.0 release version. Something to do with Spring 2 maybe? Any help greatly appreciated, BJ
-- Cheers, Guillaume Nodet
