u, make that "EJB 3.0 dependency injection annotations only works in EJB
objects -- not generic POJOs" oh well, I have to take it all back... no,
seriously, I got that wrong, but it's still cool. Some automation is better
than none and, last time I checked, SpringFramework (et. al.) plays
OK, random obnoxious dissing aside, I'm going through some EJB3 intro material
on the JBoss site and am beginning to smile again about standards-based J2EE
development. At long last. And I know there's a real debt to Gavin and other
Hibernate folks for getting the standards going in the right
Thanks for all the great, no wait, make that insanely great hints and advice.
My sarcasm (arrogance?) came from reading the JBoss trail. On-and-on about how
things are decoupled... sounds nice, then the switch to an example and the
example shows: by default, things are coupled via a name... K
OK, now that the flame baits out of the way Following the EJB3 trail I
read:
<>
OK, sounds reasonable and might even be 1/2 as useful as old-fashioned
Objective-C / SmallTalk dynamic method invocation, but the kicker is the
example.
You look up the stateless session bean via JNDI. And
