[JBoss JIRA] (DROOLS-2998) [DMN Designer] Data-type restrictions
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2998?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2998:
-----------------------------------
Attachment: EnumerationDateTime.png
> [DMN Designer] Data-type restrictions
> -------------------------------------
>
> Key: DROOLS-2998
> URL: https://issues.jboss.org/browse/DROOLS-2998
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Attachments: UnaryTest1.png, UnaryTest2.png, UnaryTest3.png, UnaryTest4.png
>
>
> The data-type dialog needs to support restrictions on the data-type definition; such as enumeration, range, expression etc. The development work for the Data Type dialog to support said restrictions also needs to be re-used by the DMN Decision Table for {{InputClause}} and {{OutputClause}} columns' {{UnaryTests}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2998) [DMN Designer] Data-type restrictions
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2998?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2998:
-----------------------------------
Attachment: (was: EnumerationDateTime.png)
> [DMN Designer] Data-type restrictions
> -------------------------------------
>
> Key: DROOLS-2998
> URL: https://issues.jboss.org/browse/DROOLS-2998
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Attachments: UnaryTest1.png, UnaryTest2.png, UnaryTest3.png, UnaryTest4.png
>
>
> The data-type dialog needs to support restrictions on the data-type definition; such as enumeration, range, expression etc. The development work for the Data Type dialog to support said restrictions also needs to be re-used by the DMN Decision Table for {{InputClause}} and {{OutputClause}} columns' {{UnaryTests}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2998) [DMN Designer] Data-type restrictions
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2998?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2998:
----------------------------------------
Images illustrating {{UnaryTests}} restrictions attached.
> [DMN Designer] Data-type restrictions
> -------------------------------------
>
> Key: DROOLS-2998
> URL: https://issues.jboss.org/browse/DROOLS-2998
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Attachments: UnaryTest1.png, UnaryTest2.png, UnaryTest3.png, UnaryTest4.png
>
>
> The data-type dialog needs to support restrictions on the data-type definition; such as enumeration, range, expression etc. The development work for the Data Type dialog to support said restrictions also needs to be re-used by the DMN Decision Table for {{InputClause}} and {{OutputClause}} columns' {{UnaryTests}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2998) [DMN Designer] Data-type restrictions
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2998?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2998:
-----------------------------------
Attachment: UnaryTest1.png
UnaryTest2.png
UnaryTest3.png
UnaryTest4.png
> [DMN Designer] Data-type restrictions
> -------------------------------------
>
> Key: DROOLS-2998
> URL: https://issues.jboss.org/browse/DROOLS-2998
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Attachments: UnaryTest1.png, UnaryTest2.png, UnaryTest3.png, UnaryTest4.png
>
>
> The data-type dialog needs to support restrictions on the data-type definition; such as enumeration, range, expression etc. The development work for the Data Type dialog to support said restrictions also needs to be re-used by the DMN Decision Table for {{InputClause}} and {{OutputClause}} columns' {{UnaryTests}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2998) [DMN Designer] Data-type restrictions
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2998:
--------------------------------------
Summary: [DMN Designer] Data-type restrictions
Key: DROOLS-2998
URL: https://issues.jboss.org/browse/DROOLS-2998
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.11.0.Final
Reporter: Michael Anstis
Assignee: Guilherme Carreiro
The data-type dialog needs to support restrictions on the data-type definition; such as enumeration, range, expression etc. The development work for the Data Type dialog to support said restrictions also needs to be re-used by the DMN Decision Table for {{InputClause}} and {{OutputClause}} columns' {{UnaryTests}}.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11042) mod_cluster custom load metrics fail to load
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-11042:
-------------------------------------
Summary: mod_cluster custom load metrics fail to load
Key: WFLY-11042
URL: https://issues.jboss.org/browse/WFLY-11042
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 14.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Critical
Fix For: 15.0.0.Alpha1
This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
{code}
OPVDX001: Validation error in standalone-ha.xml --------------------------------
|
| 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
| 449: <dynamic-load-provider>
| 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
| ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
| element
|
| Attributes allowed here are: capacity, class, module, weight
|
| 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
| 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
| 453: </custom-load-metric>
|
| 'module' is allowed on elements:
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
| - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
| - server > extensions > extension
| - server > vault
| - server > management > security-realms > security-realm > plug-ins > plug-in
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
| - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
| (and 26 more)
|
| The primary underlying error message was:
| > ParseError at [row,col]:[450,21]
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) mod_cluster custom load metrics fail to load
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11033:
----------------------------------
Summary: mod_cluster custom load metrics fail to load (was: "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be)
> mod_cluster custom load metrics fail to load
> --------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 15.0.0.Alpha1
>
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4119) Add exclusions for org.picketbox
by Yeray Borges (JIRA)
Yeray Borges created WFCORE-4119:
------------------------------------
Summary: Add exclusions for org.picketbox
Key: WFCORE-4119
URL: https://issues.jboss.org/browse/WFCORE-4119
Project: WildFly Core
Issue Type: Task
Reporter: Yeray Borges
Assignee: Yeray Borges
Priority: Minor
The productized version of org.picketbox includes some libraries that must be explicitly excluded from core.
Although those libraries are not included by the community version, it is harmless if we add those exclusions directly in the upstream project, instead of adding the exclusions on each product conversion.
An alternative could be to use an eap-ization commit for this task, but these exclusions in the upstream will minimize the required stuff for the wf-to-cd branches.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-6607) Broadcast/Discovery group is possible to create with just a name
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-6607?page=com.atlassian.jira.plugin.... ]
ehsavoie Hugonnet reassigned WFLY-6607:
---------------------------------------
Assignee: ehsavoie Hugonnet (was: Chao Wang)
> Broadcast/Discovery group is possible to create with just a name
> ----------------------------------------------------------------
>
> Key: WFLY-6607
> URL: https://issues.jboss.org/browse/WFLY-6607
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: ehsavoie Hugonnet
>
> When defining new broadcast-group in Configuration: Subsystems Subsystem: Messaging - ActiveMQ Messaging Provider: default
> user must define name, at least one connector and then either socket-binding or jgroups-channel-name (not both of them, just one)
> At this moment it's possible to create broadcast group with just a name which is wrong.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months