fellow the
Tutorials(http://incubator.apache.org/servicemix/hello-world-se.html), when
use the follow command:
mvn archetype:create \
-DarchetypeGroupId=org.apache.servicemix.tooling \
-DarchetypeArtifactId=servicemix-service-unit \
-DarchetypeVersion=3.1-incubating \
-DgroupId=org.apache.servicemix.samples.helloworld.se \
-DartifactId=hello-world-su \
-DremoteRepositories=http://people.apache.org/repo/m2-incubating-repository
we get a service unit project.  After use "mvn install" command, we get file
hello-world-su-1.0-SNAPSHOT.jar which will be deployed to dir deploy of
servicemix. But in the file hello-world-su-1.0-SNAPSHOT.jar, there is only a
valid file,that is jbi.xml, the content like that:
<?xml version="1.0" encoding="UTF-8"?>
<jbi xmlns="http://java.sun.com/xml/ns/jbi"; version="1.0">
  <services binding-component="false"/>
</jbi>
in the jbi.xml no service name or service type name is specified, how can
others services can consume the service engine we just built.
on the topic "Questions about Hello World
Example"(http://www.nabble.com/Questions-about-Hello-World-Example-tf3036579s12049.html#a9248585),
CharlesP wants to use a Http binding component consume the Service Engine. 
The xbean.xml of the http bc like that:
<beans xmlns:http="http://servicemix.apache.org/http/1.0"; 
    xmlns:replaceMe="http://servicemix.apache.org/replaceMe";> 
  <http:endpoint service="hello-world-se-su" 
                 endpoint="soap" 
                 role="consumer" 
                 locationURI="http://0.0.0.0:8192/example/"; 
                 defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; 
                 soap="true" />             

</beans> 
in the xbean.xml, no targetservice is specified, how can the http request
can route to the se we just built? help!

-- 
View this message in context: 
http://www.nabble.com/Question-about-hello-world-bc-example---related-to-topic-%22Questions-about-Hello-World-Example%22-tf3648931s12049.html#a10192360
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to