Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 50187 invoked from network); 2 Feb 2009 16:25:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Feb 2009 16:25:50 -0000 Received: (qmail 4249 invoked by uid 500); 2 Feb 2009 16:25:50 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 4231 invoked by uid 500); 2 Feb 2009 16:25:50 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 4220 invoked by uid 500); 2 Feb 2009 16:25:50 -0000 Delivered-To: apmail-activemq-camel-user@activemq.apache.org Received: (qmail 4217 invoked by uid 99); 2 Feb 2009 16:25:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 08:25:50 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 16:25:42 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LU1bt-00086r-Vg for camel-user@activemq.apache.org; Mon, 02 Feb 2009 08:25:21 -0800 Message-ID: <21792749.post@talk.nabble.com> Date: Mon, 2 Feb 2009 08:25:21 -0800 (PST) From: aliasrob To: camel-user@activemq.apache.org Subject: Help with camel relaying HTTP msg between .Net web client and .Net service. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: aliasrobM@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hello, we are using a .NET client to communicate over http: with a .NET web service. We are attempting to send a message directly to Camel from the .NET client, and then have camel relay that message to the service. Then the service will then reply back to Camel and Camel should send that reply message back to the client. We wish to do all this over HTTP without adding any of these messages to a JMS queue. So the process would look something like this Message sent out {Client Machine} --Http Message out --> {Camel Machine} -- Http Message out --> {Service Machine} Message returned {Client Machine} <-- Http Message retuned --< {Camel Machine} <-- Http Message retuned <-- {Service Machine} Our main problem right now is how to configure the endpoints and which files need hold the information. In other words, what HTTP endpoint address does the client side send a message to in order to reach Camel? (How do we expose Camel as an HTTP endpoint that is reachable by the client?) Also, how do we then forward that message from Camel to our .NET service over HTTP? Are there any settings in .wsdl we and web.config files which we need to pay particular attention to? Any help on how resolve this issue would be greatly appreciated. Please provide an example of any xml settings etc. Thanks Rob -- View this message in context: http://www.nabble.com/Help-with-camel-relaying-HTTP-msg--between-.Net-web-client-and-.Net-service.-tp21792749s22882p21792749.html Sent from the Camel - Users mailing list archive at Nabble.com.