Another option is to put the metaclass code in BootStrap. The problem with the plugin approach is that delete() is lazily added to the metaclass when the first dynamic method is called at runtime, so your version will get replaced. But you can force the initialization of the metaclass methods by calling one of them, e.g. get(-1) which is pretty lightweight:
> You can hook into the Hibernate initialization with a custom Configuration subclass and set the persister there:
>
> package com.yourcompany.yourapp;
>
> import java.util.Collection;
>
> import org.codehaus.groovy.grails.orm.hibernate.cfg.GrailsAnnotationConfiguration;
> import org.hibernate.MappingException;
> import org.hibernate.mapping.PersistentClass;
> import org.hibernate.mapping.RootClass;
>
> public class MyHibernateConfiguration extends GrailsAnnotationConfiguration {
>
> private static final long serialVersionUID = 1;
>
> private boolean _alreadyProcessed;
>
> @SuppressWarnings("unchecked")
> @Override
> protected void secondPassCompile() throws MappingException {
> super.secondPassCompile();
>
> if (_alreadyProcessed) {
> return;
> }
>
> for (PersistentClass pc : (Collection<PersistentClass>)classes.values()) {
> if (pc instanceof RootClass) {
> RootClass root = (RootClass)pc;
> if ("Foo".equals(root.getClassName())) {
> root.setEntityPersisterClass(MyEntityPersister.class);
> }
> }
> }
>
> _alreadyProcessed = true;
> }
> }
>
> To use this, put the class in src/java and register it using the 'configClass' attribute:
>
> dataSource {
> pooled = true
> driverClassName = ...
> username = ...
> password = ...
> configClass = com.yourcompany.yourapp.MyHibernateConfiguration
> }
>
> But if you're just trying to block deleting instances, you can use the beforeDelete event hook:
>
> transient beforeDelete = {
> throw new IllegalAccessException('Delete not allowed')
> }
>
> Burt
>
> > Just a followup
> >
> > the EntityPersister was just an idea to reuse a ready and tested
> > artifact. Basically I'm interested in overriding the delete save
> > methods of GraislDomain Objects.
> >
> > I'm trying also the plugin approach but something like
> >
> > def doWithDynamicMethods = { applicationContext ->
> >
> > application.domainClasses.each { domainClass ->
> >
> > domainClass.metaClass.delete = { ->
> > println("HEY!!!!!!!!!!!!!!! Do not delete ever!")
> > }
> > }
> >
> > doesn't seem to work.
> >
> > 2010/5/7 ::SammyRulez:: <
[hidden email]>:
> > > looking at the code of GrailsDomainBinder it would be possible if I
> > > can access the org.hibernate.mapping.PersistentClass of the
> > > DomainClass... any ideas?
> > >
> > > 2010/5/7 Peter Ledbrook <
[hidden email]>:
> > >>> Dealing with a legacy database I'm trying to reuse a Hibernate
> > >>> EntityPersister (which extends SingleTableEntityPersister ).
> > >>>
> > >>> I can't figure how to use GROM mapping to add my custom
> > >>> EntityPersister to Grails domain Objects and I cant find documentation
> > >>> about it.
> > >>
> > >> I'm afraid this doesn't seem possible. Hopefully someone else will be
> > >> able to confirm this one way or the other, but I can't see anything in
> > >> the code.
> > >>
> > >> Cheers,
> > >>
> > >> Peter
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe from this list, please visit:
> > >>
> > >>
http://xircles.codehaus.org/manage_email> > >>
> > >>
> > >>
> > >
> > >
> > >
> > > --
> > > SammyRulez
> > >
http://www.sammyrulez.com> > >
http://twitter.com/sammyrulez> > >
http://www.linkedin.com/in/sammyrulez> > >
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>
Locked
