As a Bean Provider, your deliverable is an ejb-jar file with your beans/interfaces/deployment-descriptor. This ejb-jar file can possibly be mixed with other ejb-jar's from the application-assembler, to better fit a domain, based on the requirements. And I guess that's why EJB spec does not recommend putting classes in packages.
I read some where that defining beans in packages, will be a security hole. If it is the case, is there any body who knows why and how?
Best Regards,<br />Pourang Emami
I miss the old days when I would think up a sinister scheme for world domination and you would show a little emotional support. So just look at this tiny ad:
a bit of art, as a gift, the permaculture playing cards