forgot to send it to the list instead of directly ....so here you go :) ----- Original Message ----- From: "Max Rydahl Andersen" <[EMAIL PROTECTED]> To: "Gavin King" <[EMAIL PROTECTED]> Sent: Sunday, October 27, 2002 3:33 PM Subject: Re: [Hibernate] Metadata, codegenerator et.al...
> > > Any suggestions on formats/semantics of it all ? (property and attribute > > are > > > dubious names in > > > this db context, so is custom-attribute a good tag-name/metadata name > for > > > it ?) > > > > How about <metadata name="foo" value="bar"/> > > So, we got a metadata to augment/describe the metadata - well, I suppose > that's the > way it is supposed to be :) > > > > I would love to contribute the above mentioned stuff, if I had a clear > > > vision on the existing parsing and building > > > of metadata info in Hibernate....and currently it seems that Hibernate > > > CANNOT parse an hbm.xml without > > > having the related classes in its classpath ...and that is somewhat of > an > > > limitiation when it is a codegenerator that > > > is about to generate these classes :) > > > > Good point. > > > > > Anyone with a clear vision and understanding of hibernates hbm.xml > parsing > > > that can untangle that web of assumptions > > > in the hibernate core ? > > > > Okay, there are two levels of metadata. The "parsed" metadata, represented > > by the cirrus.hibernate.map package and the "compiled" metadata which is > > really just the internal state of the EntityPersisters. > > > > You have no chance of using the compiled metadata. On the other hand, it > > would be reasonably easy to remove any references to actual classes from > the > > cirrus.hibernate.map package which is used to represent the internal state > > of Datastore. If you could clean up that package a little bit, it would > > probably do what you want. Now, that package is definately not meant to be > > exposed to users, but you might be able to expose it to the toolset. > > I've tried to dig into the map package, but it seems there is waaay to many > places > the code tries to do a classForName to check if it can continue to do its > parsing - > and by waaay to many, I mean waaay to many for me to go changing the parse > semantics :( > > So, I'll try to "just" add the metadata tag stuff...that should be doable > without changing much > of the semantics, but it sure won't be as usable when the parser still > requires the classes to > be available ;( > > /max > ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
