Re: [Jetty-support] Command-line/http admin and hot-deployment tool

[Jan B. <ja...@mo...>]

Steve,

If I were you, I'd go straight to 6.1.1. There were issues in 6.0.2
that have been solved by the 6.1.x series, and 6.1.1 is now final
and definitely to be preferred.

Regarding an AdminServlet like tool, go for it! I'd say that jetty
could do with a web-console like tool, but something that shows the
status of webapps, and stops and starts them would be a good start.

As for the hot deployment scanner, what did you have in mind there?
The current hot deployment scanner can be contacted (at least should
be) via jmx. Wouldn't a remote deployer be more useful than a 
remote scanner?

cheers
Jan


Steve Sobol wrote:
> I just upgraded from 5.1.2 to 6.0.2.
> 
> I haven't explored everything new in 6, but there are plenty of things I
> like about it. But the Admin Servlet has gone away.
> 
> I have an interim solution -- tunnel localhost:8082 on my laptop to
> localhost:8082 on my server and use the MX4j HttpAdaptor and a web
> browser. But that solution is clunky. All I generally need to do,
> admin-wise, is to restart Web app contexts. Even the old Admin Servlet was
> more than I needed.
> 
> So, I'm creating my own solution. Initially it will just stop and start
> webapps, but if there's any interest in expanding its capabilities, I
> might do so later. I'm also considering writing a hot-deployment scanner
> that will use JMX.
> 
> Basically, my solution will require JMX and RMI to be running, will
> enumerate all of the contexts currently available and will allow you to
> start or stop them by display name or virtual hostname.
> 
> Any thoughts? Would anyone besides me be interested in this? I'll write
> it, polish it up and donate it to the community if y'all want it. :>
> 
> 
>