The problem is that the jbi maven plugin checks the dependency to find
which component is the target for a given SU.
You should be able to do that but you need to set a property
specifying that your target component is servicemix-cxfse. See
http://fisheye6.cenqua.com/browse/servicemix/branches/servicemix-3.1.2/archetypes/servicemix-ode-service-unit/src/main/resources/archetype-resources/pom.xml?r=576233
for an example.
On 9/19/07, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> I'm trying to startup the NotificationBroker for Servicemix but was getting
> some errors when I add the notification broker to my existing cxf SU. I
> boiled down one of the errors to including the servicemix-http dependency in
> my cxf SU, so if I add this dependency to my cxf service:
>
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-http</artifactId>
> <version>${servicemix-version}</version>
> </dependency>
>
> then I get the following error (if I comment out that dependency, then it's
> fine). Is this an illegal thing to do? I'm guessing it's overriding xbean
> definitions somehow:
>
> <component-task-result xmlns="
> http://java.sun.com/xml/ns/jbi/management-message";>
> <component-name>servicemix-http</component-name>
> <component-task-result-details>
> <task-result-details>
> <task-id>deploy</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Could not deploy xbean service unit</loc-message>
> </msg-loc-info>
> </task-status-msg>
> <exception-info>
> <nesting-level>1</nesting-level>
> <msg-loc-info>
> <loc-token/>
> <loc-message>
> org.springframework.beans.factory.BeanDefinitionStoreException: Unre
> cognized xbean namespace mapping: http://servicemix.apache.org/cxfse/1.0
> </loc-message>
> <stack-trace><