Stian Soiland-Reyes created TAVERNA-923:
-------------------------------------------
Summary: Avoid deprecated RMISecurityManager?
Key: TAVERNA-923
URL: https://issues.apache.org/jira/browse/TAVERNA-923
Project: Apache Taverna
Issue Type: Bug
Components: Taverna Server
Reporter: Stian Soiland-Reyes
In Java 8 the
[RMISecurityManager|https://docs.oracle.com/javase/8/docs/api/java/rmi/RMISecurityManager.html]
has been deprecated, saying we should generally use the superclass
{{SecurityManager}} instead.
In Taverna Server we use RMISecurityManager [in
TavernaRunManager|https://github.com/apache/incubator-taverna-server/blob/67c67cfbd54c2ec86dff960b5e8670e76e33168a/taverna-server-worker/src/main/java/org/taverna/server/localworker/impl/TavernaRunManager.java#L187]
and [in
AbstractRemoteRunFactory|https://github.com/apache/incubator-taverna-server/blob/67c67cfbd54c2ec86dff960b5e8670e76e33168a/taverna-server-webapp/src/main/java/org/taverna/server/master/localworker/AbstractRemoteRunFactory.java#L279]
Donal - do you think this would work well with just SecurityManager in these
places? Why is RMISecurityManager deprecated?
Note: We use RMI for internal communication between Taverna Server and the
individual worker process (which runs executeworkflow) - which may run as
different Unix workers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
