thanks for you help! I just to know how to give the SU a service name, use
the following 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
a SU project is created, but I don't know the service name, and how to give
service name for the SU.

bsnyder wrote:
> 
> On 4/25/07, gc y <[EMAIL PROTECTED]> wrote:
>>
>> 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.
> 
> What you built is a JBI compliant service engine (SE) - messages are
> not routed to the SE, they're routed to a SU that depends upon the SE.
> The SE gets deployed to the JBI container and just sits there waiting
> for a configuration to tell it how to behave. A SU is what contains a
> configuration for a SE and this configuration is what contains a
> service name. The SU is what messages get routed to.
> 
>> 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!
> 
> That example doesn't seem to be complete because there is no
> targetService attribute defined and he didn't create a WSDL with a
> soap:address pointing to the same URL as the locationURI. Charles was
> only pulling pieces of the wsdl-first example and trying to adapt them
> to his situation. I'm not sure of the details of your situation, but
> if you have not defined a WSDL, you'll need to use the targetService
> attribute.
> 
> Bruce
> -- 
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
> 
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Castor - http://castor.org/
> 
> 

-- 
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#a10193728
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to