I'd prefer something convention-based and user-configurable like Fabio has done with ConfORM. That's the approach I had in mind. Attributes smell, and I believe the XSD has been the same for a while now, so best not to change it if possible.
My two cents, Jason On Mon, Mar 22, 2010 at 9:07 AM, Tuna Toksoz <[email protected]> wrote: > Sorry Simon, > > I am sorry, i just missed this email. > > 1. I don't know about AuditSync, my port was incomplete and i think i > didn't get into that class yet. > 2. Annotations are for EntityManager (of JPA). They are used for mapping > entities, just like XML. > > For Envers configuration, I was planning to discard XML configuration > completely, and only have fluent interface. Makes things a lot easier, and > also harder at the same time. > > Please let me know if you need anything else. > > > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksoz > http://tunatoksoz.com > http://twitter.com/tehlike > > > > > On Mon, Mar 22, 2010 at 2:15 PM, Simon Duduica <[email protected]> wrote: > >> Hey, any answer at all would be greatly appreciated! >> >> I got over point 1., 2 is still actual and now I got stuck in the >> following problem: The xml mapping document for Envers needs some >> added attributes for the tag key-property (insert and update, both >> bool) and for key-many-to-one (type), but the schema validation fails >> because of these added properties in >> NHibernate.Cfg.XmlHbmBinding.Binder.Deserialize[T](XmlNode node) >> >> This is the mapping: >> >> <hibernate-mapping assembly="Envers.NET" xmlns="urn:nhibernate- >> mapping-2.2" auto-import="false"> >> <class entity-name="Envers.Net.Model.Address_AUD" >> table="Address_AUD"> >> <composite-id name="originalId"> >> <key-property name="id" insert="true" >> update="false" >> type="SimpleValue"> >> <column name="id" length="255" >> scale="2" precision="19" /> >> </key-property> >> <key-many-to-one type="integer" >> class="NHibernate.Envers.DefaultRevisionEntity" name="REV"> >> <column name="REV" /> >> </key-many-to-one> >> </composite-id> >> <property name="REVTYPE" insert="true" >> update="false" >> type="NHibernate.Envers.Entities.RevisionTypeType" /> >> </class> >> </hibernate-mapping> >> >> The first option seems to add the attributes to tne hibernate- >> mapping.xsd schema. What do you think? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "NHibernate Contrib - Development Group" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<nhcdevs%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/nhcdevs?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "NHibernate Contrib - Development Group" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhcdevs%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhcdevs?hl=en. > -- You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhcdevs?hl=en.
