For quite some time I've used ejb3unit to test my EJB3 entities, but now I decided to give it a try to test the integrated session beans (I often use spring-test features althought it causes some testing configuration overhead).
Well, making a long history short I've faced a problem regarding named queries declared on xml mapping-files. Since it builds its own persistence context, of course it will never know what orm files I'm using, but that's an issue for the architecture I'm working on.
Can you guys think in a workaround for that? Is there any hidden hack to declare some classpath mapping file inside a BaseSessionBeanFixture test instance?