Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Message-ID: <412503F8.8040803@gmx.ch>
Date: Thu, 19 Aug 2004 21:48:08 +0200
From: Jakob Braeuchi <jbraeuchi@gmx.ch>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT;
 rv:1.7.2) Gecko/20040803
MIME-Version: 1.0
To: OJB Developers List <ojb-dev@db.apache.org>
Subject: Re: [OJB 1.1] MetadataManager issue
References: <411A4984.40509@apache.org>
In-Reply-To: <411A4984.40509@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

hi armin,

QueryByCriteria#setObjectProjectionAttribute also uses MM directly.

jakob

Armin Waibel schrieb:

> Hi all,
> 
> as I said in my initial 1.1 post there are some issues in code:
> 
> ======================
> MetadataManager use
> ======================
> Some classes still use MetadataManager.getInstance() and lookup object 
> metadata or connection metadata information. But in 1.1 you only can 
> lookup metadata of the current used PC when the PBKey/PCKey or a PB 
> instance was used.
> 
> 
> - DatabaseHandlingTask
> should be easy to fix when an OJB instance was used or when the 
> MetadataManager will be usable in standalone mode for tool support.
> 
> 
> - QueryByCriteria#buildCriteria(Object anExample)
> here the MM was used to lookup the ClassDescriptor of the given object. 
> QueryByCriteria has public constructor and can currently be reused by PB 
> instances of different PC, thus we can't bind a PB, PC or PCKey to this 
> class. But reuse of Query objects could be problematic when using 
> different model for the same class (one model supports all fields, the 
> other model only PK + name).
> Should we use an Query service bind to a PB instance. In that case we 
> can set a PCKey/PBkey in the query object and can lookup current PC to 
> lookup metadata information and the PB instance can check the PCKey 
> before perform a getCollectionByQuery(...) or similar???
> 
> 
> - OQLParser#selectQuery
> again MM was used to lookup classDescriptor of query object on parsing.
> 
> 
> - jdoql.QueryTreeResolver
> again used for parsing
> 
> 
> - graph.ObjectWrapper
> ???
> 
> A hard nut to crack ;-)
> 
> regards,
> Armin
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org