Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 51973 invoked from network); 18 Oct 2008 01:26:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Oct 2008 01:26:34 -0000 Received: (qmail 32245 invoked by uid 500); 18 Oct 2008 01:26:36 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 32219 invoked by uid 500); 18 Oct 2008 01:26:35 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 32208 invoked by uid 99); 18 Oct 2008 01:26:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Oct 2008 18:26:35 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com designates 72.14.220.157 as permitted sender) Received: from [72.14.220.157] (HELO fg-out-1718.google.com) (72.14.220.157) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Oct 2008 01:25:26 +0000 Received: by fg-out-1718.google.com with SMTP id 16so572785fgg.44 for ; Fri, 17 Oct 2008 18:26:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=/M2IKEK/tORv7CqCCMoSGmgyXq8VBsk5ZIp/zxRR8+c=; b=odY+ruFAt3sDspJeMxmXeOMjJ9Y6DNJbVpPHj5eXrb6dMT3mQ9MnUUYrlM4J3a7nfx PVJpdDngOpHnNLxKMmhmGYH00tE9GGxlqLA9x78uvj/x/7vuXn/64qVCO7AUdRaMcdzo V0GuzULyhpTsd4Jue+xnnuyvqvWGE+owULfiw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=Iwa8CrKAe0OJxLJTGi1ucdze1D7w8A+yZDhfZoIf4OyplXs8W1CfiD66XN8/RxvkXE J6qJUZTCQGgjeS3XuwLC7yOf8rbS5oC56J7JreXK5/IImpv835bPam+o2KkVRbTlaaPv 8o7CUu++9RAKa4vhebB32Pz5Jun5ziALixuoM= Received: by 10.181.20.6 with SMTP id x6mr47549bki.167.1224293162620; Fri, 17 Oct 2008 18:26:02 -0700 (PDT) Received: by 10.181.7.20 with HTTP; Fri, 17 Oct 2008 18:26:02 -0700 (PDT) Message-ID: Date: Sat, 18 Oct 2008 09:26:02 +0800 From: "Willem Jiang" To: camel-user@activemq.apache.org Subject: Re: Camel inside CXF or CXF inside Camel In-Reply-To: <48F92537.3010709@die-schneider.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_109966_29564875.1224293162632" References: <20030207.post@talk.nabble.com> <48F8AF8B.7070901@die-schneider.net> <20041730.post@talk.nabble.com> <48F92537.3010709@die-schneider.net> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_109966_29564875.1224293162632 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline In CXF , we leverage the servlet transport to publish the service through Tomcat. Maybe we can port some part of CXF Servlet to Camel, in this way we can deploy Camel Servlet transport into Tomcat and send the message into a camel context :) Thoughts? Willem On Sat, Oct 18, 2008 at 7:52 AM, Christian Schneider < chris@die-schneider.net> wrote: > Hi Christopher, > > if I understand you right you want to have a http endpoint that simply > receives a soap message and sends it to a topic. Is that right? > In that case you do not need cxf at all. cxf is only needed if you want to > deserialize the soap message and call a java implementation. > > Simply do something like that in camel: > > from("jetty:http://localhost:8080/myapp/myservice > ").to("jms://topic:topicname") > > Look at the jetty and jms components for more details. > > I think the jetty component is normally used if you are not running in > tomcat. I do not know how to receive a request using tomcat but I am > sure someone can help here. > > Greetings > > Christian > > > huntc schrieb: > >> Hi Christian, >> >> Thank you for the guidance here. I have indeed read your fine article >> although I am curious as to what the CXF web service implementation should >> do if all that is required is to pass on its parameters as a Camel >> Exchange, >> and return success if it can do so successfully. Any advice there? >> >> Kind regards, >> Christopher >> >> >> >> > > > -- > > Christian Schneider > --- > http://www.liquid-reality.de > > ------=_Part_109966_29564875.1224293162632--