Ahhhh...I'm guessing I didn't install JBoss with the EJB 3.0 profile, since I installed it by just unzipping the zip distribution rather than running the installer. What exactly determines whether JBoss starts up in an EJB 3.0-happy fashion?
right. use the jboss installer and remember to select the EJB3 profile.
Reinstalled with the installer this time, made sure I used the EJB 3.0 profile, and now it works OK. Must follow directions harder, I guess. [blush]
I encountered this beast today as i was trying to get some hand on SEAM after i heard lots of good reviews. As mentioned in one of the posts here I 're-installed JBoss', using JEMS installer, using ption 'ejb3' on installer menu, previously i opted for option 'ALL'.
And when i deployed example of 'booking' from SEAM it deployed sucessfully.
Prior to this i had the above mentioned errors and i tried changing ejb-jar file as suggested above, but all those things didn't work.
So if you reinstall JBoss using ejb3 option than it will be fine, it is also metoined on JBoss app server download page specifically.
I hope this helps, sometimes trying to become smart can bite you badly, as i encountered :)
Let me see if I understand: "all" for some reason does not include "ejb3"? Can someone explain this? Why is EJB3 not part of all?
Because ejb3 is not part of J2EE 1.4.