> I'm getting a number of non-Jetty exceptions and ignoring them.
What exceptions are you getting?
> 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 ?
Like I said before, I have not really looked at the changes Marc commited in
much detail yet. I can't really say more than that at the moment.
> 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.
I did not spend much time integrating the plugins/jetty module. All I did
was get it to compile under the new system, and package up the
jetty-plugin.jar.
I think that if we could turn that into a jetty-plugin.sar, which had had
all of the support files (static config and whatever) that would be the way
to go.
That said, I don't really know (at the moment) what needs to be done to make
that happen.
=|
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
