Given that jboss.xml is not part of the J2EE spec. and that JBoss is a spec. compliant application server, you should be able to deploy an ear which has no jboss.xml in it. JBoss.xml just contains vendor-specific configuration which is always optional. [ July 21, 2005: Message edited by: Paul Sturrock ]
The J2EE 2 spec never intended that applications be deployable without vendor specific deployment options. That you may be able to do this in many cases is entirely coincidental. It might even appear to be working, but if you are doing anything with security or any number of other un/under-defined aspects of J2EE apps, your deployment won't make sense.
The reason this is working in this case is most likely that the ejb-links are fully resolving the bean and there is no need for the explicit JNDI name mappingd in the jboss.xml.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop