On 2001-05-15 at 12:12 +0200, [EMAIL PROTECTED] wrote:
> > Is it a bug? Shouldn't jBoss report that it could not
> > find jboss.xml during deployment?
>
> No, if no jboss.xml found, it uses the standardjboss.xml in the
> configuration dir. Same applies to the jaws.xml (it uses standardjaws.xml
> instead). Only ejb-jar.xml is required.
This sort of thing, although not this particular one, bit me before
between jboss.xml and jboss-auto.xml. It might be a good idea to put the
start-up sequence and the complete list of files and their alternatives
into a single place in the documentation under a heading like "Starting
Sequence." Many of these issues are documented, but are scattered all
over the documentation.
I think it might be prudent for jBoss at least to make a log entry,
something like "jboss.xml not found; using standardjboss.xml default
instead." This would make it a lot easier to figure out what is going on.
While on the subject of documentation, it would be really handy to have a
keyword index of the on-line HTML manual. A utility such as ht://Dig --
http://www.htdig.org/ -- could be used to generate this off-the-shelf.
For example, if someone wants to know how to configure jBoss for Postgres,
they need to look under "Minerva." Having a keyword index would allow
them to look under "Postgres" and produce fruitful results.
-- Mike
P.S. Personal note to Manu Srivastava, who started this thread (his words
are those marked with ">>"): Are you the same person as Manoj Srivastava?
If so, hello!
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
