Affects Version/s: 126.96.36.199
Fix Version/s: None
Windows, Oracle Java 6, latest Release (_45)
We are trying to deploy an application (war) which uses spring-data-jpa.
At deploy time GlassFish tries to instantiate two spring-data-jpa framework classes as beans (org.springframework.data.jpa.repository.support.JpaRepositoryFactoryBean and org.springframework.data.jpa.repository.support.QueryDslRepositorySupport).
This classes have a @PersistenceContext-annotation at their setEntityManager-methods, but no annotation at class level which declares this classes as beans.
I think it's wrong behavior for an application server to try to instantiate classes which have no "bean annotation" like @Statefull ...
I think it's no duplicate of GLASSFISH-4204 because it's no annotation at class level.
This makes spring-data-jpa unusable on GlassFish (you do not need to like spring, but spring-data is realy cool). We have no problems with spring-data on jetty or tomcat (which are of course no JEE container), but we have to extend an application which unfortunately relies on some other JEE features. spring-data-jpa will save us 3/4 of the work to do for this task.