March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10013) Upgrade WildFly Core to 5.0.0.Alpha1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10013?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10013: ------------------------------------ Component/s: Server (was: Domain Management) > Upgrade WildFly Core to 5.0.0.Alpha1 > ------------------------------------ > > Key: WFLY-10013 > URL: https://issues.jboss.org/browse/WFLY-10013 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Panagiotis Sotiropoulos > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3666) Provide Elytron alternative to RoleMappingLoginModule

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3666?page=com.atlassian.jira.plugi... ] Martin Choma edited comment on WFCORE-3666 at 3/13/18 1:01 PM: --------------------------------------------------------------- Adding customer case, where they use static mapping (DeploymentRoleToRolesMappingProvider in this case) #02049722 And there is another case #02049722 where they are missing this feature was (Author: mchoma): Adding customer case, where they use static mapping (DeploymentRoleToRolesMappingProvider in this case) > Provide Elytron alternative to RoleMappingLoginModule > ----------------------------------------------------- > > Key: WFCORE-3666 > URL: https://issues.jboss.org/browse/WFCORE-3666 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 4.0.0.Final > Reporter: Martin Choma > > In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron. > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3666) Provide Elytron alternative to RoleMappingLoginModule

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3666?page=com.atlassian.jira.plugi... ] Martin Choma updated WFCORE-3666: --------------------------------- > Provide Elytron alternative to RoleMappingLoginModule > ----------------------------------------------------- > > Key: WFCORE-3666 > URL: https://issues.jboss.org/browse/WFCORE-3666 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 4.0.0.Final > Reporter: Martin Choma > > In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron. > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3666) Provide Elytron alternative to RoleMappingLoginModule

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3666?page=com.atlassian.jira.plugi... ] Martin Choma updated WFCORE-3666: --------------------------------- Adding customer case, where they use static mapping (DeploymentRoleToRolesMappingProvider in this case) > Provide Elytron alternative to RoleMappingLoginModule > ----------------------------------------------------- > > Key: WFCORE-3666 > URL: https://issues.jboss.org/browse/WFCORE-3666 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 4.0.0.Final > Reporter: Martin Choma > > In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron. > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2383) Heartbeat example seems broken

by Jens Reimann (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2383?page=com.atlassian.jira.plugi... ] Jens Reimann commented on DROOLS-2383: -------------------------------------- Yes, you are right sorry. I did overlook that. > Heartbeat example seems broken > ------------------------------ > > Key: DROOLS-2383 > URL: https://issues.jboss.org/browse/DROOLS-2383 > Project: Drools > Issue Type: Bug > Affects Versions: 7.6.0.Final > Reporter: Jens Reimann > Assignee: Mario Fusco > > To me it looks as if the common heartbeat example is broken: > {code} > import foo.bar.Heartbeat > rule "Sound the alarm" > when > $h: Heartbeat( ) from entry-point "MonitoringStream" > not( Heartbeat( this != $h, this after[0s,10s] $h ) from entry-point "MonitoringStream" ) > then > System.out.println("Sound the alarm"); > end > {code} > When running the rule set with: > {code:java} > public class Application { > public static void main(final String[] args) { > final KieServices ks = KieServices.Factory.get(); > final KieBaseConfiguration config = ks.newKieBaseConfiguration(); > config.setOption(EventProcessingOption.STREAM); > final KieContainer kContainer = ks.getKieClasspathContainer(); > final KieBase kBase = kContainer.getKieBase("rules"); > final KieSession kSession = kBase.newKieSession(); > kSession.getEntryPoint("MonitoringStream").insert(new Heartbeat()); > kSession.fireUntilHalt(); > } > } > {code} > Results in: > {code} > 11:55:55.092 [main] DEBUG org.drools.compiler.kie.builder.impl.ClasspathKieProject - Found and used pom.properties /home/jreimann/Development/iot-kura-develop-oxygen/ws/drools-test-1/target/classes/META-INF/maven/de.dentrassi.test/drools-test-1/pom.properties > 11:55:55.095 [main] DEBUG org.drools.compiler.kie.builder.impl.ClasspathKieProject - Discovered classpath module de.dentrassi.test:drools-test-1:0.0.1-SNAPSHOT > 11:55:55.098 [main] INFO org.drools.compiler.kie.builder.impl.KieRepositoryImpl - KieModule was added: FileKieModule[releaseId=de.dentrassi.test:drools-test-1:0.0.1-SNAPSHOT,file=/home/jreimann/Development/iot-kura-develop-oxygen/ws/drools-test-1/target/classes] > 11:55:55.820 [main] DEBUG org.drools.core.common.DefaultAgenda - State was INACTIVE is now FIRING_UNTIL_HALT > Sound the alarm > 11:55:55.850 [main] DEBUG org.drools.core.common.DefaultAgenda - State was FIRING_UNTIL_HALT is now INACTIVE_ON_FIRING_UNTIL_HALT > {code} > Which looks to me as if the alarm gets activated right away instead of 10 seconds after. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector

by Nagaraju Chitimilla (JIRA)

