Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 17952 invoked from network); 11 Feb 2009 11:43:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Feb 2009 11:43:48 -0000 Received: (qmail 68417 invoked by uid 500); 11 Feb 2009 11:43:48 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 68379 invoked by uid 500); 11 Feb 2009 11:43:47 -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 68368 invoked by uid 500); 11 Feb 2009 11:43:47 -0000 Delivered-To: apmail-activemq-camel-user@activemq.apache.org Received: (qmail 68365 invoked by uid 99); 11 Feb 2009 11:43:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2009 03:43:47 -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 (nike.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; Wed, 11 Feb 2009 11:43:36 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LXDUp-0002RW-DZ for camel-user@activemq.apache.org; Wed, 11 Feb 2009 03:43:15 -0800 Message-ID: <21953127.post@talk.nabble.com> Date: Wed, 11 Feb 2009 03:43:15 -0800 (PST) From: cmoulliard To: camel-user@activemq.apache.org Subject: camel-cxf component & dependencies jars !! MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: cmoulliard@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I would like to know what is the best/quickest way to design OSGI librairies/bundles for a project ? First of all, let's start with a example : camel + cxf To deploy such a project top of SMX kernel 1.x, I need of course to create an osgi project for my code. This project can be created using mvn archetype (maven-felix-plugin), bnd or pax-contruct my.company.osgi.camel.cxf Let's says that this osgi bundle depends on : camel-core 2.0-SNAPSHOT, camel-spring 2.0-SNAPSHOT, camel-cxf 2.0-SNAPSHOT Those dependencies already exist as OSGI bundles (thanks for Camel team), so I can install them easily in SMX Kernel 1.x But these dependencies depends on additional jars which are potentially not at all 'OSGI'fied like org.apache.cxf.* (2.2-SNAPSHOT). Moreover, apache cxf depends on another jars. Questions : - How can I easily/quickly detect which jars are not 'osgi'fied' to avoid to iterate through cycles of deployment, looking in the log and discovering that dependencies are unresolved ? - What is the best strategy to OSGIfied them ? I mean 'use by example the option 'embed-transitive' of bnd tools (which is used by maven-felix-plugin or pax-constrcut)'. But the risk is that too much jars are embedded in my osgi bundle or wrapped separetely Regards, ----- Charles Moulliard SOA Architect My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://www.nabble.com/camel-cxf-component---dependencies-jars-%21%21-tp21953127s22882p21953127.html Sent from the Camel - Users mailing list archive at Nabble.com.