In the attempt of migrating an application using JBPM 3.x to the upcoming JBoss 6 release (including Hibernate 3.5 CR1) I stumbled over the Hibernate Exception:
Code:
java.lang.UnsupportedOperationException: any not supported yet
at org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:441)
generated by hibernate 3.5 ejb.metamodel.AttributeFactory:
http://anonsvn.jboss.org/repos/hibernat ... ctory.javaCode:
....
if ( type.isAnyType() ) {
throw new UnsupportedOperationException( "any not supported yet" );
}
...
My questions are:
1. Will "any" be supported in the final 3.5 release finally?
2. In the mentioned project (working with JBoss 4.0.5) JBPM is configured to use the JBoss Datasource (hbm.xml files using the any declaration mapping,
are included into the ejb persistence.xml) and is referenced as an "ear module". Is there a configuration possibility to
not trigger the hibernate "ejb.metamodel.AttributeFactory" but something like a "plain Hibernate" attributeFactory for such Entities?