[JBoss JIRA] (ELY-820) CredentialStore is not able to create CS file which was deleted after server startup.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-820?page=com.atlassian.jira.plugin.sy... ]
Hynek Švábek reassigned ELY-820:
--------------------------------
Assignee: Peter Skopek (was: Darran Lofthouse)
> CredentialStore is not able to create CS file which was deleted after server startup.
> -------------------------------------------------------------------------------------
>
> Key: ELY-820
> URL: https://issues.jboss.org/browse/ELY-820
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
>
> CredentialStore is not able to create CS file which was deleted after server startup.
> CS file is recreated only if create.storage is set to true. But this feature would work with create.storage too.
> What do you think about it?
> *How to reproduce:*
> these steps are for creating CS file
> /subsystem=elytron/credential-store=recreate001:add(uri="cr-store://test/recreate001.jceks?store.password=pass123;create.storage=true")
> /subsystem=elytron/credential-store=recreate001/alias=alias001:add(secret-value=Elytron)
> *Own reproducer:*
> * /subsystem=elytron/credential-store=recreateCS:add(uri="cr-store://test/recreate001.jceks?store.password=pass123;create.storage=false")
> * /subsystem=elytron/credential-store=recreateCS/alias=alias2:add(secret-value=Elytron123)
> * *NOW* delete recreate001.jceks from filesystem
> * /subsystem=elytron/credential-store=recreateCS/alias=alias3:add(secret-value=Elytron123)
> * FAIL
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09504: Cannot write storage file '/home/hsvabek/securityworkspace/VERIFICATION/CredentialStore_2016_09_14/jboss-eap-7.1.0.DR9/standalone/data/recreate001.jceks' for the store 'recreateCS''",
> "rolled-back" => true
> }
> {code}
> * https://github.com/wildfly-security/wildfly-elytron/blob/5f0ed115ea265240...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (DROOLS-669) Create "behavesAs" operator to support traiting
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-669?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-669:
------------------------------------------
Fix Version/s: 7.0.0.Beta5
(was: 7.0.0.Beta4)
> Create "behavesAs" operator to support traiting
> -----------------------------------------------
>
> Key: DROOLS-669
> URL: https://issues.jboss.org/browse/DROOLS-669
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.2.0.CR3
> Reporter: Davide Sottara
> Assignee: Davide Sottara
> Fix For: 7.0.0.Beta5
>
>
> Define an operator that would check if an object can provide *natively* all the methods required by an interface. This would ensure that, upon donning the interface as a trait, no soft field would be required, and that all methods in the interface would have a concrete implementation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (DROOLS-607) Match.getObjects() should reflect the patterns' order
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-607?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-607:
------------------------------------------
Fix Version/s: 7.0.0.Beta5
(was: 7.0.0.Beta4)
> Match.getObjects() should reflect the patterns' order
> -----------------------------------------------------
>
> Key: DROOLS-607
> URL: https://issues.jboss.org/browse/DROOLS-607
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.1.0.Final
> Reporter: Davide Sottara
> Assignee: Mark Proctor
> Priority: Minor
> Fix For: 7.0.0.Beta5
>
>
> if Match.getObjects() is called on a rule with LHS A() B() C(),
> the resulting list will have the matching objects in reversed order
> - that is, [c, b, a] - making it more difficult to analyze it.
> The object's position in the list should reflect the LHS.
> The order should be preserved even when subnetworks are present.
> For example, A() not B() C() should then result in the list [a, *, c ]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (DROOLS-470) Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-470?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-470:
------------------------------------------
Fix Version/s: 7.0.0.Beta5
(was: 7.0.0.Beta4)
> Decision Table (XLS) should support fixed conditions, such as SeatDesignation(isNeighborOf($guest))
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-470
> URL: https://issues.jboss.org/browse/DROOLS-470
> Project: Drools
> Issue Type: Enhancement
> Components: decision tables
> Affects Versions: 6.1.0.Beta2
> Reporter: Geoffrey De Smet
> Assignee: Michael Anstis
> Labels: optaplanner-request-for-drools
> Fix For: 7.0.0.Beta5
>
>
> This DT should work:
> ||CONDITION||CONDITION||ACTION|
> |$guest : SeatDesignation()|$neighbor : SeatDesignation(isNeighborOf($guest))||
> |guestName == "$param"|guestName == "$param"|doSomething();|
> It crashes because of the "SeatDesignation(isNeighborOf($guest))". Only empty parenthesis are allowed.
> Failing workaround 1: This workaround (as specified by the docs), does NOT work well, because it adds the same condition (isNeighborOf($guest)) multiple times in the same rule:
> ||CONDITION||CONDITION||CONDITION||ACTION|
> |$guest : SeatDesignation()|$neighbor : SeatDesignation()|||
> |guestName == "$param"|isNeighborOf($guest), guestName == "$param"|isNeighborOf($guest), guestAge == "$param"|doSomething();|
> Failing workaround 2: Adding an extra, hidden column with that condition does not work when new rows are added because condition columns with an empty cell are ignored.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (DROOLS-744) Rule Generation Feature Request
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-744?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-744:
------------------------------------------
Fix Version/s: 7.0.0.Beta5
(was: 7.0.0.Beta4)
> Rule Generation Feature Request
> -------------------------------
>
> Key: DROOLS-744
> URL: https://issues.jboss.org/browse/DROOLS-744
> Project: Drools
> Issue Type: Feature Request
> Components: core engine, kie server
> Affects Versions: 6.2.0.Final
> Reporter: Justin Holmes
> Assignee: Mario Fusco
> Fix For: 7.0.0.Beta5
>
>
> As a developer using Drools, I want a rule generation java api that supports control logic in the rule templates (e.g. for loops, if/else) and integrates with the rule workbench in order to build highly dynamic business rules driven systems.
> The initial thought process around implementation is to build two things 1) a simple way to author mvel templates in business central, the existing text editor could be used at first and 2) a simple embedded java api in it's own maven module which can checkout the git project that has the mvel template, apply a set of domain objects to the template, check in the resulting rule files to the local git repo and then push the changes back to business central. This allows us to leverage the power of the existing MVEL and JGit tech stack while pushing the complexity to a java api, where we are stronger than the workbench itself.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (DROOLS-680) "contains" operator behaves inconsistently when used with Maps
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-680?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer updated DROOLS-680:
------------------------------------------
Fix Version/s: 7.0.0.Beta5
(was: 7.0.0.Beta4)
> "contains" operator behaves inconsistently when used with Maps
> --------------------------------------------------------------
>
> Key: DROOLS-680
> URL: https://issues.jboss.org/browse/DROOLS-680
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.6.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4
> Reporter: Davide Sottara
> Assignee: Mario Fusco
> Fix For: 7.0.0.Beta5
>
>
> In a rule
> {code}
> Bean( map contains "x" ) // assuming "map" is a property of type Map
> {code}
> "contains" is arbitrarily interpreted as "containsKey"
> The constrain will then fail after being jitted
> The documentation explicitly states that "contains" applies to collections
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months