October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1888) Review Context Association

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1888?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1888: ---------------------------------- Priority: Critical (was: Major) > Review Context Association > -------------------------- > > Key: ELY-1888 > URL: https://issues.jboss.org/browse/ELY-1888 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, MicroProfile > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 2.0.0.Alpha5 > > > Our APIs are very much written for objects to be associated with the current Thread and to remain associated either until they are replaced or the call stack returns to the point where association occurs and the association is automatically removed. > Concurrent APIs are always a problem in this area as a "request" can now traverse multiple Threads, issues arise in relation to propagation to worker threads but also potentially in the association for any resulting callbacks / resumption of work across different threads. > We should double check our relationship with Jakarta Concurrency: - > https://projects.eclipse.org/projects/ee4j.cu > The following specification within MicroProfile is looking into some mechanisms for this association: - > https://github.com/eclipse/microprofile-context-propagation > It may be preferable for our APIs to remain unchanged but instead we provide sufficient integration to capture our current context specific instances and propagate them. > As we have more than one item that can be associated we may want to review if we want to use a single context internally that associates multiple items so we only have one item to propagate. > Generally the items we associate are immutable so cross Thread modifications are not likely to be an issue. > Alternatively we may choose to revisit our association APIs. > Overall creating this issue for now as it is an area we will need to investigate further and plan for - tentatively scheduled against 2.0 although I suspect we will need to handle this within a 1.x release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Daniele Zonca reassigned DROOLS-4625: ------------------------------------- Assignee: Elizabeth Clayton (was: Tao Zhu) > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4625: -------------------------------- Description: As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. was: As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4625: -------------------------------- Tester: Anna Dupliak (was: Klara Kufova) > Scenario Test: UX for background data error reporting > ----------------------------------------------------- > > Key: DROOLS-4625 > URL: https://issues.jboss.org/browse/DROOLS-4625 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Jozef Marko > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4625: ----------------------------------- Summary: Scenario Test: UX for background data error reporting Key: DROOLS-4625 URL: https://issues.jboss.org/browse/DROOLS-4625 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Jozef Marko Assignee: Tao Zhu As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4624) Accumulate doesn't get modified and parsed to double String correctly

by Almas Toimbekov (Jira)

Almas Toimbekov created DROOLS-4624: --------------------------------------- Summary: Accumulate doesn't get modified and parsed to double String correctly Key: DROOLS-4624 URL: https://issues.jboss.org/browse/DROOLS-4624 Project: Drools Issue Type: Bug Environment: 7.27.0.Final Reporter: Almas Toimbekov Assignee: Mario Fusco I have to sum one field on all objects of "Resource" class. And I found out that accumulate's behavior is odd when before accumulating I am modifying that field. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4407) Cannot configure Elytron security domain using embedded server in admin mode

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4407?page=com.atlassian.jira.plugi... ] Yeray Borges resolved WFCORE-4407. ---------------------------------- Fix Version/s: 10.0.0.Beta2 (was: 11.0.0.Beta1) Resolution: Done > Cannot configure Elytron security domain using embedded server in admin mode > ---------------------------------------------------------------------------- > > Key: WFCORE-4407 > URL: https://issues.jboss.org/browse/WFCORE-4407 > Project: WildFly Core > Issue Type: Bug > Components: Embedded > Environment: > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > Fix For: 10.0.0.Beta2 > > > There are some configurations that are impossible to do using the embedded server, for example, we cannot create a security domain in Elytron that references a security domain in the security subsystem: > {noformat} > embed-server --server-config=standalone-full-ha.xml --std-out=echo > /subsystem=security/security-domain=my-sec-domain:add(cache-type=default) > /subsystem=security/security-domain=my-sec-domain/authentication=classic:add(login-modules=[{code=RealmUsersRoles, flag=required, module=RealmUsersRoles, module-options=[("usersProperties"=>"usersProperties"),("rolesProperties"=>"rolesProperties")]}]) > /subsystem=security/elytron-realm=my-sec-domain:add(legacy-jaas-config=my-sec-domain) > /subsystem=elytron/security-domain=my-sec-domain:add(realms=[{realm=my-sec-domain}],default-realm=my-sec-domain,permission-mapper=default-permission-mapper) > stop-embedded-server > {noformat} > The execution of these operations in an embedded server running in admin-mode throws the following error: > {noformat} > [standalone@embedded /] /subsystem=elytron/security-domain=my-sec-domain:add(realms=[{realm=my-sec-domain}],default-realm=my-sec-domain,permission-mapper=default-permission-mapper) > 12:30:53,429 ERROR [org.jboss.as.controller.management-operation] (pool-3-thread-1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "my-sec-domain") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.my-sec-domain"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.my-sec-domain.initial is missing [org.wildfly.security.security-realm.my-sec-domain]"] > } > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.my-sec-domain"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.my-sec-domain.initial is missing [org.wildfly.security.security-realm.my-sec-domain]"] > }, > "rolled-back" => true > } > {noformat} > The problem here is Elytron security domain services cannot be up because they require the legacy installed realm services, which are not up when we are using embedded in admin-only mode. > The SecurityDomain advertises no runtime operation, if no services are installed that would ever depend on security domain we may be able to skip installing some of these services entirely and allow their configuration in embedded / admin-only. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4381) BigDecimal and primitive comparison error in executable-model build

