October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1746) API changes review for Drools Core

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1746?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1746: --------------------------------------- This is quite interesting [~lvc], but we consider the drools-core jar as an internal API. We are going through refactorings to clean up and modernize the API in there, so changes are expected. Our public API is on the kie-api.jar (https://github.com/kiegroup/droolsjbpm-knowledge/tree/master/kie-api). That is where we are very sensitive about API changes and backward compatibility. If you could run a similar analysis on it, it would be quite interesting to see. /cc [~mark.proctor] > API changes review for Drools Core > ---------------------------------- > > Key: DROOLS-1746 > URL: https://issues.jboss.org/browse/DROOLS-1746 > Project: Drools > Issue Type: Enhancement > Reporter: Andrey V. Ponomarenko > Assignee: Edson Tirelli > Attachments: drools-core-1.png, drools-core-2.png > > > The review of API changes for the Drools Core library since 6.3.0 version: https://abi-laboratory.pro/java/tracker/timeline/drools-core/ > Hope it will be helpful for users and maintainers of the library. > The report is generated by the https://github.com/lvc/japi-tracker tool for jars found at http://central.maven.org/maven2/org/drools/drools-core/ according to https://wiki.eclipse.org/Evolving_Java-based_APIs_2. > Thank you. > !drools-core-2.png|API symbols timeline! > !drools-core-1.png|API changes review! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1730) Cyclic information requirement generates a stackoverflow

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1730?page=com.atlassian.jira.plugi... ] Fedor Gavrilov reassigned DROOLS-1730: -------------------------------------- Assignee: Fedor Gavrilov (was: Edson Tirelli) > Cyclic information requirement generates a stackoverflow > -------------------------------------------------------- > > Key: DROOLS-1730 > URL: https://issues.jboss.org/browse/DROOLS-1730 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Fedor Gavrilov > > If you have Decision A -> Decision B -> Decision A this causes a stackoverflow when executing it at org.kie.dmn.core.impl.DMNRuntimeImpl.evaluateDecision(DMNRuntimeImpl.java:282) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1375) Digest auth uses single use nonces with no Authentication-Info header

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/ELY-1375?page=com.atlassian.jira.plugin.s... ] Jan Stourac commented on ELY-1375: ---------------------------------- Just for the record - [here is the related PR|https://github.com/wildfly-security/wildfly-elytron/pull/995]. > Digest auth uses single use nonces with no Authentication-Info header > --------------------------------------------------------------------- > > Key: ELY-1375 > URL: https://issues.jboss.org/browse/ELY-1375 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Blocker > > The results in every single request being retried -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1380) Calling getNegotiatedProperty for Elytron SASL mechanisms doesn't throw IllegalStateException when negotiatition is not completed

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1380?page=com.atlassian.jira.plugin.s... ] Jan Kalina moved JBEAP-13360 to ELY-1380: ----------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1380 (was: JBEAP-13360) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: SASL (was: Security) Affects Version/s: 1.2.0.Beta4 (was: 7.1.0.CR2) > Calling getNegotiatedProperty for Elytron SASL mechanisms doesn't throw IllegalStateException when negotiatition is not completed > --------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1380 > URL: https://issues.jboss.org/browse/ELY-1380 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.2.0.Beta4 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > > The Elytron SASL mechanism implementations don't throw {{IllegalStateException}} when calling the {{getNegotiatedProperty()}} method before the negotiation is finished. > The contract of the {{Object javax.security.sasl.SaslClient.getNegotiatedProperty(String propName)}} says: > bq. Retrieves the negotiated property. This method can be called only after the authentication exchange has completed (i.e., when isComplete() returns true); otherwise, an IllegalStateException is thrown. > The same is valid for the {{SaslServer}} interface. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1379) KeyStore element does not support overriding Provider discovery

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1379: ------------------------------------- Summary: KeyStore element does not support overriding Provider discovery Key: ELY-1379 URL: https://issues.jboss.org/browse/ELY-1379 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 Additionally it doesn't take into account the default Provider discovery or the Provider definition at the root of the <authentication-configuration /> definition. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1378) KeyStore resource does not support specifying the module

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1378: ------------------------------------- Summary: KeyStore resource does not support specifying the module Key: ELY-1378 URL: https://issues.jboss.org/browse/ELY-1378 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta5 In other areas of the authentication configuration where the ClassLoader is used we allow an optional module to be specified, we don't do this for <keyStore><resource/><keyStore> which only accepts a name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.

