The Swing console in WAS could only be used as an example how rich clients should not be done. The integrated console in WSAD was significantly better but was not providing all functions.
But if you start referring WAS, there the admin console is started on a different http port, can be forced to http in a very simple way. It can run i.e. on the cell component independently from server instances and can manage all servers in a distributed / clustered environment. All things I miss in G. But I'm not complaining, just listing options. What should be done first and how can I help? Heinz On 9/20/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
If IBM's experience is any indicator the Swing Management Console disappeared in WebSphere Version 5 because customers didn't like a heavyweight thing to carry around. The overwhelming response from users was give us a web console. FWIW. On Sep 17, 2006, at 4:42 PM, Jason Dillon wrote: > Anyone have any thoughts on using Swing for the console... instead > of a webapp (which are kinda evil IMO)... and then using webstart > to serve it? Maybe using Netbeans (or that license not ASL > friendly)? I've done some work with NB before at it would be very > easy to create a rich user experience... and its easy to drop in > new modules to support different aspects of administration and > monitoring. > > I dunno.. just a thought... > > --jason > > Matt Hogstrom [EMAIL PROTECTED]
