I was troubleshooting a problem due to a faulty jboss.xml file (missing one
Stateful configuration in it) and I believe that the configuration file
jboss.xml for jboss is overkill.
The fact is that 95% users will *not* need to supply a jboss.xml describing
in gory detail the kind of cache and pool they will need, the type of
"ContainerInvoker" they need and the min and max sizes.
In fact the "default files" already in do provide this and you don't need
the file almost always. Only if you are an advanced user or sys-admin and
you want to configure the container details differently for one particular
bean then supply your own jboss.xml file.
If not, DON'T BOTHER. Don't EVEN supply a jboss.xml.
I think this will *greatly* simplify the "user guide" as we only need to
cover the jboss.xml in the following cases:
1- using 1.2.2 (invoker conf, although it could be automated)
2- advanced non-default cache
3- changing pool sizes
4- changing plugins (own TxManager etc etc)
And that is all.
This file can be tricky (one thing breaks, everything breaks) and I believe
it will take care of 90% of our "bean not bound" problem reports that we
have been seeing and are hard to troubleshoot.
We probably will fix the doco accordingly...
thanks
marc
________________________
Marc Fleury
Chief Technology Officer
Telkel, Inc.
________________________
