On 4/11/07, Benamin <[EMAIL PROTECTED]> wrote:
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?
There is no list of all available services because message routing occurs using the service name, interface name or endpoint name. As for your HTTP consumer, it is exposed on http://localhost:8192/MyTest. The only thing you need to do is send a message to it at that URL. The easiest type of message to send is SOAP. Just make sure that soap="true" is added to the HTTP consumer configuration so that it will accept SOAP messages. After enabling that, just use SoapUI to point at the HTTP consumer URL and help you to generate a SOAP message to send to it. SoapUI makes it really easy. 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/
