> I agree it's horrific but it got rid of a bunch of
> crappy code that I'd have to maintain.
I hear you there. :-)
> It wasn't a straightforward search (I meandered
> through a bunch of pages for a couple days before I
> found it):
>
> http://blog.blackbit.be/?p=5
But even here he's indicating that the domain.xml file solves a JPA integration problem, not a classpath scanning problem. That is, before he put the domain.xml down, he could (presumably) get the EJBContainer to find his EJBs. I can't do that, with exactly his code. The only thing that has changed is that I am depending on v3.0.1b02, not b74 as he has in his example.
I think I'm going to make a dirt simple maven project that manifests this problem and file it as a critical showstopping bug, because at least that way someone else can reproduce it and explain to me how all these tutorials have it wrong. Man, what a frustrating day.
Thanks again.
[Message sent by forum member 'ljnelson']
http://forums.java.net/jive/thread.jspa?messageID=395778