[Red Hat JIRA] (WFCORE-5271) NullPointerException creating new KeyStore without type
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFCORE-5271?page=com.atlassian.jira.plug... ]
Lukas Vydra reassigned WFCORE-5271:
-----------------------------------
Assignee: Lukas Vydra
> NullPointerException creating new KeyStore without type
> -------------------------------------------------------
>
> Key: WFCORE-5271
> URL: https://issues.redhat.com/browse/WFCORE-5271
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Lukas Vydra
> Priority: Major
>
> The "type" attribute when adding a new KeyStore has been made optional, this is so that is the KeyStore already exists we can dynamically discover the type.
> If however the KeyStore does not exist this leads to a NullPointerException as it is never created:
> {code:java}
> /subsystem=elytron/key-store=test:add(relative-to=jboss.server.config.dir, path=test1.keystore, credential-reference={clear-text="${ENC:AAA}"})
> {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.key-store.test" => "WF
> LYELY00004: Unable to start the service.
> Caused by: java.lang.NullPointerException"}},
> "rolled-back" => true
> } {code}
>
> If it doesn't exist we should likely create it using the default from KeyStore.getDetaultType()
> {code:java}
> Caused by: java.lang.NullPointerExceptionCaused by: java.lang.NullPointerException at org.wildfly.extension.elytron@15.0.0.Beta1-SNAPSHOT//org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:180) ... 8 more {code}
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-6028) Implement Transformations/Expressions
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-6028:
----------------------------------------
Summary: Implement Transformations/Expressions
Key: DROOLS-6028
URL: https://issues.redhat.com/browse/DROOLS-6028
Project: Drools
Issue Type: Story
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
define framework for Expression/Transformation implementation.
Implements specific Expressions.
This must be do at some common module
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5993) BRL call action columns with template keys are not converted correctly
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5993?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5993:
--------------------------------
Steps to Reproduce:
# Import the attached project [^MySpace_covid.zip]
# There will be decision table producing '$test.sendNotification( "you are positive" );' snippet
# Convert the gdst to XLS
# Open the produced XLS table
Current: in XLS there is '$test.sendNotification( "you are positive" );' snippet
Expected: in XLS there is '$test.setSendNotification( "you are positive" );' snippet
was:
# Import the attached project [^MySpace_covid.zip]
# There will be decision table producing '$test.sendNotification( "you are positive" );' snippet
# Convert the gdcs to XLS
# Open the produced XLS table
Current: in XLS there is '$test.sendNotification( "you are positive" );' snippet
Expected: in XLS there is '$test.setSendNotification( "you are positive" );' snippet
> BRL call action columns with template keys are not converted correctly
> ----------------------------------------------------------------------
>
> Key: DROOLS-5993
> URL: https://issues.redhat.com/browse/DROOLS-5993
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.50.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: MySpace_covid.zip, Screenshot from 2021-02-02 15-07-53.png, Screenshot from 2021-02-02 15-08-00.png, Screenshot from 2021-02-02 15-08-13.png
>
>
> This issue is related to the new feature implemented as DROOLS-5892
>
> If the guided decision table, with BRL action call column is converted to XLS, the conversion change the method name with *set* prefix.
> Reproducer test prepared https://github.com/kiegroup/drools-wb/pull/1460
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (DROOLS-5993) BRL call action columns with template keys are not converted correctly
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5993?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5993:
--------------------------------
Steps to Reproduce:
# Import the attached project [^MySpace_covid.zip]
# There will be decision table producing '$test.sendNotification( "you are positive" );' snippet
# Convert the gdst to XLS
# Open the produced XLS table
Current: in XLS there is '$test.setSendNotification( "you are positive" );' snippet
Expected: in XLS there is '$test.sendNotification( "you are positive" );' snippet
was:
# Import the attached project [^MySpace_covid.zip]
# There will be decision table producing '$test.sendNotification( "you are positive" );' snippet
# Convert the gdst to XLS
# Open the produced XLS table
Current: in XLS there is '$test.sendNotification( "you are positive" );' snippet
Expected: in XLS there is '$test.setSendNotification( "you are positive" );' snippet
> BRL call action columns with template keys are not converted correctly
> ----------------------------------------------------------------------
>
> Key: DROOLS-5993
> URL: https://issues.redhat.com/browse/DROOLS-5993
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.50.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: MySpace_covid.zip, Screenshot from 2021-02-02 15-07-53.png, Screenshot from 2021-02-02 15-08-00.png, Screenshot from 2021-02-02 15-08-13.png
>
>
> This issue is related to the new feature implemented as DROOLS-5892
>
> If the guided decision table, with BRL action call column is converted to XLS, the conversion change the method name with *set* prefix.
> Reproducer test prepared https://github.com/kiegroup/drools-wb/pull/1460
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months