[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ]
Jozef Marko reassigned DROOLS-4042:
-----------------------------------
Assignee: Michael Anstis (was: Jozef Marko)
> [DMN Designer] Add support for importing and consuming PMML models 7.5
> ----------------------------------------------------------------------
>
> Key: DROOLS-4042
> URL: https://issues.jboss.org/browse/DROOLS-4042
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.24.0.Final
>
>
> We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor.
> h2. Requirement
> - As user, via included models tab, remove included pmml model, even if used somewhere
> - As user, via included models tab, rename included pmml model, even if used somewhere
> - As user, via included models tab, include multiple pmml models
> - As user, via included models tab, include multiple pmml models at the same time eternal dmn
> - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished
> - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values
> - As user, via included models tab, no restriction for included pmml model name
> - As user, via new test scenarios, test dmn model that uses pmml inside
> - As user, via kie-server, query kie container that has dmn model with pmml
> - As user, via included models tab, I want to have just unique aliases of imported models
> h2. UX design
> - Selectbox in place of Document and Model selection
> h2. Documentation
> - Mention what pmml model can be imported into dmn
> - Mention where it can be used
> - Mention if something more needed to dpeloy such project on kie server
> h2. Acceptance test
> - Include two pmml models
> - In dmn, select one in function grid
> - Change the selected one to second
> - Finish the dmn model
> - build deploy on kie-server
> - Interact with kie container via rest
> - Create new test scenario for created dmn model
> - In included models tab, try to include one pmml and one dmn with same alias, it shouldn't be possible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ]
Jozef Marko reopened DROOLS-4042:
---------------------------------
> [DMN Designer] Add support for importing and consuming PMML models 7.5
> ----------------------------------------------------------------------
>
> Key: DROOLS-4042
> URL: https://issues.jboss.org/browse/DROOLS-4042
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.24.0.Final
>
>
> We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor.
> h2. Requirement
> - As user, via included models tab, remove included pmml model, even if used somewhere
> - As user, via included models tab, rename included pmml model, even if used somewhere
> - As user, via included models tab, include multiple pmml models
> - As user, via included models tab, include multiple pmml models at the same time eternal dmn
> - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished
> - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values
> - As user, via included models tab, no restriction for included pmml model name
> - As user, via new test scenarios, test dmn model that uses pmml inside
> - As user, via kie-server, query kie container that has dmn model with pmml
> - As user, via included models tab, I want to have just unique aliases of imported models
> h2. UX design
> - Selectbox in place of Document and Model selection
> h2. Documentation
> - Mention what pmml model can be imported into dmn
> - Mention where it can be used
> - Mention if something more needed to dpeloy such project on kie server
> h2. Acceptance test
> - Include two pmml models
> - In dmn, select one in function grid
> - Change the selected one to second
> - Finish the dmn model
> - build deploy on kie-server
> - Interact with kie container via rest
> - Create new test scenario for created dmn model
> - In included models tab, try to include one pmml and one dmn with same alias, it shouldn't be possible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ]
Jozef Marko reassigned DROOLS-4042:
-----------------------------------
Assignee: Jozef Marko (was: Michael Anstis)
> [DMN Designer] Add support for importing and consuming PMML models 7.5
> ----------------------------------------------------------------------
>
> Key: DROOLS-4042
> URL: https://issues.jboss.org/browse/DROOLS-4042
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Jozef Marko
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.24.0.Final
>
>
> We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor.
> h2. Requirement
> - As user, via included models tab, remove included pmml model, even if used somewhere
> - As user, via included models tab, rename included pmml model, even if used somewhere
> - As user, via included models tab, include multiple pmml models
> - As user, via included models tab, include multiple pmml models at the same time eternal dmn
> - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished
> - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values
> - As user, via included models tab, no restriction for included pmml model name
> - As user, via new test scenarios, test dmn model that uses pmml inside
> - As user, via kie-server, query kie container that has dmn model with pmml
> - As user, via included models tab, I want to have just unique aliases of imported models
> h2. UX design
> - Selectbox in place of Document and Model selection
> h2. Documentation
> - Mention what pmml model can be imported into dmn
> - Mention where it can be used
> - Mention if something more needed to dpeloy such project on kie server
> h2. Acceptance test
> - Include two pmml models
> - In dmn, select one in function grid
> - Change the selected one to second
> - Finish the dmn model
> - build deploy on kie-server
> - Interact with kie container via rest
> - Create new test scenario for created dmn model
> - In included models tab, try to include one pmml and one dmn with same alias, it shouldn't be possible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-11983) Unify line-endings of bat scripts (regression against WF15)
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11983?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-11983:
--------------------------------------
You are correct the files themselves need to be updated. You'd have to apply this change then do something like {{find feature-pack/src -name "*.bat" | xargs git reset-file}}. Every user would have to do this though or more importantly whoever does the release.
That said there is also WFGP-144 which fixes this issue with the changes on the [WFCORE-4502|https://issues.jboss.org/browse/WFCORE-4502?focusedCommentId=...] comment.
> Unify line-endings of bat scripts (regression against WF15)
> -----------------------------------------------------------
>
> Key: WFLY-11983
> URL: https://issues.jboss.org/browse/WFLY-11983
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 16.0.0.Final
> Reporter: Marek Kopecky
> Assignee: Radoslav Husar
> Priority: Major
>
> Line-endings of bat scripts should be unified. This is regression against WF15.
> Some files in WF16 uses CRLF, another LF only. We need to clarify the recommended line ending and use this line ending in all Windows scripts.
> WF16:
> {noformat}
> $ find | grep bat$ | xargs file
> ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jboss-cli.bat: DOS batch file, ASCII text
> ./elytron-tool.bat: DOS batch file, ASCII text
> ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.conf.bat: ASCII text, with CRLF line terminators
> ./common.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jdr.bat: DOS batch file, ASCII text
> ./jconsole.bat: DOS batch file, ASCII text
> ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.conf.bat: ASCII text, with CRLF line terminators
> ./standalone.conf.bat: ASCII text, with CRLF line terminators
> ./add-user.bat: DOS batch file, ASCII text
> $
> {noformat}
> WF15:
> {noformat}
> $ find | grep bat$ | xargs file
> ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jboss-cli.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./elytron-tool.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.conf.bat: ASCII text, with CRLF line terminators
> ./common.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jdr.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jconsole.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.conf.bat: ASCII text, with CRLF line terminators
> ./standalone.conf.bat: ASCII text, with CRLF line terminators
> ./add-user.bat: DOS batch file, ASCII text, with CRLF line terminators
> $
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11983) Unify line-endings of bat scripts (regression against WF15)
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11983?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11983:
-----------------------------------------
I merged https://github.com/wildfly/wildfly/pull/12336 but I believe the files themselves need to be updated so I'm not resolving this. If I'm wrong and this can be resolved, go for it!
> Unify line-endings of bat scripts (regression against WF15)
> -----------------------------------------------------------
>
> Key: WFLY-11983
> URL: https://issues.jboss.org/browse/WFLY-11983
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 16.0.0.Final
> Reporter: Marek Kopecky
> Assignee: Radoslav Husar
> Priority: Major
>
> Line-endings of bat scripts should be unified. This is regression against WF15.
> Some files in WF16 uses CRLF, another LF only. We need to clarify the recommended line ending and use this line ending in all Windows scripts.
> WF16:
> {noformat}
> $ find | grep bat$ | xargs file
> ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jboss-cli.bat: DOS batch file, ASCII text
> ./elytron-tool.bat: DOS batch file, ASCII text
> ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.conf.bat: ASCII text, with CRLF line terminators
> ./common.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jdr.bat: DOS batch file, ASCII text
> ./jconsole.bat: DOS batch file, ASCII text
> ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.conf.bat: ASCII text, with CRLF line terminators
> ./standalone.conf.bat: ASCII text, with CRLF line terminators
> ./add-user.bat: DOS batch file, ASCII text
> $
> {noformat}
> WF15:
> {noformat}
> $ find | grep bat$ | xargs file
> ./wsprovide.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jboss-cli.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./elytron-tool.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./wsconsume.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./standalone.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./vault.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./domain.conf.bat: ASCII text, with CRLF line terminators
> ./common.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jdr.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./jconsole.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.bat: DOS batch file, ASCII text, with CRLF line terminators
> ./appclient.conf.bat: ASCII text, with CRLF line terminators
> ./standalone.conf.bat: ASCII text, with CRLF line terminators
> ./add-user.bat: DOS batch file, ASCII text, with CRLF line terminators
> $
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (LOGMGR-255) PeriodicRotatingFileHandler doesn't rotate log content when using Compression
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-255?page=com.atlassian.jira.plugin... ]
James Perkins commented on LOGMGR-255:
--------------------------------------
What version of WildFly or JBoss EAP are you seeing this one? There was LOGMGR-246 which seems somewhat similar.
> PeriodicRotatingFileHandler doesn't rotate log content when using Compression
> -----------------------------------------------------------------------------
>
> Key: LOGMGR-255
> URL: https://issues.jboss.org/browse/LOGMGR-255
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: Alain Baxter
> Priority: Major
>
> When configuring a PeriodicRotatingFileHandler where the suffix ends with .zip or .gz, as such:
> {noformat}
> <periodic-rotating-file-handler name="FILE" autoflush="true">
> <formatter>
> <named-formatter name="PATTERN"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> <suffix value=".yyyy-MM-dd-HH.gz"/>
> <append value="true"/>
> </periodic-rotating-file-handler>
> {noformat}
> This is supposed to compressed the rotated logs to save space. See https://issues.jboss.org/browse/LOGMGR-30
> What I'm seeing is that the rotation log file is successfully created and compressed at the periodic interval, however the log file content is not removed.
> This means that the log file itself continues to grow instead of rotating log content, and each rotation log contains the content from all the previous, so their size gets larger and larger:
> {noformat}
> -rw-r--r--. 1 jboss jboss 1779799 Jun 18 21:03 server.log
> -rw-r--r--. 1 jboss jboss 21831 Jun 18 19:00 server.log.2019-06-18-18.gz
> -rw-r--r--. 1 jboss jboss 55168 Jun 18 20:00 server.log.2019-06-18-19.gz
> -rw-r--r--. 1 jboss jboss 88021 Jun 18 21:00 server.log.2019-06-18-20.gz
> {noformat}
> *NOTE:* This issue would exist for SizeRotatingFileHandler and PeriodicSizeRotatingFileHandler
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (LOGMGR-255) PeriodicRotatingFileHandler doesn't rotate log content when using Compression
by Alain Baxter (Jira)
[ https://issues.jboss.org/browse/LOGMGR-255?page=com.atlassian.jira.plugin... ]
Alain Baxter updated LOGMGR-255:
--------------------------------
Description:
When configuring a PeriodicRotatingFileHandler where the suffix ends with .zip or .gz, as such:
{noformat}
<periodic-rotating-file-handler name="FILE" autoflush="true">
<formatter>
<named-formatter name="PATTERN"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="server.log"/>
<suffix value=".yyyy-MM-dd-HH.gz"/>
<append value="true"/>
</periodic-rotating-file-handler>
{noformat}
This is supposed to compressed the rotated logs to save space. See https://issues.jboss.org/browse/LOGMGR-30
What I'm seeing is that the rotation log file is successfully created and compressed at the periodic interval, however the log file content is not removed.
This means that the log file itself continues to grow instead of rotating log content, and each rotation log contains the content from all the previous, so their size gets larger and larger:
{noformat}
-rw-r--r--. 1 jboss jboss 1779799 Jun 18 21:03 server.log
-rw-r--r--. 1 jboss jboss 21831 Jun 18 19:00 server.log.2019-06-18-18.gz
-rw-r--r--. 1 jboss jboss 55168 Jun 18 20:00 server.log.2019-06-18-19.gz
-rw-r--r--. 1 jboss jboss 88021 Jun 18 21:00 server.log.2019-06-18-20.gz
{noformat}
*NOTE:* This issue would exist for SizeRotatingFileHandler and PeriodicSizeRotatingFileHandler
was:
When configuring a PeriodicRotatingFileHandler where the suffix ends with .zip or .gz, as such:
{noformat}
<periodic-rotating-file-handler name="FILE" autoflush="true">
<formatter>
<named-formatter name="PATTERN"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="server.log"/>
<suffix value=".yyyy-MM-dd.gz"/>
<append value="true"/>
</periodic-rotating-file-handler>
{noformat}
This is supposed to compressed the rotated logs to save space. See https://issues.jboss.org/browse/LOGMGR-30
What I'm seeing is that the rotation log file is successfully created and compressed at the periodic interval, however the log file content is not removed.
This means that the log file itself continues to grow instead of rotating log content, and each rotation log contains the content from all the previous, so their size gets larger and larger:
{noformat}
-rw-r--r--. 1 jboss jboss 1779799 Jun 18 21:03 server.log
-rw-r--r--. 1 jboss jboss 21831 Jun 18 19:00 server.log.2019-06-18-18.gz
-rw-r--r--. 1 jboss jboss 55168 Jun 18 20:00 server.log.2019-06-18-19.gz
-rw-r--r--. 1 jboss jboss 88021 Jun 18 21:00 server.log.2019-06-18-20.gz
{noformat}
*NOTE:* This issue would exist for SizeRotatingFileHandler and PeriodicSizeRotatingFileHandler
> PeriodicRotatingFileHandler doesn't rotate log content when using Compression
> -----------------------------------------------------------------------------
>
> Key: LOGMGR-255
> URL: https://issues.jboss.org/browse/LOGMGR-255
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: Alain Baxter
> Priority: Major
>
> When configuring a PeriodicRotatingFileHandler where the suffix ends with .zip or .gz, as such:
> {noformat}
> <periodic-rotating-file-handler name="FILE" autoflush="true">
> <formatter>
> <named-formatter name="PATTERN"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> <suffix value=".yyyy-MM-dd-HH.gz"/>
> <append value="true"/>
> </periodic-rotating-file-handler>
> {noformat}
> This is supposed to compressed the rotated logs to save space. See https://issues.jboss.org/browse/LOGMGR-30
> What I'm seeing is that the rotation log file is successfully created and compressed at the periodic interval, however the log file content is not removed.
> This means that the log file itself continues to grow instead of rotating log content, and each rotation log contains the content from all the previous, so their size gets larger and larger:
> {noformat}
> -rw-r--r--. 1 jboss jboss 1779799 Jun 18 21:03 server.log
> -rw-r--r--. 1 jboss jboss 21831 Jun 18 19:00 server.log.2019-06-18-18.gz
> -rw-r--r--. 1 jboss jboss 55168 Jun 18 20:00 server.log.2019-06-18-19.gz
> -rw-r--r--. 1 jboss jboss 88021 Jun 18 21:00 server.log.2019-06-18-20.gz
> {noformat}
> *NOTE:* This issue would exist for SizeRotatingFileHandler and PeriodicSizeRotatingFileHandler
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (LOGMGR-255) PeriodicRotatingFileHandler doesn't rotate log content when using Compression
by Alain Baxter (Jira)
Alain Baxter created LOGMGR-255:
-----------------------------------
Summary: PeriodicRotatingFileHandler doesn't rotate log content when using Compression
Key: LOGMGR-255
URL: https://issues.jboss.org/browse/LOGMGR-255
Project: JBoss Log Manager
Issue Type: Bug
Reporter: Alain Baxter
When configuring a PeriodicRotatingFileHandler where the suffix ends with .zip or .gz, as such:
{noformat}
<periodic-rotating-file-handler name="FILE" autoflush="true">
<formatter>
<named-formatter name="PATTERN"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="server.log"/>
<suffix value=".yyyy-MM-dd.gz"/>
<append value="true"/>
</periodic-rotating-file-handler>
{noformat}
This is supposed to compressed the rotated logs to save space. See https://issues.jboss.org/browse/LOGMGR-30
What I'm seeing is that the rotation log file is successfully created and compressed at the periodic interval, however the log file content is not removed.
This means that the log file itself continues to grow instead of rotating log content, and each rotation log contains the content from all the previous, so their size gets larger and larger:
{noformat}
-rw-r--r--. 1 jboss jboss 1779799 Jun 18 21:03 server.log
-rw-r--r--. 1 jboss jboss 21831 Jun 18 19:00 server.log.2019-06-18-18.gz
-rw-r--r--. 1 jboss jboss 55168 Jun 18 20:00 server.log.2019-06-18-19.gz
-rw-r--r--. 1 jboss jboss 88021 Jun 18 21:00 server.log.2019-06-18-20.gz
{noformat}
*NOTE:* This issue would exist for SizeRotatingFileHandler and PeriodicSizeRotatingFileHandler
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4287) CLI should show not show default value once value one of "alternatives" attributes was set
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4287?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-4287:
------------------------------------------
Sorry, [~michpetrov], I have no idea. I suggest asking on the wildfly-developers stream in zulip with a link to some details of the test problem.
> CLI should show not show default value once value one of "alternatives" attributes was set
> ------------------------------------------------------------------------------------------
>
> Key: WFCORE-4287
> URL: https://issues.jboss.org/browse/WFCORE-4287
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Management
> Reporter: Miroslav Novak
> Priority: Major
>
> If there are attributes which are "alternatives" and both of them are undefined then default value of one of the attributes is shown in CLI, for example:
> {code}
> [standalone@localhost:9990 /] ls /subsystem=messaging-activemq/server=default
> elytron-domain=undefined
> security-domain=other
> {code}
> at this moment when I try set elytron-domain:
> {code}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default:write-attribute(name=elytron-domain,value=ApplicationRealm)
> {code}
> then it shows:
> {code}
> [standalone@localhost:9990 /] ls /subsystem=messaging-activemq/server=default
> elytron-domain=ApplicationDomain
> security-domain=other
> {code}
> Can this be changed that it would show {{security-domain=undefined}} so it would not show default values anymore? Current display is confusing as it's not clear what is used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4531) Eliminate WF naming workaround
by Richard Opalka (Jira)
Richard Opalka created WFCORE-4531:
--------------------------------------
Summary: Eliminate WF naming workaround
Key: WFCORE-4531
URL: https://issues.jboss.org/browse/WFCORE-4531
Project: WildFly Core
Issue Type: Enhancement
Components: Modules
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: 9.0.2.Final
Now that WildFly Naming client have been upgraded in WildFly code base we can eliminate
module workaround we introduced in WFLY-10394
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months