by Daniel Rosa (Jira)

[ https://issues.jboss.org/browse/DROOLS-4381?page=com.atlassian.jira.plugi... ] Daniel Rosa commented on DROOLS-4381: ------------------------------------- There's a misspelling on the pull request. Instead of 4381, it is written 4831 as it follows: DROOLS-4376] [DROOLS-4377] [DROOLS-4831] (#2490) The commit related to this issue can be found here: https://github.com/kiegroup/drools/commit/e1a2be044c64a67ffd89be7bdfd7247... > BigDecimal and primitive comparison error in executable-model build > ------------------------------------------------------------------- > > Key: DROOLS-4381 > URL: https://issues.jboss.org/browse/DROOLS-4381 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.24.0.Final > Reporter: Toshiya Kobayashi > Assignee: Luca Molteni > Priority: Major > Labels: support > > When you compare BigDecimal (but the field type is Object) with primitive int, > {noformat} > import org.drools.modelcompiler.domain.Result; > rule "rule1" > when > $r : Result( value <= 20 ) > then > end > {noformat} > executable-model build fails. > {noformat} > [ERROR] Failures: > [ERROR] CompilerTest.testBigDecimalIntCoercion:1901->BaseModelTest.getKieSession:99->BaseModelTest.getKieSession:103->BaseModelTest.getKieContainer:107->BaseModelTest.getKieContainer:114->BaseModelTest.createKieBuilder:125->BaseModelTest.createKieBuilder:152 [Message [id=1, level=ERROR, path=src/main/java/defaultpkg/RulesC992C95703C3473926B5B025D30097DARuleMethods0.java, line=24, column=122 > text=no suitable method found for lessOrEqualNumbers(java.lang.Object,int) > method org.drools.modelcompiler.util.EvaluationUtil.lessOrEqualNumbers(java.lang.Number,java.lang.Number) is not applicable > (argument mismatch; java.lang.Object cannot be converted to java.lang.Number) > method org.drools.modelcompiler.util.EvaluationUtil.lessOrEqualNumbers(java.lang.Long,java.lang.Long) is not applicable > (argument mismatch; java.lang.Object cannot be converted to java.lang.Long)], Message [id=2, level=ERROR, path=src/main/java/defaultpkg/RulesC992C95703C3473926B5B025D30097DARuleMethods0.java, line=0, column=0 > text=Java source of src/main/java/defaultpkg/RulesC992C95703C3473926B5B025D30097DARuleMethods0.java in error: > {noformat} > Non executable-model works with the rule. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4507) Ability to externally execute project defined tests.

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4507?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4507: --------------------------------------- [~Rikkola] Which API are you referring to? Btw here the requirement is to be able run a scesim file against a compiled kjar > Ability to externally execute project defined tests. > ---------------------------------------------------- > > Key: DROOLS-4507 > URL: https://issues.jboss.org/browse/DROOLS-4507 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Paul Brown > Assignee: Daniele Zonca > Priority: Major > > Provide the ability to externally invoke project define tests scenario i.e via a rest api. > This is required in order for project defined tests to be reused and executed as part of a delivery pipeline and not from within business central. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-235) ${JBOSS_HOME}/extensions/postconfigure.sh gets executed at server boot time, does not block

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFWIP-235?page=com.atlassian.jira.plugin.... ] Yeray Borges commented on WFWIP-235: ------------------------------------ >From Yesterday's conversation, it looks like this is not a bug and it is working as expected, [~mjurc] will close this if he agrees. > ${JBOSS_HOME}/extensions/postconfigure.sh gets executed at server boot time, does not block > ------------------------------------------------------------------------------------------- > > Key: WFWIP-235 > URL: https://issues.jboss.org/browse/WFWIP-235 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Michal Jurc > Assignee: Yeray Borges > Priority: Blocker > > {{$\{JBOSS_HOME\}/extensions/postconfigure.sh}} file does not get triggered before the boot of server is started and it does not block the current terminal session. > This is a change compared to previous behaviour. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019