Return-Path: 
 <users-return-42391-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 72FCE10B69
	for <apmail-camel-users-archive@www.apache.org>;
 Tue,  3 Sep 2013 10:35:46 +0000 (UTC)
Received: (qmail 83856 invoked by uid 500); 3 Sep 2013 10:35:45 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 83659 invoked by uid 500); 3 Sep 2013 10:35:45 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 83651 invoked by uid 99); 3 Sep 2013 10:35:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 10:35:44 +0000
X-ASF-Spam-Status: No, hits=0.6 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.175 as permitted sender)
Received: from [209.85.223.175] (HELO mail-ie0-f175.google.com)
 (209.85.223.175)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 10:35:41 +0000
Received: by mail-ie0-f175.google.com with SMTP id u16so9405140iet.6
        for <users@camel.apache.org>; Tue, 03 Sep 2013 03:35:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=QyW2B2YogM1BOUkCGklFat3G4zxQRyAbMVMY04ScQvA=;
        b=uopqaiGE8jikZwLP+MbP4TcAHuDBnfR+f6cQBhDdEd2ycD4YQrYZs8z37NxNtD6HyK
         yQvoPgVe8DRk58wSu0xrjOxk73yNnqpHU4Aq/aQ6uODrU/ovOlRV1bgzv19Wt9Twbunc
         IZr9r1o7dU7hJHI1zmDZ67b9ZKjHnvOByAj/OHY+80/xjwBkqVccmKqt2i2FUeJqp+Xa
         gRwXE3ofGx7ZbVH1qq3FG2mI2S4ITZ4Nq9lS//Ngj1hOSeW5saoth/6VF4ybSH61bdrK
         tRKeL7uosf1WwOOWrQVtO9hZVkLcmOOse3YXtiCwnRlTY8+ivMH4+jv4vCQQ7BCYww7f
         djng==
X-Received: by 10.42.146.1 with SMTP id h1mr4093461icv.38.1378204520656; Tue,
 03 Sep 2013 03:35:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.20.196 with HTTP; Tue, 3 Sep 2013 03:34:59 -0700 (PDT)
In-Reply-To: <1378033398426-5738423.post@n5.nabble.com>
References: <1377962419040-5738400.post@n5.nabble.com>
 <1378033398426-5738423.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 3 Sep 2013 12:34:59 +0200
Message-ID: 
 <CAGB5yNn=fTXwNJ-azJ_2vOD4PdNkXO_5NYNyxW_=WRzN+wKKHQ@mail.gmail.com>
Subject: Re: Missing datasource exception while referring to OSGI datasource
 for clustering quartz with camel-quartz
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Hi

As its Quartz which does the DataSource lookup then wonder how it does
the lookup?
Though I assume spring users with quartz may have defined their data
sources as spring <bean>.
So maybe you can find some information how to tell quartz to lookup in
spring etc. Then spring-dm in OSGi ought to work with it.

There is also a new camel-quartz2 component in Camel 2.12. Maybe
quartz2 would work better with OSGi ?

On Sun, Sep 1, 2013 at 1:03 PM, lakshmi.prashant
<lakshmi.kala.venkatesan@sap.com> wrote:
> Hi,
>
>  I have already referred to the datasource (OSGI service) in the beans.xml:
>
>  <reference id="dataSource" interface="javax.sql.DataSource"
> filter="(dataSourceName=default)" />
>
> a) And I had already tried referring to the datasource using the reference
> id, in quartz properties:
>
>   <bean id="quartz"
> class="org.apache.camel.component.quartz.QuartzComponent">
>         <property name="properties"><props>
>                      <prop
> key="org.quartz.jobStore.dataSource">*dataSource*</prop>....
>           </props></properties>
>  </bean>
>
> b) Also, I had earlier tried to refer the datasource by the osgi service
> name..
>
>    <bean id="quartz"
> class="org.apache.camel.component.quartz.QuartzComponent">
>         <property name="properties"><props>
>                      <prop
> key="org.quartz.jobStore.dataSource">*default*</prop>....
>           </props></properties>
>  </bean>
>
>
> None of the 3 approached had worked.
>
> Exception trace while referring to bean reference id.
>
>
> Failed to obtain DB connection from data source 'dataSource':
> java.sql.SQLException: There is no DataSource named 'dataSource'
> org.quartz.JobPersistenceException: Failed to obtain DB connection from data
> source 'dataSource': java.sql.SQLException: There is no DataSource named
> 'dataSource' [See nested exception: java.sql.SQLException: There is no
> DataSource named 'dataSource']
>
> Thanks,
> Lakshmi
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Missing-datasource-exception-while-referring-to-OSGI-datasource-for-clustering-quartz-with-camel-quaz-tp5738400p5738423.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen