[JBoss JIRA] (WFLY-9855) [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/WFLY-9855?page=com.atlassian.jira.plugin.... ]
Tomas Hofman commented on WFLY-9855:
------------------------------------
Good point, I will get back to this shortly. Thx Tomaz.
> [JDK9+] org.jboss.security.negotiation.spnego package is exported by two jars
> -----------------------------------------------------------------------------
>
> Key: WFLY-9855
> URL: https://issues.jboss.org/browse/WFLY-9855
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Tomaz Cerar
> Assignee: Tomas Hofman
> Priority: Critical
>
> Currently if you have
> jboss-negotiation-spnego-3.0.4.Final and jboss-negotiation-extras-3.0.4.Final.jar
> on your module path, jvm complains as both jars export package org.jboss.security.negotiation.spnego
> which violates the modules contract where only one module (jar) can provide single package.
> example error that jvm prints
> {noformat}
> Error: Modules jboss.negotiation.extras and jboss.negotiation.spnego export package org.jboss.security.negotiation.spnego to module wildfly.clustering.common
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3371) [DMN Designer] Add Decision Service to Palette
by Michael Anstis (Jira)
Michael Anstis created DROOLS-3371:
--------------------------------------
Summary: [DMN Designer] Add Decision Service to Palette
Key: DROOLS-3371
URL: https://issues.jboss.org/browse/DROOLS-3371
Project: Drools
Issue Type: Feature Request
Components: DMN Editor
Affects Versions: 7.15.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
Add a(n expanded) Decision Service node to the Palette.
Allow containment of all DMN elements (so Decision Service is a container).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1962) [DMN Editor] Decision service
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-1962?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-1962:
-----------------------------------
Description:
The DMN Editor is to support Decision Services (as defined in the DMN 1.2 Specification).
Decision Services should present themselves as a new node in the Palette that can be dragged on to the Canvas.
Decision Services will appear _expanded_ to begin however we should also add support for collapsing the Decision Service node (thus hiding it's _content_).
A Decision Service node acts as a container for the other pre-existing DMN elements (Decision, BKM, InputData, KnowledgeSource etc).
See 5.3.3 Decision services of the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF] for details.
See 6.2.3 Connection rules for connection rules.
See 6.2.5 Decision service for schematics.
was:"In DRD it is rounded rectangle that surrounds all of the encapsulated decisions in the service. The inputs to the service are defined by all of the information requirements leading into the rounded rectangle. The outputs of the service are the decisions shown above the straight line bisecting the rounded rectangle. If there is no such line, all encapsulated decisions are exposed in the service output." cited form DMN Method and Style, Chapter 3, Decision Requirements
> [DMN Editor] Decision service
> -----------------------------
>
> Key: DROOLS-1962
> URL: https://issues.jboss.org/browse/DROOLS-1962
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The DMN Editor is to support Decision Services (as defined in the DMN 1.2 Specification).
> Decision Services should present themselves as a new node in the Palette that can be dragged on to the Canvas.
> Decision Services will appear _expanded_ to begin however we should also add support for collapsing the Decision Service node (thus hiding it's _content_).
> A Decision Service node acts as a container for the other pre-existing DMN elements (Decision, BKM, InputData, KnowledgeSource etc).
> See 5.3.3 Decision services of the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF] for details.
> See 6.2.3 Connection rules for connection rules.
> See 6.2.5 Decision service for schematics.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1962) [DMN Editor] Decision service
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-1962?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-1962:
-----------------------------------
Description:
The DMN Editor is to support Decision Services (as defined in the DMN 1.2 Specification).
Decision Services should present themselves as a new node in the Palette that can be dragged on to the Canvas.
Decision Services will appear _expanded_ to begin however we should also add support for _collapsing_ the Decision Service node (thus hiding it's _content_).
A Decision Service node acts as a container for the other pre-existing DMN elements (Decision, BKM, InputData, KnowledgeSource etc).
See 5.3.3 Decision services of the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF] for details.
See 6.2.3 Connection rules for connection rules.
See 6.2.5 Decision service for schematics.
was:
The DMN Editor is to support Decision Services (as defined in the DMN 1.2 Specification).
Decision Services should present themselves as a new node in the Palette that can be dragged on to the Canvas.
Decision Services will appear _expanded_ to begin however we should also add support for collapsing the Decision Service node (thus hiding it's _content_).
A Decision Service node acts as a container for the other pre-existing DMN elements (Decision, BKM, InputData, KnowledgeSource etc).
See 5.3.3 Decision services of the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF] for details.
See 6.2.3 Connection rules for connection rules.
See 6.2.5 Decision service for schematics.
> [DMN Editor] Decision service
> -----------------------------
>
> Key: DROOLS-1962
> URL: https://issues.jboss.org/browse/DROOLS-1962
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The DMN Editor is to support Decision Services (as defined in the DMN 1.2 Specification).
> Decision Services should present themselves as a new node in the Palette that can be dragged on to the Canvas.
> Decision Services will appear _expanded_ to begin however we should also add support for _collapsing_ the Decision Service node (thus hiding it's _content_).
> A Decision Service node acts as a container for the other pre-existing DMN elements (Decision, BKM, InputData, KnowledgeSource etc).
> See 5.3.3 Decision services of the [DMN 1.2 Specification|https://www.omg.org/spec/DMN/1.2/Beta1/PDF] for details.
> See 6.2.3 Connection rules for connection rules.
> See 6.2.5 Decision service for schematics.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3347) Implement Undo/Redo
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3347?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3347:
----------------------------------
Sprint: 2018 Week 48-50
> Implement Undo/Redo
> -------------------
>
> Key: DROOLS-3347
> URL: https://issues.jboss.org/browse/DROOLS-3347
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Provide actual implementation of undo/redo.
> Step:
> 1) verify that all model modification happen through commands (check "flush" methods inside grid cells and other access to model)
> 2) implement columns size persistence inside backend model (wrap simulation inside another object to store dimension size)
> 3) implement actual undo/redo
> 4) add Undo/Redo buttons
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3361) Update simulation model to support multiple types (DRL, DMN)
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3361?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3361:
----------------------------------
Description:
Update simulation model to support multiple types (DRL, DMN).
Specs:
- DRL: Save name of the session to use
- DMN: Save path to the DMN file
was:Update simulation model to support multiple types (DRL, DMN)
> Update simulation model to support multiple types (DRL, DMN)
> ------------------------------------------------------------
>
> Key: DROOLS-3361
> URL: https://issues.jboss.org/browse/DROOLS-3361
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
>
> Update simulation model to support multiple types (DRL, DMN).
> Specs:
> - DRL: Save name of the session to use
> - DMN: Save path to the DMN file
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months