[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3269:
----------------------------------------
Hi [~jomarko] could you please explain a little more?
It looks like the DMN's {{Context}} has a {{typeRef}} of "string":
{code:xml}
<dmn:context id="_4B4416D7-9A05-4E24-9855-EAB423A5C5CB" typeRef="string">
{code}
The {{DecisionTable}} {{OutputClause}} is also "string":
{code:xml}
<dmn:output id="_72AC8190-8D99-46E0-AF09-67B010C2935A" name="output-1" typeRef="string">
{code}
I'd like to understand more specifically what the issue is (or more probably, what the requirement is).
> [DMN Designer] Context: Default can be any expression type
> ----------------------------------------------------------
>
> Key: DROOLS-3269
> URL: https://issues.jboss.org/browse/DROOLS-3269
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Qclt6jQn.dmn, Screenshot from 2018-11-09 08-16-34.png
>
>
> The "default" box can be any type of expression, specially decision tables and nested contexts.
> Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3269:
-------------------------------------
[~manstis] please see the attached picture and dmn model, I have concern that default output context entry doesn't respect the output typeRef of the holding context.
> [DMN Designer] Context: Default can be any expression type
> ----------------------------------------------------------
>
> Key: DROOLS-3269
> URL: https://issues.jboss.org/browse/DROOLS-3269
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Qclt6jQn.dmn, Screenshot from 2018-11-09 08-16-34.png
>
>
> The "default" box can be any type of expression, specially decision tables and nested contexts.
> Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3269:
--------------------------------
Attachment: Screenshot from 2018-11-09 08-16-34.png
> [DMN Designer] Context: Default can be any expression type
> ----------------------------------------------------------
>
> Key: DROOLS-3269
> URL: https://issues.jboss.org/browse/DROOLS-3269
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Qclt6jQn.dmn, Screenshot from 2018-11-09 08-16-34.png
>
>
> The "default" box can be any type of expression, specially decision tables and nested contexts.
> Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3269:
--------------------------------
Attachment: Qclt6jQn.dmn
> [DMN Designer] Context: Default can be any expression type
> ----------------------------------------------------------
>
> Key: DROOLS-3269
> URL: https://issues.jboss.org/browse/DROOLS-3269
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Qclt6jQn.dmn, Screenshot from 2018-11-09 08-16-34.png
>
>
> The "default" box can be any type of expression, specially decision tables and nested contexts.
> Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11314) Look up of RemoteConnectionFactory with discovery-group is null
by Miroslav Novak (Jira)
Miroslav Novak created WFLY-11314:
-------------------------------------
Summary: Look up of RemoteConnectionFactory with discovery-group is null
Key: WFLY-11314
URL: https://issues.jboss.org/browse/WFLY-11314
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 14.0.0.Final
Reporter: Miroslav Novak
Assignee: ehsavoie Hugonnet
Fix For: 15.0.0.Alpha1
If RemoteConnectionFactory is defined with discovery-group like (note that it's defined directly in messaging subsystem, not in <server>...</server>):
{code}
<subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0">
<discovery-group name="dg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster" initial-wait-timeout="30000"/>
<connection-factory name="RemoteConnectionFactory" discovery-group="dg-group1" entries="java:jboss/exported/jms/RemoteConnectionFactory java:/jms/RemoteConnectionFactory"/>
</subsystem>
{code}
then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with {{null}}. See JNDI view:
{code}
[standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view
...
"jms" => {
"class-name" => "javax.naming.Context",
"children" => {
"RemoteConnectionFactory" => {
"class-name" => "java.lang.Object",
"value" => "null"
},
{code}
Result:
If EE deployment looks up or injects such CF then it fails on NullPointerException.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3261) [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue`
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3261?page=com.atlassian.jira.plugi... ]
Jozef Marko resolved DROOLS-3261.
---------------------------------
Resolution: Done
> [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue`
> ------------------------------------------------------------------------------
>
> Key: DROOLS-3261
> URL: https://issues.jboss.org/browse/DROOLS-3261
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
> Attachments: diagram.png, dtable.png
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> .. select the "Can drink beer?" header, set the default value as {{false}} and the file:
> {quote}
> <dmn:outputValues id="_A117F7DC-508C-4132-8F5F-8F8F2B0B489F">
> <dmn:text>false</dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_A4881AD1-7EDC-4B4D-AC00-078626795BA7" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> {quote}
> ..and the expected behaviour is to persist the value {{false}} in the {{defaultOutputEntry}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months