>> Can you show me what this xbean.xml file for the SU that wraps my SE should >> look like?
> It's completely dependent upon the implementation of your SE. At a > minimum you'll need to define a namespace, provide a service name and > an endpoint name. Beyond that it's dependent upon the parameters that > are exposed by your SE that will need to be configured. >> My new configuration for the http su looks like this: >> >> <beans xmlns:http="http://servicemix.apache.org/http/1.0"; >> xmlns:test="http://servicemix.apache.org/samples/MyTest";> >> >> <!-- add this to config: targetService="Endpoint_Of_SU_That_Wraps_SE" --> >> <http:endpoint service="test:http" >> endpoint="endpoint" >> role="consumer" >> locationURI="http://0.0.0.0:8192/MyTest/"; >> defaultMep="http://www.w3.org/2004/08/wsdl/in-only"; /> >> >> </beans> >> >> I attempt to deploy this using an SA, and ServiceMix provides a message >> saying the SA was deployed, but if I browse to localhost:8192, I do not >> see >> my service available. Any thing I can look for to see why it might not >> be >> available? > What are you expecting to see when you visit http://localhost:8192? What I would expect to see is a list of available services. All I want to do is be able to send a SOAP request (like what the bridge example sends in the client.html) which contains some xml data. Then forward that xml data from the http su to my su that wraps my se. The se then does the rest of the work. I thought by sending the xml data from the http su to the su that wraps the se that the data would arrive at the MyEndpoint::processInOut() method for my se. Is that right? -- View this message in context: http://www.nabble.com/How-to-send-messages-between-service-units-tf3555183s12049.html#a9943325 Sent from the ServiceMix - User mailing list archive at Nabble.com.