by Walter Medvedeo (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ] Walter Medvedeo edited comment on DROOLS-1748 at 10/4/17 8:54 AM: ------------------------------------------------------------------ For domain installations the following additional configurations are required. # the profile name that is being used, e.g. full, default, etc. datasource.management.wildfly.profile=full # the server group name to which the current kie-wb installation belongs. e.g: datasource.management.wildfly.serverGroup=primary-server-group # Internal kie-wb component configuration for domain configurations datasource.management.DefChangeHandler=DomainModeChangeHandler The profile and serverGroup name to use can be found in the hosts.xml configuration file in a section like this: <server-groups> <server-group name="primary-server-group" profile="full"> <jvm name="default"> <heap size="1000m" max-size="1000m"/> </jvm> <socket-binding-group ref="full-sockets"/> <deployments> <deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/> </deployments> </server-group> All this 3 mentioned properties must be added to the datasource-management.properties file found in the: kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties was (Author: wmedvede): For domain installations the following additional configurations are required. # the profile name that is being used, e.g. full, default, etc. datasource.management.wildfly.profile=full # the server group name to with the current kie-wb installation belongs. e.g: datasource.management.wildfly.serverGroup=primary-server-group # Internal kie-wb component configuration for domain configurations datasource.management.DefChangeHandler=DomainModeChangeHandler The profile and serverGroup name can be found in the hosts.xml configuration file in a section like this: <server-groups> <server-group name="primary-server-group" profile="full"> <jvm name="default"> <heap size="1000m" max-size="1000m"/> </jvm> <socket-binding-group ref="full-sockets"/> <deployments> <deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/> </deployments> </server-group> All this 3 mentioned properties should added to the datasource-management.properties file found in the: kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties > Drools workbench datasource on Wildfly domain. > ---------------------------------------------- > > Key: DROOLS-1748 > URL: https://issues.jboss.org/browse/DROOLS-1748 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.Final, 7.3.0.Final > Environment: Drools workbench on Wildfly domain cluster > Reporter: M C > Assignee: Petr Široký > Priority: Critical > > After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source. > [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")] > Problem does not affect Wildfly standalone configuration, only domain configuration using profiles. > WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/... > In standalone syntax is: /subsystem=datasource/. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1748) Drools workbench datasource on Wildfly domain.

by Walter Medvedeo (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1748?page=com.atlassian.jira.plugi... ] Walter Medvedeo commented on DROOLS-1748: ----------------------------------------- For domain installations the following additional configurations are required. # the profile name that is being used, e.g. full, default, etc. datasource.management.wildfly.profile=full # the server group name to with the current kie-wb installation belongs. e.g: datasource.management.wildfly.serverGroup=primary-server-group # Internal kie-wb component configuration for domain configurations datasource.management.DefChangeHandler=DomainModeChangeHandler The profile and serverGroup name can be found in the hosts.xml configuration file in a section like this: <server-groups> <server-group name="primary-server-group" profile="full"> <jvm name="default"> <heap size="1000m" max-size="1000m"/> </jvm> <socket-binding-group ref="full-sockets"/> <deployments> <deployment name="kie-wb-7.0.0-SNAPSHOT-eap7.war" runtime-name="kie-wb-7.0.0-SNAPSHOT-eap7.war"/> </deployments> </server-group> All this 3 mentioned properties should added to the datasource-management.properties file found in the: kie-wb-7.0.0.Final-wildfly10.war/WEB-INF/classes/datasource-management.properties > Drools workbench datasource on Wildfly domain. > ---------------------------------------------- > > Key: DROOLS-1748 > URL: https://issues.jboss.org/browse/DROOLS-1748 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.Final, 7.3.0.Final > Environment: Drools workbench on Wildfly domain cluster > Reporter: M C > Assignee: Petr Široký > Priority: Critical > > After starting workbench war (version 7.3 and 7.0, both Final) on Wildfly 10.1 domain cluster, got the issues with data source. > [Server:server-one] 13:09:07,908 WARN [org.kie.workbench.common.screens.datasource.management.backend.DataSourceManagementBootstrap] (pool-14-thread-1) Initialize deployments task finished with errors: operation execution failed. :WFLYCTL0030: No resource definition is registered for address [("subsystem" => "datasources")] > Problem does not affect Wildfly standalone configuration, only domain configuration using profiles. > WFLYCTL0030 warning says the syntax problem using jboss-cli.sh. In domain cluster it's used /profile=full-ha/subsystem=datasource/... > In standalone syntax is: /subsystem=datasource/. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9417) No default-response-code during deployment sent

by Nero M (JIRA)

Nero M created WFLY-9417: ---------------------------- Summary: No default-response-code during deployment sent Key: WFLY-9417 URL: https://issues.jboss.org/browse/WFLY-9417 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 11.0.0.CR1 Reporter: Nero M Assignee: Stuart Douglas Fix For: 11.0.0.Final Hi, i am experiencing a strange behaviour with WF11 which was not like this on WF10. When a *.dodeploy file exists during server-start. The Default response code e.g. <host name="default-host" alias="localhost" default-response-code="503"> Is not sent during the time of deployment. Instead any requests goes into a pending state with (seemingly) no timeout. If the *.dodeploy file is created AFTER the server boots up, the default response code is sent until the deployment is complete. (After this line): WFLYSRV0025: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.4.Final) started in 6468ms I think the server should not "hang" during the deployment-time, just like it was on WF10. Is there anything which has to be changed in the standalone xml between 10 and 11 to get the same behaviour? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9375) META-INF/services are always accessible from dependencies

by Alexander Kudrevatykh (JIRA)

[ https://issues.jboss.org/browse/WFLY-9375?page=com.atlassian.jira.plugin.... ] Alexander Kudrevatykh commented on WFLY-9375: --------------------------------------------- Can I guess that It will be added in something like 11.1.0 or in 10.2.0 releases? > META-INF/services are always accessible from dependencies > --------------------------------------------------------- > > Key: WFLY-9375 > URL: https://issues.jboss.org/browse/WFLY-9375 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final, 10.1.0.Final, 11.0.0.CR1 > Reporter: Alexander Kudrevatykh > Assignee: Stuart Douglas > > I found regression in Wildfly 10.1 (10.0 and 11 CR1 also affected) - META-INF/services entries are accesible from war dependencies, even if not marked as "import" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 2017