Yeah, it seems this is something that needs enhancements.
FWIW, James Strachan fixed that on ActiveMQ, so we need
to do the same on ServiceMix.
In the mean time, I would advise to use the xbean specific contexts.
One of the other reasons is that it supports QNames whereas spring does not,
so service="test:Hello" won't work in spring.
On 7/3/07, Cristian Pascu <[EMAIL PROTECTED]> wrote:
Hi all!
I am trying to get started with ServiceMix and I try to start the container
embedded within a Spring application context. However, I have difficulties
understanding how XBean works comparing with the standard namespace
mechanism in Spring.
The first thing that surprise me is that in the examples provided in the
site, the xsi:schemaLocation attribute is not present. Also, in the
spring.schemas files, the keys are not the URI's to a schema file, but the
namespace it self:
http\://servicemix.apache.org/config/1.0=servicemix.xsd
and not something like
http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd
in Spring distribution.
I am trying to run this example:
<sm:container id="jbi" embedded="true">
<sm:endpoints>
<jsr181:endpoint
pojoClass="org.apache.servicemix.itests.beans.Echo"
service="test:Hello" endpoint="testService" />
<http:endpoint service="test:Hello" endpoint="testService"
role="consumer" defaultOperation="echo"
locationURI="http://localhost:8194/Service/"; soap="true" />
</sm:endpoints>
</sm:container>
and I get this error:
org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching
wildcard is strict, but no declaration can be found for element
'sm:container'.
Is ServiceMix supposed to work within a Spring 2.0 application context? Or
should I create a XBean specific Spring application context?
Thanks a lot for your answers!
Cristian
--
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/
