[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 edited comment on DROOLS-4086 at 5/30/19 6:02 AM:
-----------------------------------------------------------------
[~manstis] Hi, I will just share my opinion about some of questions:
# We discuss with Jozef and we thinking the most important thing need to be searchable is "Data cells".
# We may have a small button with magnifier among other functional buttons and if you navigate the cursor on it or click, the search field will appear
!Example.png|thumbnail!
# If we will create search only for "Expression editor", I suppose it will be enough just highlight needed result as if we use the browser search.
# In [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279] if I understand right, Edson asks you to estimate implementation of the search for DMN models and GDT, but customer mention only GDT. So I think we need search for GDT or for both.
was (Author: jfomin):
[~manstis] Hi, I will just share my opinion about some of questions:
# We discuss with Jozef and we thinking the most important thing need to be searchable is "Data cells".
# We may have a small button with magnifier among other functional buttons and if you navigate the cursor on it or click, the search field will appear
!Example.png|thumbnail!
# If we will create search only for "Expression editor", I suppose it will be enough just highlight needed result as if we use the browser search.
# In [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279] if I understand right, Edson ask you to estimate implementation of search for DMN models and GDT, but customer mention only GDT. So I think we need search for GDT or for both.
> [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
> Attachments: Example.png
>
>
> 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] (WFCORE-4497) jdbc realm is not supporting hex encoding
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-4497?page=com.atlassian.jira.plugi... ]
Darran Lofthouse resolved WFCORE-4497.
--------------------------------------
Resolution: Explained
Thanks, please re-open or create a new issue if there are problems with WildFly 17.
> jdbc realm is not supporting hex encoding
> ------------------------------------------
>
> Key: WFCORE-4497
> URL: https://issues.jboss.org/browse/WFCORE-4497
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Environment: windows mssql
> Reporter: Christopher Willems
> Priority: Major
>
> following CLI is not generating the encoding attributes in the standalone xml :
> /subsystem=elytron/jdbc-realm=demo-realm:add(principal-query=[{data-source=Identities,sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?", bcrypt-mapper={password-index=1,hash-encoding=hex, salt-index=2, salt-encoding=hex, iteration-count-index=3}}])
> we get
> <jdbc-realm name="demo-realm">
> <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3"/>
> </principal-query>
> </jdbc-realm>
> adding the attributes ourselves results in a parsing error .
> OPVDX001: Validation error in standalone.xml -----------------------------------
> |
> | 360: <jdbc-realm name="demo-realm">
> | 361: <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> | 362: <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3" hash-encoding="hex"/>
> | ^^^^ 'hash-encoding' isn't an allowed attribute for the 'bcrypt-mapper'
> | element
> |
> | Attributes allowed here are: iteration-count-index, password-index,
> | salt-index
> |
> | 363: </principal-query>
> | 364: </jdbc-realm>
> | 365: <jdbc-realm name="jdbc2-realm">
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[362,25]
> | > Message: WFLYCTL0376: Unexpected attribute 'hash-encoding'
> | > encountered. Valid attributes are: 'password-index, salt-index,
> | > iteration-count-index'
> |
> this is also the case for the other mappers
--
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:
-----------------------------------
Attachment: Example.png
> [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
> Attachments: Example.png
>
>
> 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] (WFCORE-4497) jdbc realm is not supporting hex encoding
by Christopher Willems (Jira)
[ https://issues.jboss.org/browse/WFCORE-4497?page=com.atlassian.jira.plugi... ]
Christopher Willems edited comment on WFCORE-4497 at 5/30/19 5:45 AM:
----------------------------------------------------------------------
ok. i will try again with 17 and confirm if this is resolved . Currently running 16 final.
was (Author: i015101):
ok. i will try again with 17 and confirm if this is resolved .
> jdbc realm is not supporting hex encoding
> ------------------------------------------
>
> Key: WFCORE-4497
> URL: https://issues.jboss.org/browse/WFCORE-4497
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Environment: windows mssql
> Reporter: Christopher Willems
> Priority: Major
>
> following CLI is not generating the encoding attributes in the standalone xml :
> /subsystem=elytron/jdbc-realm=demo-realm:add(principal-query=[{data-source=Identities,sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?", bcrypt-mapper={password-index=1,hash-encoding=hex, salt-index=2, salt-encoding=hex, iteration-count-index=3}}])
> we get
> <jdbc-realm name="demo-realm">
> <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3"/>
> </principal-query>
> </jdbc-realm>
> adding the attributes ourselves results in a parsing error .
> OPVDX001: Validation error in standalone.xml -----------------------------------
> |
> | 360: <jdbc-realm name="demo-realm">
> | 361: <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> | 362: <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3" hash-encoding="hex"/>
> | ^^^^ 'hash-encoding' isn't an allowed attribute for the 'bcrypt-mapper'
> | element
> |
> | Attributes allowed here are: iteration-count-index, password-index,
> | salt-index
> |
> | 363: </principal-query>
> | 364: </jdbc-realm>
> | 365: <jdbc-realm name="jdbc2-realm">
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[362,25]
> | > Message: WFLYCTL0376: Unexpected attribute 'hash-encoding'
> | > encountered. Valid attributes are: 'password-index, salt-index,
> | > iteration-count-index'
> |
> this is also the case for the other mappers
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4497) jdbc realm is not supporting hex encoding
by Christopher Willems (Jira)
[ https://issues.jboss.org/browse/WFCORE-4497?page=com.atlassian.jira.plugi... ]
Christopher Willems commented on WFCORE-4497:
---------------------------------------------
ok. i will try again with 17 and confirm if this is resolved .
> jdbc realm is not supporting hex encoding
> ------------------------------------------
>
> Key: WFCORE-4497
> URL: https://issues.jboss.org/browse/WFCORE-4497
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Environment: windows mssql
> Reporter: Christopher Willems
> Priority: Major
>
> following CLI is not generating the encoding attributes in the standalone xml :
> /subsystem=elytron/jdbc-realm=demo-realm:add(principal-query=[{data-source=Identities,sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?", bcrypt-mapper={password-index=1,hash-encoding=hex, salt-index=2, salt-encoding=hex, iteration-count-index=3}}])
> we get
> <jdbc-realm name="demo-realm">
> <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3"/>
> </principal-query>
> </jdbc-realm>
> adding the attributes ourselves results in a parsing error .
> OPVDX001: Validation error in standalone.xml -----------------------------------
> |
> | 360: <jdbc-realm name="demo-realm">
> | 361: <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> | 362: <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3" hash-encoding="hex"/>
> | ^^^^ 'hash-encoding' isn't an allowed attribute for the 'bcrypt-mapper'
> | element
> |
> | Attributes allowed here are: iteration-count-index, password-index,
> | salt-index
> |
> | 363: </principal-query>
> | 364: </jdbc-realm>
> | 365: <jdbc-realm name="jdbc2-realm">
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[362,25]
> | > Message: WFLYCTL0376: Unexpected attribute 'hash-encoding'
> | > encountered. Valid attributes are: 'password-index, salt-index,
> | > iteration-count-index'
> |
> this is also the case for the other mappers
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4497) jdbc realm is not supporting hex encoding
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFCORE-4497?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved ELY-1817 to WFCORE-4497:
-----------------------------------------------
Project: WildFly Core (was: WildFly Elytron)
Key: WFCORE-4497 (was: ELY-1817)
Component/s: Security
(was: Authentication Mechanisms)
Affects Version/s: (was: 1.8.0.Final)
> jdbc realm is not supporting hex encoding
> ------------------------------------------
>
> Key: WFCORE-4497
> URL: https://issues.jboss.org/browse/WFCORE-4497
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Environment: windows mssql
> Reporter: Christopher Willems
> Priority: Major
>
> following CLI is not generating the encoding attributes in the standalone xml :
> /subsystem=elytron/jdbc-realm=demo-realm:add(principal-query=[{data-source=Identities,sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?", bcrypt-mapper={password-index=1,hash-encoding=hex, salt-index=2, salt-encoding=hex, iteration-count-index=3}}])
> we get
> <jdbc-realm name="demo-realm">
> <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3"/>
> </principal-query>
> </jdbc-realm>
> adding the attributes ourselves results in a parsing error .
> OPVDX001: Validation error in standalone.xml -----------------------------------
> |
> | 360: <jdbc-realm name="demo-realm">
> | 361: <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> | 362: <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3" hash-encoding="hex"/>
> | ^^^^ 'hash-encoding' isn't an allowed attribute for the 'bcrypt-mapper'
> | element
> |
> | Attributes allowed here are: iteration-count-index, password-index,
> | salt-index
> |
> | 363: </principal-query>
> | 364: </jdbc-realm>
> | 365: <jdbc-realm name="jdbc2-realm">
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[362,25]
> | > Message: WFLYCTL0376: Unexpected attribute 'hash-encoding'
> | > encountered. Valid attributes are: 'password-index, salt-index,
> | > iteration-count-index'
> |
> this is also the case for the other mappers
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ELY-1817) jdbc realm is not supporting hex encoding
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/ELY-1817?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on ELY-1817:
---------------------------------------
Which application server version are you using? This is a feature added to WildFly 17.
> jdbc realm is not supporting hex encoding
> ------------------------------------------
>
> Key: ELY-1817
> URL: https://issues.jboss.org/browse/ELY-1817
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Mechanisms
> Affects Versions: 1.8.0.Final
> Environment: windows mssql
> Reporter: Christopher Willems
> Priority: Major
>
> following CLI is not generating the encoding attributes in the standalone xml :
> /subsystem=elytron/jdbc-realm=demo-realm:add(principal-query=[{data-source=Identities,sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?", bcrypt-mapper={password-index=1,hash-encoding=hex, salt-index=2, salt-encoding=hex, iteration-count-index=3}}])
> we get
> <jdbc-realm name="demo-realm">
> <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3"/>
> </principal-query>
> </jdbc-realm>
> adding the attributes ourselves results in a parsing error .
> OPVDX001: Validation error in standalone.xml -----------------------------------
> |
> | 360: <jdbc-realm name="demo-realm">
> | 361: <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
> | 362: <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3" hash-encoding="hex"/>
> | ^^^^ 'hash-encoding' isn't an allowed attribute for the 'bcrypt-mapper'
> | element
> |
> | Attributes allowed here are: iteration-count-index, password-index,
> | salt-index
> |
> | 363: </principal-query>
> | 364: </jdbc-realm>
> | 365: <jdbc-realm name="jdbc2-realm">
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[362,25]
> | > Message: WFLYCTL0376: Unexpected attribute 'hash-encoding'
> | > encountered. Valid attributes are: 'password-index, salt-index,
> | > iteration-count-index'
> |
> this is also the case for the other mappers
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ELY-1817) jdbc realm is not supporting hex encoding
by Christopher Willems (Jira)
Christopher Willems created ELY-1817:
----------------------------------------
Summary: jdbc realm is not supporting hex encoding
Key: ELY-1817
URL: https://issues.jboss.org/browse/ELY-1817
Project: WildFly Elytron
Issue Type: Bug
Components: Authentication Mechanisms
Affects Versions: 1.8.0.Final
Environment: windows mssql
Reporter: Christopher Willems
following CLI is not generating the encoding attributes in the standalone xml :
/subsystem=elytron/jdbc-realm=demo-realm:add(principal-query=[{data-source=Identities,sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?", bcrypt-mapper={password-index=1,hash-encoding=hex, salt-index=2, salt-encoding=hex, iteration-count-index=3}}])
we get
<jdbc-realm name="demo-realm">
<principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
<bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3"/>
</principal-query>
</jdbc-realm>
adding the attributes ourselves results in a parsing error .
OPVDX001: Validation error in standalone.xml -----------------------------------
|
| 360: <jdbc-realm name="demo-realm">
| 361: <principal-query sql="select PASSWORD, SALT, ITERATION_COUNT from IDENTITIES where NAME = ?" data-source="veri95">
| 362: <bcrypt-mapper password-index="1" salt-index="2" iteration-count-index="3" hash-encoding="hex"/>
| ^^^^ 'hash-encoding' isn't an allowed attribute for the 'bcrypt-mapper'
| element
|
| Attributes allowed here are: iteration-count-index, password-index,
| salt-index
|
| 363: </principal-query>
| 364: </jdbc-realm>
| 365: <jdbc-realm name="jdbc2-realm">
|
| The primary underlying error message was:
| > ParseError at [row,col]:[362,25]
| > Message: WFLYCTL0376: Unexpected attribute 'hash-encoding'
| > encountered. Valid attributes are: 'password-index, salt-index,
| > iteration-count-index'
|
this is also the case for the other mappers
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4089) EvaluatedExpression not well resolved with JIT during race
by vincent palau (Jira)
[ https://issues.jboss.org/browse/DROOLS-4089?page=com.atlassian.jira.plugi... ]
vincent palau commented on DROOLS-4089:
---------------------------------------
Morning [~mfusco],
we created this repo as a reproducer:
{noformat}https://github.com/vp-stage/evaluatedexpressionandjit{noformat}
Executing the test WriterTest you'll see what are we facing.
{noformat} Testclass: com.isolator.cases.WriterTest
executing:$ mvn clean test
{noformat}
{noformat}
java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class com.isolator.cases.Writer
at org.drools.core.reteoo.PropertySpecificUtil.setPropertyOnMask(PropertySpecificUtil.java:105)
{noformat}
BTW: We also updated to latest version: 7.22.0.Final
I hope this is now useful for you :)
Thank you for your help!
Regards
> EvaluatedExpression not well resolved with JIT during race
> ------------------------------------------------------------
>
> Key: DROOLS-4089
> URL: https://issues.jboss.org/browse/DROOLS-4089
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.20.0.Final
> Reporter: vincent palau
> Assignee: Mario Fusco
> Priority: Major
> Attachments: debugging-1.png
>
>
> We recently moved from Drools 7.9.0 to 7.20.
> Some errors started appearing in ours tests when calling static methods in LHS drools.
> This started happening when all tests were run simultaneously.
> It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name:
> A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error:
> {noformat}
> "java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord"
> {noformat}
> Debugging info:
> Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main...
> !debugging-1.png|full!
> 1) is the current evaluated property
> 2) Should be the right property of WriterRecord
> 3) Perhaps the expression which should be executed instead of invocations.get(0)
> We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat}
> Is there any chance to this bug fixed?
> Do you need more info?
> Thanks in advance for your support.
> {panel:title=Reproducer}
> https://github.com/vp-stage/evaluatedexpressionandjit
> {panel}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month