[JBoss JIRA] (WFCORE-4482) Out of the box SSL with Wildfly Elytron
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/WFCORE-4482?page=com.atlassian.jira.plugi... ]
Farah Juma updated WFCORE-4482:
-------------------------------
Fix Version/s: 11.0.0.Beta1
(was: 10.0.0.Beta1)
> Out of the box SSL with Wildfly Elytron
> ---------------------------------------
>
> Key: WFCORE-4482
> URL: https://issues.jboss.org/browse/WFCORE-4482
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Major
> Labels: EAP-CD18
> Fix For: 11.0.0.Beta1
>
>
> The details of this RFE will be explored within the analysis, presently Undertow depends on a security-realm that generates a self signed cert on start up so we will require an Elytron equivalent.
> There may be opportunities to tie this in in some way with the new CA integration support but that can be explored in the analysis.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-3420?page=com.atlassian.jira.plugi... ]
Yeser Amer commented on DROOLS-3420:
------------------------------------
[~kkufova] Point 2 and 3 managed on https://issues.jboss.org/browse/DROOLS-4080
> Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget
> -------------------------------------------------------------------
>
> Key: DROOLS-3420
> URL: https://issues.jboss.org/browse/DROOLS-3420
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Daniele Zonca
> Priority: Minor
>
> SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget".
> Later, ask [~Rikkola] to move it on upper framework.
> *ADDITIONAL IMPROVEMENTS:*
> # -When there are two {{.dmn}} files in the project, the second one is not in the list when creating a new test scenario asset. *The list must be refreshed to contain all available {{.dmn}} files.* The same problem occurs also with a single {{.dmn}} file in the project. Sometimes the list of available {{.dmn}} files is not refreshed and even though they are in the project, they are not displayed in the list.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # Change *Choose DMN asset* to *Choose a DMN asset*.
> # The box for choosing a {{.dmn}} file is not wide enough. Make it either as wide as the boxes above (for the name of the asset and the package) or change it to a drop down (the same style as the package drop down).
> # -The value of a {{.dmn}} file should not be pre-filled once the box has been used. Clear the status so the box is always empty.- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
> # -The field *Choose DMN asset* should be marked with *{color:red}*{color}* (required field).- -> Addressed in [!1047|https://github.com/kiegroup/drools-wb/pull/1047].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-4086:
-----------------------------------
Story Points: 15
> [GSS-RFE] Search feature in GDST
> --------------------------------
>
> Key: DROOLS-4086
> URL: https://issues.jboss.org/browse/DROOLS-4086
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Yevgeniy Fomin
> Priority: Major
> Labels: drools-tools
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-4086:
----------------------------------------
[~jfomin] Hi, I'd like to understand:-
# _What_ text needs to be searchable? Header content? Cell content? Visible content or _all_ header content (e.g. a GDT's header only contains a couple of words, but these words are used to generate a much longer piece of text that can be seen on "hover over").
# _How_ should search be invoked? Popup? Dock? Keyboard shortcut? If some form of widget, how and where is the widget accessible?
# _Where_ are results to be shown? In a results panel? With link to _actual_ text? In-place? How do you iterate through matches?
# What about other assets?
[~davidredhat] Are there plans for anything like this in AppFormer? It seems a foundation type of requirement? For the two specific asset types listed I can walk the models "at search time" or I can index them at save time (although that means you can only search _saved_ files and not ones actively being edited). I think walking may be most reliable however it's likely to be the slowest too. Any plans for any form of indexing of dynamic content other than the Lucene/ES indexes we build atm?
[~uxdlc] This is likely to need UX involvement too.
> [GSS-RFE] Search feature in GDST
> --------------------------------
>
> Key: DROOLS-4086
> URL: https://issues.jboss.org/browse/DROOLS-4086
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Yevgeniy Fomin
> Priority: Major
> Labels: drools-tools
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-1280) further document state machine, thread-safety and include diagrams
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-1280?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-1280:
------------------------------------------
Will link to 7.5 decision engine reference doc, where I'll expand to include upstream content from the Running chapter to cover this (last related upstream chapter around decision engine reference, excluded from 7.4 due to scope).
> further document state machine, thread-safety and include diagrams
> ------------------------------------------------------------------
>
> Key: DROOLS-1280
> URL: https://issues.jboss.org/browse/DROOLS-1280
> Project: Drools
> Issue Type: Enhancement
> Components: docs
> Reporter: Matteo Mortari
> Assignee: Stetson Robinson
> Priority: Minor
>
> Spin-off remaining linked documentation work from [DROOLS-1272] for:
> Include docs on state machine and thread safety
> Flow charts and state diagrams
> Ensure the N&N section describing state machine and thread-safety is correctly reflected in section of the manual.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-1273) document Rule Evaluation Modes
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-1273?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-1273:
------------------------------------------
Will link to 7.5 decision engine reference doc, where I'll expand to include upstream content from the Running chapter to cover this (last related upstream chapter around decision engine reference, excluded from 7.4 due to scope).
> document Rule Evaluation Modes
> ------------------------------
>
> Key: DROOLS-1273
> URL: https://issues.jboss.org/browse/DROOLS-1273
> Project: Drools
> Issue Type: Enhancement
> Components: docs
> Reporter: Matteo Mortari
> Assignee: Stetson Robinson
> Priority: Minor
>
> documents Immediate, Eager and Lazy annotations. As well as the ForceImmedateFilter api.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST
by Yevgeniy Fomin (Jira)
[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ]
Yevgeniy Fomin updated DROOLS-4086:
-----------------------------------
Description:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirement
- The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
- We may add auto-suggestion mechanism
- Do we need search history?
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
h1. UX design
- Add magnifying-glass icon.
- Search-box can be popup window after clicking on icon or just pop field
- The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
was:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirement
- The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
- We may add auto-suggestion mechanism
- Do we need search history?
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
h1. UX design
- Add magnifying-glass icon.
- Search-box can be popup window after clicking on icon or just pop field
- The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
*- XSS, SQL, JavaScript, HTML injections.
> [GSS-RFE] Search feature in GDST
> --------------------------------
>
> Key: DROOLS-4086
> URL: https://issues.jboss.org/browse/DROOLS-4086
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Yevgeniy Fomin
> Priority: Major
> Labels: drools-tools
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month