I would add that the above code runs fine in jboss container.
While narrowing down my example code, I discovered that the error occurs if and only if I exclude artifact hibernate, group org.hibernate, from hibernate annotations depedendency.
I'm not sure this isn't self inflicted. Seems reasonable for jboss tools to depend on my project's build path.
Still want a issue report in JBIDE?
Also, a related question. After the UserType errors were elimintated, this one became apparent.
Description Resource Path Location Type Discriminator column "DTYPE" cannot be resolved on table "equipment" Equipment.java /xxxxxx/src/main/java/com/xxxxxxx line 85 JPA Problem
Its true that dtype is not on the table. I thought hibernate does not use a discriminator in this case. The application works fine in jboss as 6 with the same database definition.
Yeah, if you remove hibernate types from the classpath the type hiearchy is incomplete and thus we can't check the correctness.
But that said we should be able to see the type and that the subclass is *named* properly so I think we can improve on that situation. Please open a jira for it.
hmm - please add that to https://jira.jboss.org/jira/browse/JBIDE
it might be a default Eclipse JPA validation rule that we haven't customized or in worst case can't customize. In any case please open a bug on it and we'll take a look.
Type validation of Type/TypeDef is our problem(Please ignore it, we'll fix it soon). I have checked and org.jasypt.hibernate.type.EncryptedStringType implements UserType and ParametrizedType through AbstractEncryptedAsStringType.
I create a jira for it https://issues.jboss.org/browse/JBIDE-11364
He stated he use:
jboss by redhat, Hibernate tools: 3.4.0v20120307-2104-H60-Beta1
jboss by redhat, jboss as tools: 2.3.0.v20120308-1629-H87-Beta1
Indigo Service Release 2 Build id: 20120216-1857
so that is the latest afaics.
You are right and this is even more strange, because I can't reproduce this on Beta1