[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-4636:
----------------------------------
Story Points: 1
> Update Scenario Cheatsheet to mention MVEL
> ------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.jboss.org/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitations
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL and Background
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-4636:
----------------------------------
Summary: Update Scenario Cheatsheet to mention MVEL and Background (was: Update Scenario Cheatsheet to mention MVEL)
> Update Scenario Cheatsheet to mention MVEL and Background
> ---------------------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.jboss.org/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitations
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFWIP-231) Error messages in operator logs
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-231?page=com.atlassian.jira.plugin.... ]
Martin Choma closed WFWIP-231.
------------------------------
Verified with jbossqe-eap/wildfly-operator:0.3.0.Beta1-9d59838
> Error messages in operator logs
> -------------------------------
>
> Key: WFWIP-231
> URL: https://issues.jboss.org/browse/WFWIP-231
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Critical
> Labels: operator
>
> The following error log message appears in operator log:
> {noformat}
> {"level":"error","ts":1570436049.1596415,"logger":"wildlfyserver_resources","msg":"Failed to create new
> resource","WildFlyServer.Namespace":"pkremens-namespace","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart-
> loadbalancer","Resource.Type":"*v1.Service","error":"services \"quickstart-loadbalancer\" already exists","stacktrace":"github.com/go-logr/zapr.
> (*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\ngithub.com/wildfly/wildfly-operator/pkg/resources.Create\n\t/go
> /src/github.com/wildfly/wildfly-operator/pkg/resources/actions.go:37\ngithub.com/wildfly/wildfly-operator/pkg/resources
> /services.CreateOrUpdateLoadBalancerService\n\t/go/src/github.com/wildfly/wildfly-operator/pkg/resources/services/service.go:63\ngithub.com
> /wildfly/wildfly-operator/pkg/controller/wildflyserver.(*ReconcileWildFlyServer).Reconcile\n\t/go/src/github.com/wildfly/wildfly-operator
> /pkg/controller/wildflyserver/wildflyserver_controller.go:195\nsigs.k8s.io/controller-runtime/pkg/internal/controller.
> (*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.1.12/pkg/internal/controller/controller.go:215\nsigs.k8s.io
> /controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime(a)v0.1.12/pkg/internal/controller
> /controller.go:158\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20190221213512-86fb29eff628
> /pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/pkg/mod/k8s.io
> /apimachinery@v0.0.0-20190221213512-86fb29eff628/pkg/util/wait/wait.go:134\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/go/pkg/mod/k8s.io
> /apimachinery@v0.0.0-20190221213512-86fb29eff628/pkg/util/wait/wait.go:88"}
> {noformat}
> The error message appears every time during project creation, it can be reproduced using the latest upstream (dd5a057) operator and provided quickstart-cr.yaml example.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-12730) Move inner class org.jboss.as.webservices.util.SubjectUtil$SimpleGroup to outter level
by Jim Ma (Jira)
[ https://issues.jboss.org/browse/WFLY-12730?page=com.atlassian.jira.plugin... ]
Jim Ma updated WFLY-12730:
--------------------------
Summary: Move inner class org.jboss.as.webservices.util.SubjectUtil$SimpleGroup to outter level (was: JBossWS tests UsernameAuthorizationTestCase & UsernameAuthorizationDigestTestCase fail with elytron profile after ugrade to CXF 3.3.x in WFLY)
> Move inner class org.jboss.as.webservices.util.SubjectUtil$SimpleGroup to outter level
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12730
> URL: https://issues.jboss.org/browse/WFLY-12730
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 18.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> The WS-Security Policy tests org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationTestCase and org.jboss.test.ws.jaxws.samples.wsse.policy.jaas.UsernameAuthorizationDigestTestCase fail when running testsuite with elytron profile (server security configured via elytron subsystem). These failures after CXF upgrades to 3.3.x in WFLY.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month