Sudarson Roy Pratihar wrote: > > The entire application runs on the basis that at the startup of > the server, administrator of the application will input those > things and that will be used in timer thread to access some > resources. So currently application structure depends on that. >
Nobody can stop you from giving your server-side Java a Swing interface (I'm sure you'll figure out the problems), but what you're doing is almost never a good idea. I understand that there might be some very unusual situation where it's required, but just so people don't go thinking it's a generally good idea (I can hear the newbies thinking "hey that's cool"), here are a couple obvious drawbacks: One big problem is that no competent server side Java programmer expects to find Swing code laying around. So if anyone but you ever has to maintain the code, you're going to confuse the heck out of them. And that means lost $$$. And any good admin is going to expect to be able to reboot your server in an emergency without having to sit and wait for some Swing dialog to pop up. And that means downtime and thus lost $$$. And the container is going to expect listeners to run quickly, so it's probably single-threading the callbacks, so you're probably stalling the entire container. And it offends any good Java programmer's aesthetic sense. No lost $$$ on that one, but you do want to be able to hold your head up among your peers, right? I don't know your exact situation, so who knows, maybe yours is the one-in-a-million problem that really does require Swing in your servlets. But anybody else out there: just say no. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
