Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 80955 invoked from network); 29 Oct 2009 09:09:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Oct 2009 09:09:17 -0000 Received: (qmail 97993 invoked by uid 500); 29 Oct 2009 09:09:16 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 97971 invoked by uid 500); 29 Oct 2009 09:09:16 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 97961 invoked by uid 99); 29 Oct 2009 09:09:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Oct 2009 09:09:16 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 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; Thu, 29 Oct 2009 09:09:14 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1N3R01-0004U1-OI for users@activemq.apache.org; Thu, 29 Oct 2009 02:08:53 -0700 Message-ID: <26109373.post@talk.nabble.com> Date: Thu, 29 Oct 2009 02:08:53 -0700 (PDT) From: cmoulliard To: users@activemq.apache.org Subject: ActiveMQ - HTTP - Remoting MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: cmoulliard@gmail.com Does it make sense to design a topology like this between different osgi servers to propose remote services though an ActiveMq queue playing the role of osgi server integrator ? 1) Bundle A This bundle contains a spring DSL xml file with routes defined like this : from(). .to() .to() .to(ActiveMq:queueOut) and service waiting feedback from(ActiveMq:queueIn). .to() deployed on server OSGI (1) 2) Bundle B from(ActiveMq:queueOut). .to() // Service replying to the request .to(ActiveMq:queueIn) deployed in server OSGI (2) Additional question : Are there any restrictions if we use HTTP transport connector of ActiveMq to place Java object on the queue (size, serialization, ....) ? Regards, ----- Charles Moulliard SOA Architect My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://www.nabble.com/ActiveMQ---HTTP---Remoting-tp26109373p26109373.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.