[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2890:
--------------------------------
Description:
The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
{quote}
The Definitions properties that I think we need to expose are:
* Id (probably read only)
* name (needs to be editable; can default to the file name but should remain editable)
* namespace
* Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
{quote}
h2. Manual acceptance test
- B&D new model, non default namespace (/)
- Import model with namespace (/)
- Import model without namespace (/)
was:
The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
{quote}
The Definitions properties that I think we need to expose are:
* Id (probably read only)
* name (needs to be editable; can default to the file name but should remain editable)
* namespace
* Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
{quote}
h2. Manual acceptance test
- B&D new model, non default namespace
- Import model with namespace (/)
- Import model without namespace (/)
> [DMN Designer] DMNDiagram properties
> ------------------------------------
>
> Key: DROOLS-2890
> URL: https://issues.jboss.org/browse/DROOLS-2890
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.10.0.Final
>
>
> The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
> {quote}
> The Definitions properties that I think we need to expose are:
> * Id (probably read only)
> * name (needs to be editable; can default to the file name but should remain editable)
> * namespace
> * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
> {quote}
> h2. Manual acceptance test
> - B&D new model, non default namespace (/)
> - Import model with namespace (/)
> - Import model without namespace (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2890:
--------------------------------
Description:
The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
{quote}
The Definitions properties that I think we need to expose are:
* Id (probably read only)
* name (needs to be editable; can default to the file name but should remain editable)
* namespace
* Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
{quote}
h2. Manual acceptance test
- B&D new model, non default namespace
- Import model with namespace (/)
- Import model without namespace (/)
was:
The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
{quote}
The Definitions properties that I think we need to expose are:
* Id (probably read only)
* name (needs to be editable; can default to the file name but should remain editable)
* namespace
* Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
{quote}
h2. Manual acceptance test
- B&D new model, non default namespace
- Import model with namespace
- Import model without namespace
> [DMN Designer] DMNDiagram properties
> ------------------------------------
>
> Key: DROOLS-2890
> URL: https://issues.jboss.org/browse/DROOLS-2890
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.10.0.Final
>
>
> The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
> {quote}
> The Definitions properties that I think we need to expose are:
> * Id (probably read only)
> * name (needs to be editable; can default to the file name but should remain editable)
> * namespace
> * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
> {quote}
> h2. Manual acceptance test
> - B&D new model, non default namespace
> - Import model with namespace (/)
> - Import model without namespace (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11266) JAXWS Client BOM
by Eduardo Martins (Jira)
Eduardo Martins created WFLY-11266:
--------------------------------------
Summary: JAXWS Client BOM
Key: WFLY-11266
URL: https://issues.jboss.org/browse/WFLY-11266
Project: WildFly
Issue Type: Enhancement
Components: Quickstarts
Reporter: Eduardo Martins
Assignee: Eduardo Martins
The dependency management defined on WildFly, for JAXWS/CXF client, is over 1000 SLoC due to exclusions applied, which is a nightmare to manage on client apps projects, such as the jaxws-* quickstarts.
To hide the dependency management complexity on apps a new client BOM should be added wrt JAXWS, which apps can just depend on it, and should includes all dependencies excluded on WildFly dependency management.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3220) [DMN Designer] [Edge] Unable to edit context cell
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3220?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3220:
--------------------------------------
Assignee: Daniel José dos Santos (was: Michael Anstis)
> [DMN Designer] [Edge] Unable to edit context cell
> -------------------------------------------------
>
> Key: DROOLS-3220
> URL: https://issues.jboss.org/browse/DROOLS-3220
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Environment: Windows, Edge browser
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Blocker
> Labels: drools-tools
>
> User is unable to invoke edit mode for context cells. Other expression types seems to work fine.
> Spotted during DROOLS-3214 review, however don't think it is related.
> h2. Acceptance test
> Invoke edit mode of regular cell
> - Literal
> - Dec. Table
> - Function
> - Relation
> - Invocation
> - Context
> Invoke edit mode of header cell - where applicable
> - Literal
> - Dec. Table
> - Function
> - Relation
> - Invocation
> - Context
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2890:
--------------------------------
Description:
The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
{quote}
The Definitions properties that I think we need to expose are:
* Id (probably read only)
* name (needs to be editable; can default to the file name but should remain editable)
* namespace
* Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
{quote}
h2. Manual acceptance test
- B&D new model, non default namespace
- Import model with namespace
- Import model without namespace
was:
The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
{quote}
The Definitions properties that I think we need to expose are:
* Id (probably read only)
* name (needs to be editable; can default to the file name but should remain editable)
* namespace
* Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
{quote}
> [DMN Designer] DMNDiagram properties
> ------------------------------------
>
> Key: DROOLS-2890
> URL: https://issues.jboss.org/browse/DROOLS-2890
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.10.0.Final
>
>
> The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...)
> {quote}
> The Definitions properties that I think we need to expose are:
> * Id (probably read only)
> * name (needs to be editable; can default to the file name but should remain editable)
> * namespace
> * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above.
> {quote}
> h2. Manual acceptance test
> - B&D new model, non default namespace
> - Import model with namespace
> - Import model without namespace
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3225:
-----------------------------------
Sprint: 2018 Week 42-44
> [DMN Designer] Decision table output data type is not stored
> ------------------------------------------------------------
>
> Key: DROOLS-3225
> URL: https://issues.jboss.org/browse/DROOLS-3225
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2018-11-01 10-59-08.png
>
>
> Issue spotted during DROOLS-3214, however probably not related.
> If decision table output data type is changed, the change is not reflected in the xml.
> Please follow my steps:
> - Create new DMN diagram
> - Add a decision node
> - Set the decision node top level expression as a decision table
> - Double click on Output header cell
> - Select boolean lets say
> - Save the diagram
> Check the source, there will be still stored string output data type, like below:
> {code:xml}
> <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
> <dmn:text>input-1</dmn:text>
> </dmn:inputExpression>
> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
> <dmn:text></dmn:text>
> </dmn:inputValues>
> </dmn:input>
> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
> <dmn:text>"you are right"</dmn:text>
> </dmn:inputEntry>
> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
> <dmn:text>true</dmn:text>
> </dmn:outputEntry>
> </dmn:rule>
> </dmn:decisionTable>
> </dmn:decision>
> {code}
> But the UI is like:
> !Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3225:
--------------------------------
Description:
Issue spotted during DROOLS-3214, however probably not related.
If decision table output data type is changed, the change is not reflected in the xml.
Please follow my steps:
- Create new DMN diagram
- Add a decision node
- Set the decision node top level expression as a decision table
- Double click on Output header cell
- Select boolean lets say
- Save the diagram
Check the source, there will be still stored string output data type, like below:
{code:xml}
<dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
<dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
<dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
<dmn:text>input-1</dmn:text>
</dmn:inputExpression>
<dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
<dmn:text></dmn:text>
</dmn:inputValues>
</dmn:input>
<dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
<dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
<dmn:text></dmn:text>
</dmn:outputValues>
<dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
<dmn:text></dmn:text>
</dmn:defaultOutputEntry>
</dmn:output>
<dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
<dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
<dmn:text>"you are right"</dmn:text>
</dmn:inputEntry>
<dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
<dmn:text>true</dmn:text>
</dmn:outputEntry>
</dmn:rule>
</dmn:decisionTable>
</dmn:decision>
{code}
But the UI is like:
!Screenshot from 2018-11-01 10-59-08.png|thumbnail!
was:
If decision table output data type is changed, the change is not reflected in the xml.
Please follow my steps:
- Create new DMN diagram
- Add a decision node
- Set the decision node top level expression as a decision table
- Double click on Output header cell
- Select boolean lets say
- Save the diagram
Check the source, there will be still stored string output data type, like below:
{code:xml}
<dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
<dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
<dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
<dmn:text>input-1</dmn:text>
</dmn:inputExpression>
<dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
<dmn:text></dmn:text>
</dmn:inputValues>
</dmn:input>
<dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
<dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
<dmn:text></dmn:text>
</dmn:outputValues>
<dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
<dmn:text></dmn:text>
</dmn:defaultOutputEntry>
</dmn:output>
<dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
<dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
<dmn:text>"you are right"</dmn:text>
</dmn:inputEntry>
<dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
<dmn:text>true</dmn:text>
</dmn:outputEntry>
</dmn:rule>
</dmn:decisionTable>
</dmn:decision>
{code}
But the UI is like:
!Screenshot from 2018-11-01 10-59-08.png|thumbnail!
> [DMN Designer] Decision table output data type is not stored
> ------------------------------------------------------------
>
> Key: DROOLS-3225
> URL: https://issues.jboss.org/browse/DROOLS-3225
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2018-11-01 10-59-08.png
>
>
> Issue spotted during DROOLS-3214, however probably not related.
> If decision table output data type is changed, the change is not reflected in the xml.
> Please follow my steps:
> - Create new DMN diagram
> - Add a decision node
> - Set the decision node top level expression as a decision table
> - Double click on Output header cell
> - Select boolean lets say
> - Save the diagram
> Check the source, there will be still stored string output data type, like below:
> {code:xml}
> <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
> <dmn:text>input-1</dmn:text>
> </dmn:inputExpression>
> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
> <dmn:text></dmn:text>
> </dmn:inputValues>
> </dmn:input>
> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
> <dmn:text>"you are right"</dmn:text>
> </dmn:inputEntry>
> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
> <dmn:text>true</dmn:text>
> </dmn:outputEntry>
> </dmn:rule>
> </dmn:decisionTable>
> </dmn:decision>
> {code}
> But the UI is like:
> !Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month