Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 37975 invoked from network); 10 Sep 2004 13:13:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Sep 2004 13:13:55 -0000 Received: (qmail 62471 invoked by uid 500); 10 Sep 2004 13:13:54 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 62335 invoked by uid 500); 10 Sep 2004 13:13:53 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 62317 invoked by uid 99); 10 Sep 2004 13:13:52 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=MANY_EXCLAMATIONS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [209.137.167.162] (HELO filter.fridayfives.net) (209.137.167.162) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 10 Sep 2004 06:13:51 -0700 Received: by filter.fridayfives.net (Postfix, from userid 5054) id D85C46FC84; Fri, 10 Sep 2004 08:00:36 -0400 (EDT) Received: from freki (freki [127.0.0.1]) by freki (Postfix) with SMTP id E54086FC90 for ; Fri, 10 Sep 2004 08:00:35 -0400 (EDT) Received: from [192.168.1.30] (kite.forthill.int [192.168.1.30]) by filter.fridayfives.net (Postfix) with ESMTP id 831686FC84 for ; Fri, 10 Sep 2004 08:00:35 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <3771DD0767EB764AA9AA1D2758B9768E02DC7081@ban01bxgxs.internal.gxs.com> References: <3771DD0767EB764AA9AA1D2758B9768E02DC7081@ban01bxgxs.internal.gxs.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3DF9976A-032B-11D9-BDC5-000A95782782@forthillcompany.com> Content-Transfer-Encoding: 7bit From: Brian McCallister Subject: Re: OJB query! please help ! Date: Fri, 10 Sep 2004 09:13:44 -0400 To: "OJB Developers List" X-Mailer: Apple Mail (2.619) X-Spam-Bayes-Score: 0.0000 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on freki X-Spam-Level: X-Spam-Status: No, hits=-4.1 required=5.0 tests=BAYES_00,MANY_EXCLAMATIONS autolearn=no version=2.63 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N In all honesty, I wouldn't recommend using OJB's JDO api yet. The existing JDO 1.0.1 implementation is quite weak, and is more proof-of-concept than anything. The reflective nature of OJB persistence just never really encouraged anyone to flesh out 1.0.1. We are actively working on a JDO 2.0 right now (supports reflective persistence), with an (optimistic) timeline of around November for it being usable. This largely depends on where the spec goes as the last public showing of the spec was in June and rumour has it more changes to it are coming from feedback garnered then =) -Brian On Sep 10, 2004, at 9:05 AM, GuptaTTG@gxs.com wrote: > Hi > > I am currently evaluating different JDO products to use in my project. > Right now I am in the process of evaluating OJB (JDO API) and and > trying to > reverse engineer from the DB schema. > > We are building a search facility using a JDO solution we are > considering to > use OJB for this purpose. We have a requirement to allow the search > users to > search only a subset of attributes from a class. For example an entity > consists of 10 attributes but if the users is interested only in two > attributes then he should be able to specify only those two attributes > in > the search. Some of JDO solutions support this feature by allowing > "Featch > groups" in JDO queries. My question is does OJB - JDO support this > feature, > or is there any other way to implement this using OJB - JDO. > > Thanks in Advance. > Regards, > Tarun > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org