Actually it would probably be more useful in Remote mode. Because the only time it is called that way is when the server is being shutdown, and you want to close the database, but you don't want any clients to have a lock, and therefore corrupt the database when you close the database. In Local mode isn't any need for locking of any kind. Mark
Hi, I believe you shouldn't rely on the finalize method. At least thats what the spec says. Using a shutdown hook would also be possible, but again, it should be implemented with very few statements and probably wouldn't be appropriate, if your server takes a long time to shut down. I would advise you to do like Mark says, add a gentle form for shutdown mechanism. You can do that either in a GUI (server) component or simply add a primitive prompt, in which users can enter "stop" or "exit".
MyCerts: SCJP 1.2, SCJP 1.5, SCJD, SCWCD 1.3, SCBCD 1.3, SCDJWS 1.4, SCEA, IBM 253
MyBooks: IBM WebSphere Application Server V7.0 Web Services Guide
posted 18 years ago
If iam going to give a gui for server shutdown it will be total of 4 windows - server - 1 dos prompt , 1 gui client - 1 dos prompt , 1 gui. thats why i didnt give gui for server. if i have to give gui, can i use Activation API and reduce the dos prompt. otherwise so many windows has to be kept open. i dont like that. why do u guys think abt it ?