Re: [Hibernate] Keep information on a per Sf basis or per EntityPersister basis

[Max R. A. <max...@jb...>]

On Sun, 02 Jul 2006 03:32:35 +0200, Emmanuel Bernard  
<emm...@hi...> wrote:

> Because the configuration can be reused and changed.
> The idea is that my lucene engine (ie hibernate event) needs it.
> This is actually very close to the notion of cache which is part of the  
> core.

Shouldn't it then be upgraded to something more specific than untypede  
metaattributes?

Anyhow, I've always been +1 on adding some notion/possibility of  
"annotating" the metamodel
in Hibernate to allow for more extensibility, but it never really made it  
through because
it could always be read/accessed through the Configuration model.

/max

>
> Max Rydahl Andersen wrote:
>>
>> On Sat, 01 Jul 2006 20:02:46 +0200, Emmanuel Bernard  
>> <emm...@hi...> wrote:
>>
>> > For the Lucene integration I need to keep track of the  
>> DirectoryProvider
>> > associated to a given entity.
>> > Basically DirectoryProvider are shared across several entities.
>> > I might also need to keep track of some informations on a per SF  
>> basis.
>> >
>> > Currently there is no good way to do it.
>> > It might make sense to have some sort of copy of metaAttributes  
>> between
>> > PersistentClass and EntityPersister.
>> >
>> > WDYT?
>>
>> metaAttributes were not moved in to the core "compiled" model because
>> the core persistence engine does not need them.
>>
>> AFAIK it still does not need them, so why not build some external "data  
>> repository"
>> or simply keep the Configuration (maybe a serialized clone) around for  
>> these special cases ?
>>
>> --
>> --
>> Max Rydahl Andersen
>> callto://max.rydahl.andersen
>>
>> Hibernate
>> ma...@hi...
>> http://hibernate.org
>>
>> JBoss Inc
>> max...@jb...
>>
>



-- 
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
ma...@hi...
http://hibernate.org

JBoss Inc
max...@jb...