It seems you are trying to deploy a service unit on the lightweight
container which includes endpoints for servicemix-http and
servicemix-eip, right ?
The advised packaging is to create two SUs, one for servicemix-http
and one for servicemix-eip and package them in a single SA.
If you really want to do that, you need to modify the classpath
of your SU to include the needed jars for servicemix-http and
servicemix-eip. These jars should be in your SU.
This can be done adding the following xml at the top of your servicemix.xml
for the lwcontainer SU:
<classpath>
<location>lib/servicemix-http-3.0-incubating.jar</location
<location>lib/servicemix-eip-3.0-incubating.jar</location
</location>
On 9/29/06, credmp <[EMAIL PROTECTED]> wrote:
Hi all,
Using the example at:
http://www.nabble.com/External-Webservices-binding-(the-answer)-tf1971463.html
I created a maven project to expose my own service.
The maven project consists out of a service-unit and a service-assembly. I
changed everything to my own situation and tossed it in an xbean.xml.
The maven plugin generates a couple of files:
service-unit jbi.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0">
<services xmlns:myns="http://myNameSpace/servicemix/1.0"
xmlns:ns1="http://server.service.ebuddy.com">
<provides service-name="myns:routerForAxis"
endpoint-name="wireTrapAxisEndpoint"/>
<consumes service-name="ns1:AxisWebservice"/>
<consumes service-name="myns:trace"/>
</services>
</jbi>
service-assembly jbi.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0">
<service-assembly>
<identification>
<name>server-service-assembly</name>
<description>ServiceMix :: Company :: Server :: Service ::
Assembly</description>
</identification>
<service-unit>
<identification>
<name>server-service-unit</name>
</identification>
<target>
<artifacts-zip>server-service-unit-1.0-SNAPSHOT.zip</artifacts-zip>
<component-name>servicemix-http</component-name>
</target>
</service-unit>
</service-assembly>
</jbi>
in the service unit the depencies include both the HTTP and EIP components:
<dependencies>
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-eip</artifactId>
<version>${servicemix-version}</version>
</dependency>
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-http</artifactId>
<version>${servicemix-version}</version>
</dependency>
</dependencies>
During the deployment I get the following error:
nested exception is java.lang.IllegalStateException: Unable to invoke
parseNestedCustomElement method
which is caused by:
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException:
Unrecognized xbean namespace mapping: http://servicemix.apache.org/eip/1.0
But maven seems to include all the dependencies just fine, I see both the
eip and http components being deployed and as far as I know (and see) the
jars are included:
[INFO] [jbi:jbi-service-unit]
[INFO] Resolving
org.apache.servicemix:servicemix-shared:jar:3.0-incubating-20060907.104512-31:compile
[INFO] Resolving
org.apache.servicemix:servicemix-eip:jar:3.0-incubating-20060907.104512-40:compile
[INFO] Resolving
org.apache.servicemix:servicemix-common:jar:3.0-incubating-20060907.104512-44:compile
[INFO] Resolving
org.apache.servicemix:servicemix-http:jar:3.0-incubating-20060907.104512-42:compile
Any advice you can give me?
Thanks
Arjen
xbean.xml:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:sm="http://servicemix.apache.org/config/1.0"
xmlns:eip="http://servicemix.apache.org/eip/1.0"
xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:ns1="http://server.service.company.com"
xmlns:myns="http://myNameSpace/servicemix/1.0">
<classpath>
<location>.</location>
</classpath>
<sm:serviceunit id="jbi">
<sm:activationSpecs>
<sm:activationSpec componentName="provider">
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint service="ns1:AxisWebservice"
endpoint="axisWebserviceEP"
targetService="ns1:AxisWebservice"
role="provider"
locationURI="http://localhost:8080/ServerService-1.0-SNAPSHOT/services/ServerService"
wsdlResource="http://localhost:8080/ServerService-1.0-SNAPSHOT/services/ServerService?wsdl"
/>
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
<sm:activationSpec componentName="consumer">
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint service="ns1:AxisWebservice"
endpoint="axisWebserviceEP"
targetService="myns:routerForAxis"
role="consumer"
soap="true"
targetInterfaceName="ns1:AxisWebservicePortType"
locationURI="http://localhost:8180/services/AxisService/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out" />
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
<sm:activationSpec componentName="trace"
service="int:trace">
<sm:component>
<bean xmlns="http://xbean.org/schemas/spring/1.0"
class="org.apache.servicemix.components.util.TraceComponent" />
</sm:component>
</sm:activationSpec>
<sm:activationSpec componentName="wireTrapAxis">
<sm:component>
<eip:component>
<eip:endpoints>
<eip:wire-tap endpoint="wireTrapAxisEndpoint"
service="myns:routerForAxis">
<eip:target>
<eip:exchange-target service="ns1:AxisWebservice" />
</eip:target>
<eip:outListener>
<eip:exchange-target service="myns:trace" />
</eip:outListener>
</eip:wire-tap>
</eip:endpoints>
</eip:component>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:serviceunit>
</beans>
--
View this message in context:
http://www.nabble.com/Unrecognized-xbean-namespace-mapping%3A-http%3A--servicemix.apache.org-eip-1-tf2356781.html#a6564579
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet