[
https://issues.jboss.org/browse/WFLY-10242?page=com.atlassian.jira.plugin...
]
R Searls commented on WFLY-10242:
---------------------------------
I would like to understand the history of -secmgr. I've looked through
prior versions of wfly. I see that no mention of -Djava.security.manager or
-secmgr is made in the scripts until version 10.0.0.Final. It is in this version
that JAVA_OPTS is checked for these options.
In versions prior to 10.0.0.Final were users required to make a conscious decision
to specify -Djava.security.manager to get the behavior they wanted? Was there
wfly user documentation describing declaring this in JAVA_OPTS?
Is there wfly user documentation describing the switch from -Djava.security.manager
to -secmgr usage?
Is setting -secmgr in JAVA_OPTS an effort to maintain backward compatibility (e.g.
-Djava.security.manager was set there; -secmgr is replacing it so should be set there as
well)?
Unify secmgr JAVA_OPTS behaviour in WF scripts
----------------------------------------------
Key: WFLY-10242
URL:
https://issues.jboss.org/browse/WFLY-10242
Project: WildFly
Issue Type: Bug
Components: Scripts
Reporter: Marek Kopecký
Assignee: Kabir Khan
Unify secmgr JAVA_OPTS behaviour in WF scripts.
standalone&&domain&&appclient scripts doesn't allow to use secmgr by
JAVA_OPTS definition. wsconsume&&wsprovide scripts allow that (see
[
this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...]
and
[
this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...])
All scripts should be unified.
cc: [~asoldano], [~jamezp], [~jbliznak], [~msvehla]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)