Nagaraju Chitimilla created WFLY-10014: ------------------------------------------ Summary: Unable to configure comma delimited enabled-protocols in remote-connector Key: WFLY-10014 URL: https://issues.jboss.org/browse/WFLY-10014 Project: WildFly Issue Type: Bug Affects Versions: 12.0.0.Final Reporter: Nagaraju Chitimilla Assignee: Jason Greene Priority: Critical When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector {noformat} <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/> {noformat} But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails: {code:java} Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12 at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205) at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342) ... 18 more {code} I set this as critical as it prevent setting more then one allowed SSLContext protocol. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2383) Heartbeat example seems broken

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2383?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2383. --------------------------------- Resolution: Rejected You're creating a KieBaseConfiguration enabling the stream mode, but never using it. You should use the method {code} kieContainer.newKieBase(String kBaseName, KieBaseConfiguration conf) {code} > Heartbeat example seems broken > ------------------------------ > > Key: DROOLS-2383 > URL: https://issues.jboss.org/browse/DROOLS-2383 > Project: Drools > Issue Type: Bug > Affects Versions: 7.6.0.Final > Reporter: Jens Reimann > Assignee: Mario Fusco > > To me it looks as if the common heartbeat example is broken: > {code} > import foo.bar.Heartbeat > rule "Sound the alarm" > when > $h: Heartbeat( ) from entry-point "MonitoringStream" > not( Heartbeat( this != $h, this after[0s,10s] $h ) from entry-point "MonitoringStream" ) > then > System.out.println("Sound the alarm"); > end > {code} > When running the rule set with: > {code:java} > public class Application { > public static void main(final String[] args) { > final KieServices ks = KieServices.Factory.get(); > final KieBaseConfiguration config = ks.newKieBaseConfiguration(); > config.setOption(EventProcessingOption.STREAM); > final KieContainer kContainer = ks.getKieClasspathContainer(); > final KieBase kBase = kContainer.getKieBase("rules"); > final KieSession kSession = kBase.newKieSession(); > kSession.getEntryPoint("MonitoringStream").insert(new Heartbeat()); > kSession.fireUntilHalt(); > } > } > {code} > Results in: > {code} > 11:55:55.092 [main] DEBUG org.drools.compiler.kie.builder.impl.ClasspathKieProject - Found and used pom.properties /home/jreimann/Development/iot-kura-develop-oxygen/ws/drools-test-1/target/classes/META-INF/maven/de.dentrassi.test/drools-test-1/pom.properties > 11:55:55.095 [main] DEBUG org.drools.compiler.kie.builder.impl.ClasspathKieProject - Discovered classpath module de.dentrassi.test:drools-test-1:0.0.1-SNAPSHOT > 11:55:55.098 [main] INFO org.drools.compiler.kie.builder.impl.KieRepositoryImpl - KieModule was added: FileKieModule[releaseId=de.dentrassi.test:drools-test-1:0.0.1-SNAPSHOT,file=/home/jreimann/Development/iot-kura-develop-oxygen/ws/drools-test-1/target/classes] > 11:55:55.820 [main] DEBUG org.drools.core.common.DefaultAgenda - State was INACTIVE is now FIRING_UNTIL_HALT > Sound the alarm > 11:55:55.850 [main] DEBUG org.drools.core.common.DefaultAgenda - State was FIRING_UNTIL_HALT is now INACTIVE_ON_FIRING_UNTIL_HALT > {code} > Which looks to me as if the alarm gets activated right away instead of 10 seconds after. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2379) DMN Validator raising false positive errors for type resolution

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2379?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-2379: --------------------------------------- Tests added with https://github.com/etirelli/drools/pull/7 > DMN Validator raising false positive errors for type resolution > --------------------------------------------------------------- > > Key: DROOLS-2379 > URL: https://issues.jboss.org/browse/DROOLS-2379 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Priority: Critical > Fix For: 7.7.0.Final > > > DMN Validator is raising false positives for errors on type resolution. It looks like it is happening since the following commit was done: > https://github.com/kiegroup/drools/commit/9e2fdc4b5e83bb9b5350a37fd89dab8... > The problem is that the .toString() call on the QName will return the full name, including the namespace: > {http://www.trisotech.com/definitions/_6cfe7d88-6741-45d1-968c-b61a597d0964}tDailyPrice > And that will always fail the constraint: > ItemDefinition( name == $typeRef.toString() ) > I believe the correct would be to change the constraint to: > ItemDefinition( name == $typeRef.getLocalPart() ) > But we might also need to check the namespace somehow. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2379) DMN Validator raising false positive errors for type resolution

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2379?page=com.atlassian.jira.plugi... ] Tibor Zimányi reassigned DROOLS-2379: ------------------------------------- Assignee: Edson Tirelli (was: Tibor Zimányi) > DMN Validator raising false positive errors for type resolution > --------------------------------------------------------------- > > Key: DROOLS-2379 > URL: https://issues.jboss.org/browse/DROOLS-2379 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Priority: Critical > Fix For: 7.7.0.Final > > > DMN Validator is raising false positives for errors on type resolution. It looks like it is happening since the following commit was done: > https://github.com/kiegroup/drools/commit/9e2fdc4b5e83bb9b5350a37fd89dab8... > The problem is that the .toString() call on the QName will return the full name, including the namespace: > {http://www.trisotech.com/definitions/_6cfe7d88-6741-45d1-968c-b61a597d0964}tDailyPrice > And that will always fail the constraint: > ItemDefinition( name == $typeRef.toString() ) > I believe the correct would be to change the constraint to: > ItemDefinition( name == $typeRef.getLocalPart() ) > But we might also need to check the namespace somehow. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2385) CCE when modifying a Nested declared type during an incremental update

by Martin Weiler (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2385?page=com.atlassian.jira.plugi... ] Martin Weiler updated DROOLS-2385: ---------------------------------- Description: When using nested facts, a ClassCastException is thrown after updateToVersion(). See PR for a test case demonstrating the problem. Affects Version/s: 7.6.0.Final > CCE when modifying a Nested declared type during an incremental update > ---------------------------------------------------------------------- > > Key: DROOLS-2385 > URL: https://issues.jboss.org/browse/DROOLS-2385 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.6.0.Final > Reporter: Vishal Soni > Assignee: Edson Tirelli > > When using nested facts, a ClassCastException is thrown after updateToVersion(). See PR for a test case demonstrating the problem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 March 2018