Closed brianoliver closed 9 years ago
@brianoliver said: Instead of multiple methods we should:
This will allow any type of application to have customized close options. This will be especially useful for VirtualizedPlatforms which have a range of shutdown/close strategies.
Introduce JavaApplication.CloseOption that will allow specific processing for a JavaApplication. eg: calling either System.exit() or Runtime.halt()
Introduce a CoherenceMember.CloseOption (extending the JavaApplication.CloseOption) that will allow CacheFactory.shutdown() in addition to System.exit() or Runtime.halt() approaches.
@brianoliver said: Introduced ApplicationClosingBehavior Option and the new Application.close(Option...) method.
This issue was imported from JIRA ORACLETOOLS-194
Reported by @brianoliver
Marked as fixed by @brianoliver on Wednesday, November 19th 2014, 11:30:36 pm
There are several ways we can close a Java-based Application.
Attempting to close/destroy/exit the process using something like Process.close()
Submitting a RemoteRunnable that does System.exit(exitCode), which should be the same as #1
Submitting a RemoteRunnable that performs a System.halt(exitCode).
We currently do #1, but we should also offer to do #2 and #3 as options with an overloaded JavaApplication.close(approach, exitCode).
This is somewhat related to the closed issue #7