EnumType.STRING unknown values

alvins82 · **Joined:** Thu Mar 20, 2008 1:27 am **Posts:** 5

Hi,

We are doing staged releases to our production environment and at points we will have two different versions of our code running.

If we add new Enum values into a version - the old version has problems running because it starts getting exceptions with unknown values when it is trying to map these enums.

Is there a way so we can tell hibernate to ignore enums which can't be mapped so we can keep running both versions?

Thanks,
Alvin

alvins82 · **Joined:** Thu Mar 20, 2008 1:27 am **Posts:** 5

Anyone?

schauder · **Joined:** Thu Jul 05, 2007 9:38 am **Posts:** 287

you could replace the table by a view that hides the new values ...
Or you could define such filter in hibernate (I think) check out WHERE and FILTER Attributes

alvins82 · **Joined:** Thu Mar 20, 2008 1:27 am **Posts:** 5

I solved the issue via AOP - however this is not the ideal solution.

Code:

@Component
@Aspect
public class TestAOP {

   @Around("execution(* org.hibernate.type.EnumType.nullSafeGet(*,*,*))")
    public Object doBasicProfiling(ProceedingJoinPoint pjp) throws Throwable {
      try {         
          Object retVal = pjp.proceed();
          return retVal;
      } catch (IllegalArgumentException e) {
      }
      return null;
     }
}

alvins82 · **Joined:** Thu Mar 20, 2008 1:27 am **Posts:** 5

..duplicate.