You need to add the namespace declaration and schema uri, as spring use
strict matching, which means it mandates all the schema have a valid xsd
available.
Take a look at the xsi:schemaLocation as in the available example:

http://svn.apache.org/repos/asf/activemq/camel/trunk/examples/camel-example-osgi/src/main/resources/META-INF/spring/camelContext.xml

On Dec 4, 2007 7:48 PM, dlaidlaw <[EMAIL PROTECTED]> wrote:

>
> I am trying to load up a CamelContext in the equinox OSGi engine using
> Spring-DM-rc1. I have all the dependencies satisfied, with camel-core,
> camel-spring, camel-jms and servicemix's jaxb-api bundles. All these
> bundles
> start OK.
>
> In my bundle using the Spring-DM stuff to create a spring context I added:
>
>
>        <bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
>                <property name="connectionFactory"
> ref="connectionFactory"/>
>        </bean>
>
>        <camelContext id="camel"
>                                xmlns="
> http://activemq.apache.org/camel/schema/spring";
>                                useJmx="false"
>        >
>                <route>
>                        <from uri="jms:queue:test.queue.1" />
>                        <to uri="file://test.queue.1?noop=true"/>
>                </route>
>        </camelContext>
>
> But when the bundle is loading and Spring is creating the context I get:
>
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line
> 67 in XML document from OSGi
> res[/META-INF/spring/bundle-context.xml|61|symName=don.sample.listener] is
> invalid; nested exception is org.xml.sax.SAXParseException:
> cvc-complex-type.2.4.c: The matching wildcard is strict, but no
> declaration
> can be found for element 'camelContext'.
>
> For some reason, the camelContext element will not resolve.
>
> Any hints?
> --
> View this message in context:
> http://www.nabble.com/Camel-with-Spring-DM-rc1-and-equinox-tf4944939s22882.html#a14156945
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to