Jason,
I have checked out a fresh jboss-all tree, built it successfully and
tried running it.
I'm getting a number of non-Jetty exceptions and ignoring them.
On the Jetty side - a couple of questions.
1.
It looks like you/someone have made Jetty into a 'plugin' - thanks. I
was expecting this to be the .SAR archive that I keep seeing mentioned
here and there.... but I've grepped all over the place and can't find
any mention of them - what's the score here ?
2.
The Jetty plugin deliverable does not appear to own a runtime
distribution tree, as such. This is the cause of all the Exceptions
generated by the default jetty.xml config file, and the reason that you
had to empty it. Assuming that the Jetty plugin needs some sort of tree
of resources available to it at runtime, has any thought been given to
how this might be distributed, since it is not simply a matter of
shipping jars about, but whole directory hierarchies.. I was hoping that
I could put this hierarchy into a .SAR, which would be distributed,
unpacked and then run. Jetty would be able to locate all the files it
needed within a tree relative to the top of the unpacked .SAR.
Thanks for the help,
Jules
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
