EJB 3.1 and evil StaticMetamodel

[oranheim]

Hi all,

Timely, Java 6 got rid of XML through Annotation and stuff. As a Weld / CDI user I love it. After searching Google I don't find many people complaining about @StaticMetamodel. The new way to describe your meta-model. This doesn't seem thought through from my perspective, since most meta data is already described. What's the point and why do I have to re-constitute my data model in order satisfy CriteraBuilder.

Am I on the wrong track here?

What's the point? This to me seems like a wrong path, as it's in the code, already!?

How come I get have to move from bloated XML code to bloated Annotated code?

Why?

Cheers

PS! Why not make a way to encompass anomalies of already existing code.

[jaikiran]

Ove,

The @StaticMetamodel isn't related to EJB3.1. It's a JPA construct. You might want to ask this question in a JPA specific forums like Hibernate. You have a better chance of getting it answered there, than here.

By the way, I guess you have already come across this http://docs.jboss.org/hibernate/entitymanager/3.5/reference/en/html/metamodel.html

[oranheim]

Thanks for your clarification and I've managed to set up a pre-processor for my JPA beans generating my meta-model. I'll move this topic over to Hibernate forum.