[JBoss JIRA] (DROOLS-3511) UX Design for additional options for "create scenario" asset dialog
by Amy Glass (Jira)
[ https://issues.jboss.org/browse/DROOLS-3511?page=com.atlassian.jira.plugi... ]
Amy Glass commented on DROOLS-3511:
-----------------------------------
[~zhutaojiajia] - is this complete? should it be included in this current sprint?
> UX Design for additional options for "create scenario" asset dialog
> -------------------------------------------------------------------
>
> Key: DROOLS-3511
> URL: https://issues.jboss.org/browse/DROOLS-3511
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Amy Glass
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: TestScenarioPreviewDEVversion.png
>
>
> Add configuration options to the "Create New Test Scenario" dialog.
> There should be a drop-down selector to select Source Type.
> Currently, the values in the drop-down will be Rule and DMN, but this list can grow.
> Once the user selects a value, depending on the source selected, the user may need to specify more information, such as a file name.
> Drools-2696 includes an initial MVP design. This issue is created to expand upon that design to support additional configuration options.
> [~dzonca] [~tirelli] [~ibek] Please add additional details if possible. Thank you.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11630) JDBC datasource should be granted the connect SocketPermission
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFLY-11630?page=com.atlassian.jira.plugin... ]
Ondrej Kotek updated WFLY-11630:
--------------------------------
Attachment: DataSourceDefinitionJPATestCase-output-missing_SocketPermission_Connect.txt
> JDBC datasource should be granted the connect SocketPermission
> --------------------------------------------------------------
>
> Key: WFLY-11630
> URL: https://issues.jboss.org/browse/WFLY-11630
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Security
> Affects Versions: 16.0.0.Beta1
> Reporter: Ondrej Kotek
> Assignee: Flavia Rainone
> Priority: Major
> Labels: security-manager
> Attachments: DataSourceDefinitionJPATestCase-output-missing_SocketPermission_Connect.txt
>
>
> When a deployment uses connection on a JDBC datasource, the deployment needs the {{connect}} {{SocketPermission}} granted.
> For example
> {noformat}
> ...
> DataSource ds = (DataSource) ctx.lookup("java:jboss/datasources/ExampleDS");
> Connection conn = ds.getConnection();
> ...
> {noformat}
> may require {{permissions.xml}} like
> {noformat}
> <permissions version="7">
> <!-- Connections to databases -->
> <permission>
> <class-name>java.net.SocketPermission</class-name>
> <name>*</name> <!-- This can be hardened by using specific URLs/IPs -->
> <actions>resolve,connect</actions>
> </permission>
> </permissions>
> {noformat}
> However, {{resolve}} {{SocketPermission}} should be enough. The JCA spec states, at the 21.2 session (SecurityPermissions), the rar should always be granted the {{connect}} {{SocketPermission.}} JDBC extends the JCA spec.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11630) JDBC datasource should be granted the connect SocketPermission
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFLY-11630?page=com.atlassian.jira.plugin... ]
Ondrej Kotek updated WFLY-11630:
--------------------------------
Attachment: (was: DataSourceDefinitionJPATestCase-output-missing_SocketPermission.txt)
> JDBC datasource should be granted the connect SocketPermission
> --------------------------------------------------------------
>
> Key: WFLY-11630
> URL: https://issues.jboss.org/browse/WFLY-11630
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Security
> Affects Versions: 16.0.0.Beta1
> Reporter: Ondrej Kotek
> Assignee: Flavia Rainone
> Priority: Major
> Labels: security-manager
>
> When a deployment uses connection on a JDBC datasource, the deployment needs the {{connect}} {{SocketPermission}} granted.
> For example
> {noformat}
> ...
> DataSource ds = (DataSource) ctx.lookup("java:jboss/datasources/ExampleDS");
> Connection conn = ds.getConnection();
> ...
> {noformat}
> may require {{permissions.xml}} like
> {noformat}
> <permissions version="7">
> <!-- Connections to databases -->
> <permission>
> <class-name>java.net.SocketPermission</class-name>
> <name>*</name> <!-- This can be hardened by using specific URLs/IPs -->
> <actions>resolve,connect</actions>
> </permission>
> </permissions>
> {noformat}
> However, {{resolve}} {{SocketPermission}} should be enough. The JCA spec states, at the 21.2 session (SecurityPermissions), the rar should always be granted the {{connect}} {{SocketPermission.}} JDBC extends the JCA spec.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3492:
---------------------------------
Story Points: 3
> Create UX proposal to show/edit Test Scenario (Preview) global setting
> ----------------------------------------------------------------------
>
> Key: DROOLS-3492
> URL: https://issues.jboss.org/browse/DROOLS-3492
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: tao zhu
> Priority: Major
> Labels: ScenarioSimulation, UXD, UXTeam
> Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png, test-report-icon.png, 屏幕快照 2019-01-22 下午4.44.04.png
>
>
> As user I want to be able to see/edit editor global settings.
> For instance DMN file linked to the scenario or the Session name of a Rule scenario
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11630) JDBC datasource should be granted the connect SocketPermission
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFLY-11630?page=com.atlassian.jira.plugin... ]
Ondrej Kotek updated WFLY-11630:
--------------------------------
Attachment: DataSourceDefinitionJPATestCase-output-missing_SocketPermission.txt
> JDBC datasource should be granted the connect SocketPermission
> --------------------------------------------------------------
>
> Key: WFLY-11630
> URL: https://issues.jboss.org/browse/WFLY-11630
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Security
> Affects Versions: 16.0.0.Beta1
> Reporter: Ondrej Kotek
> Assignee: Flavia Rainone
> Priority: Major
> Labels: security-manager
> Attachments: DataSourceDefinitionJPATestCase-output-missing_SocketPermission.txt
>
>
> When a deployment uses connection on a JDBC datasource, the deployment needs the {{connect}} {{SocketPermission}} granted.
> For example
> {noformat}
> ...
> DataSource ds = (DataSource) ctx.lookup("java:jboss/datasources/ExampleDS");
> Connection conn = ds.getConnection();
> ...
> {noformat}
> may require {{permissions.xml}} like
> {noformat}
> <permissions version="7">
> <!-- Connections to databases -->
> <permission>
> <class-name>java.net.SocketPermission</class-name>
> <name>*</name> <!-- This can be hardened by using specific URLs/IPs -->
> <actions>resolve,connect</actions>
> </permission>
> </permissions>
> {noformat}
> However, {{resolve}} {{SocketPermission}} should be enough. The JCA spec states, at the 21.2 session (SecurityPermissions), the rar should always be granted the {{connect}} {{SocketPermission.}} JDBC extends the JCA spec.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11630) JDBC datasource should be granted the connect SocketPermission
by Ondrej Kotek (Jira)
Ondrej Kotek created WFLY-11630:
-----------------------------------
Summary: JDBC datasource should be granted the connect SocketPermission
Key: WFLY-11630
URL: https://issues.jboss.org/browse/WFLY-11630
Project: WildFly
Issue Type: Bug
Components: JCA, Security
Affects Versions: 16.0.0.Beta1
Reporter: Ondrej Kotek
Assignee: Flavia Rainone
When a deployment uses connection on a JDBC datasource, the deployment needs the {{connect}} {{SocketPermission}} granted.
For example
{noformat}
...
DataSource ds = (DataSource) ctx.lookup("java:jboss/datasources/ExampleDS");
Connection conn = ds.getConnection();
...
{noformat}
may require {{permissions.xml}} like
{noformat}
<permissions version="7">
<!-- Connections to databases -->
<permission>
<class-name>java.net.SocketPermission</class-name>
<name>*</name> <!-- This can be hardened by using specific URLs/IPs -->
<actions>resolve,connect</actions>
</permission>
</permissions>
{noformat}
However, {{resolve}} {{SocketPermission}} should be enough. The JCA spec states, at the 21.2 session (SecurityPermissions), the rar should always be granted the {{connect}} {{SocketPermission.}} JDBC extends the JCA spec.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3002) Enhance performance of PMML using scorecards
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3002?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3002:
---------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01)
> Enhance performance of PMML using scorecards
> --------------------------------------------
>
> Key: DROOLS-3002
> URL: https://issues.jboss.org/browse/DROOLS-3002
> Project: Drools
> Issue Type: Enhancement
> Components: PMML
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Lance Leverich
> Priority: Major
> Labels: drools-core
>
> Re-factoring of the classes and mechanisms that generate rules and classes from a PMML resource that contains a Scorecard model.
> # Make further usage of POJOs to replace any types declared within the rule file
> # Make the generation of rules and classes be more direct (i.e. reduce/remove the rules engine use in generating rules and classes)
> # Reduce the rules generated so that the number of steps required to apply a model is minimized
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months