I have a jboss.xml for a single EJB. It contains 66 lines of
"container configurations" for 4 configurations, only 1 of which is used.
This compares to 5 lines for the EJB itself. I'm not sold on the utility
of these container configurations.
I suppose it is easier to deploy tons of beans in one JAR if you
can name and reuse your configurations, but even then I'm skeptical that
there won't be enough minor differences (pool size, etc) that this will
not help all that much. It's the sort of thing we could achieve with a
good GUI design anyway (drag and drop one bean onto another to apply all
the same settings, or something). And personally, I've never deployed
more than one bean in a JAR since I want to be able to update them all
independently.
Do others feel differently? Is this a valuable feature? Can we
at least agree (in principle) to not write out container configurations
that are not used by the beans in the JAR?
It also rubs me the wrong way that all these JARs will have a
configuration called "Default Stateless Session Bean" but the settings may
be totally different in each - but I haven't thought of a solution to that
yet.
Aaron
