June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13592) jndi-view doen't show values for EJB in java:jboss/exported

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13592?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13592: ------------------------------------ Summary: jndi-view doen't show values for EJB in java:jboss/exported (was: [GSS] (7.3.z) jndi-view doen't show values for EJB in java:jboss/exported) > jndi-view doen't show values for EJB in java:jboss/exported > ------------------------------------------------------------ > > Key: WFLY-13592 > URL: https://issues.redhat.com/browse/WFLY-13592 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Reporter: Parul Sharma > Assignee: Parul Sharma > Priority: Major > Fix For: 21.0.0.Beta1 > > > jndi-view() show values as '?' for EJB on java:jboss/exported tree. > These values could be seen on EAP 6.4. > This can be reproduced on EAP 7.3.1 and 7.2.8. > I attached a reproducer and these results as follows. > reproducer.zip > jndi_view_result_731.txt > jndi_view_result_6422.txt > > EAP 7.3.1 / 7.2.8 > {code} > [standalone@localhost:9990 /] /subsystem=naming:jndi-view() > ... > "java:jboss/exported" => { > "ejb2-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB!com.example.GreeterEJBHome" => { > "class-name" => "java.lang.Object", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJBRemote" => { > "class-name" => "java.lang.Object", > "value" => "?" > } > } > }, > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => {"GreeterEJB!com.example.GreeterRemote" => { > "class-name" => "java.lang.Object", > "value" => "?" > }} > } > }, > {code} > > EAP 6.4 > {code} > "java:jboss/exported" => { > "ejb2-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB!com.example.GreeterEJBHome" => { > "class-name" => "com.example.GreeterEJBHome", > "value" => "Proxy for remote EJB EJBHomeLocator{appName='', moduleName='ejb2-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterEJBHome'}" > }, > "GreeterEJB!com.example.GreeterEJBRemote" => { > "class-name" => "com.example.GreeterEJBRemote", > "value" => "Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='ejb2-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterEJBRemote'}" > } > } > }, > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => {"GreeterEJB!com.example.GreeterRemote" => { > "class-name" => "com.example.GreeterRemote", > "value" => "Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='ejb3-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterRemote'}" > }} > } > }, > {code} > > Additionally, > If EJB3 doesn't have @Remote, values are '?' in 'java:global' and 'java:app' similarly. > The following behaviour is not changed from 6.4. But it seems a sililar behavir as the above. > I attached the reproducer and these results as follows. > reproducer_without_remote_if.zip > jndi_view_result_no_remoteif_731.txt > jndi_view_result_no_remoteif_6422.txt > EAP 7.3.1 > {code} > "java:global" => { > ... > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > } > } > } > } > }, > "applications" => { > "ejb3-1.0.jar" => { > "java:app" => { > ... > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > } > } > } > }, > "modules" => undefined > }, > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13594) Upgrade Artemis Native to 1.0.2

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13594?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-13594. ------------------------------------- Resolution: Duplicate Issue > Upgrade Artemis Native to 1.0.2 > ------------------------------- > > Key: WFLY-13594 > URL: https://issues.redhat.com/browse/WFLY-13594 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 20.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Because of a fix in the kernel, libaio is now returning duplicate events -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5451) Upgrade pmml-model version

by Donato Marrazzo (Jira)

[ https://issues.redhat.com/browse/DROOLS-5451?page=com.atlassian.jira.plug... ] Donato Marrazzo commented on DROOLS-5451: ----------------------------------------- Hi [~jomarko] I attached a pmml 4.4 [^logistic.pmml] here the spec: [http://dmg.org/pmml/v4-4/GeneralStructure.html] > Upgrade pmml-model version > -------------------------- > > Key: DROOLS-5451 > URL: https://issues.redhat.com/browse/DROOLS-5451 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: logistic.pmml > > > Current org.jpmml:pmml-model version inside kie-parent pom.xml is 1.4.11, > that does not support PMML version 4.4 > > Upgrade it to last version 1.5.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5451) Upgrade pmml-model version

by Donato Marrazzo (Jira)

[ https://issues.redhat.com/browse/DROOLS-5451?page=com.atlassian.jira.plug... ] Donato Marrazzo updated DROOLS-5451: ------------------------------------ Attachment: logistic.pmml > Upgrade pmml-model version > -------------------------- > > Key: DROOLS-5451 > URL: https://issues.redhat.com/browse/DROOLS-5451 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: logistic.pmml > > > Current org.jpmml:pmml-model version inside kie-parent pom.xml is 1.4.11, > that does not support PMML version 4.4 > > Upgrade it to last version 1.5.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13618) Upgrade WildFly Core 13.0.0.Beta1

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13618?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13618: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Upgrade WildFly Core 13.0.0.Beta1 > --------------------------------- > > Key: WFLY-13618 > URL: https://issues.redhat.com/browse/WFLY-13618 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 21.0.0.Beta1 > > > Tag + Release Notes: https://github.com/wildfly/wildfly-core/releases/tag/13.0.0.Beta1 > Diff to previous integrated version: https://github.com/wildfly/wildfly-core/compare/12.0.1.Final...13.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5454) Please bring back the IDE-based 'Guided Rule Editor'

by Edson Tirelli (Jira)

[ https://issues.redhat.com/browse/DROOLS-5454?page=com.atlassian.jira.plug... ] Edson Tirelli commented on DROOLS-5454: --------------------------------------- Please note that Code Ready Studio and Code Ready Workspaces are different tools. We are targeting Code Ready Workspaces. [https://developers.redhat.com/products/codeready-workspaces/overview] At the moment there are no plans to support the Guided Rules Editor on VS Code/Code Ready Workspaces. For the Guided Rules Editor, our solution continues to be based on Business Central. The alternate solution I mentioned above focus on higher level, open standards, like DMN and BPMN. These plugins are available in VS Code store already, and will be made available on Code Ready Workspaces as soon as Code Ready Workspaces adds support for the latest web editors API, that was recently published by the VS Code team. [https://medium.com/kie-foundation/we-are-on-vs-code-store-35280693573c] [https://porcelli.me/announcement/tooling/vscode/store/bpmn/dmn/2020/06/10...] > Please bring back the IDE-based 'Guided Rule Editor' > ---------------------------------------------------- > > Key: DROOLS-5454 > URL: https://issues.redhat.com/browse/DROOLS-5454 > Project: Drools > Issue Type: Feature Request > Components: eclipse plugin > Affects Versions: 7.39.0.Final > Reporter: Rick Wagner > Assignee: Edson Tirelli > Priority: Major > > JBoss Rules users have had access to an Eclipse/DevStudio plugin called the "Guided Rules Editor". It has been removed or replaced by non-IDE solutions. This is disappointing to some users who have business processes, training, etc. based around the plugin version. > > Please bring back the Guided Rule Editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1994) Ensure the Elytron build works on Java 14

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-1994?page=com.atlassian.jira.plugin.... ] Sonia Zaldana edited comment on ELY-1994 at 6/26/20 11:41 AM: -------------------------------------------------------------- The impact is mainly related to _java.security.acl.Group_. Overview: * _TestLoginModule.java_: A _Group_ implementation is used in the tests to store the caller principal. * _JaasSecurityRealm.java_: _JaasSecurityRealm#getCallerPrincipal_ looks for a _Group_ and returns the first principal in the group. The _java.security.acl_ package has been replaced with _java.security.policy_ ([https://docs.oracle.com/javase/7/docs/api/java/security/Policy.html)|http... I don't see a straightforward way to switch to the alternative. was (Author: szaldana): The impact is mainly related to _java.security.acl.Group_. Overview: * _TestLoginModule.java_: A _Group_ implementation is used in the tests to store the caller principal. * _JaasSecurityRealm.java_: _JaasSecurityRealm#getCallerPrincipal_ looks for a _Group_ and returns the first principal in the group. The _java.security.acl_ package has been replaced with j_ava.security.policy_ ([https://docs.oracle.com/javase/7/docs/api/java/security/Policy.html)|http... I don't see a straightforward way to switch to the alternative. > Ensure the Elytron build works on Java 14 > ----------------------------------------- > > Key: ELY-1994 > URL: https://issues.redhat.com/browse/ELY-1994 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2 > > > Overall the build is not doing too badly and doesn't fail until we get to the main testsuite. > > {code:java} > [INFO] WildFly Elytron - Tests ............................ FAILURE [ 1.447 s] > [INFO] WildFly Elytron .................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:46 min > [INFO] Finished at: 2020-06-11T11:25:23+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0-jboss-1:testCompile (default-testCompile) on project wildfly-elytron-tests: Compilation failure: Compilation failure: > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[31,25] package java.security.acl does not exist > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[107,40] cannot find symbol > [ERROR] symbol: class Group > [ERROR] location: class org.wildfly.security.auth.TestLoginModule > [ERROR] -> [Help 1] {code} > If this is all that is failing for us maybe we can revisit the test and see how appropriate it is and if it can be adapted to use available APIs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1994) Ensure the Elytron build works on Java 14

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-1994?page=com.atlassian.jira.plugin.... ] Sonia Zaldana edited comment on ELY-1994 at 6/26/20 11:41 AM: -------------------------------------------------------------- The impact is mainly related to _java.security.acl.Group_. Overview: * _TestLoginModule.java_: A _Group_ implementation is used in the tests to store the caller principal. * _JaasSecurityRealm.java_: _JaasSecurityRealm#getCallerPrincipal_ looks for a _Group_ and returns the first principal in the group. The _java.security.acl_ package has been replaced with j_ava.security.policy_ ([https://docs.oracle.com/javase/7/docs/api/java/security/Policy.html)|http... I don't see a straightforward way to switch to the alternative. was (Author: szaldana): The impact is mainly related to _java.security.acl.Group_. Overview: * _TestLoginModule.java_: A _Group_ implementation is used in the tests to store the caller principal. * _JaasSecurityRealm.java_: _JaasSecurityRealm#getCallerPrincipal_ looks for a _Group_ and returns the first principal in the group. The _java.security.acl_ package has been replaced with [java.security.policy|[https://docs.oracle.com/javase/7/docs/api/jav... but I don't see a straightforward way to switch to the alternative. > Ensure the Elytron build works on Java 14 > ----------------------------------------- > > Key: ELY-1994 > URL: https://issues.redhat.com/browse/ELY-1994 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2 > > > Overall the build is not doing too badly and doesn't fail until we get to the main testsuite. > > {code:java} > [INFO] WildFly Elytron - Tests ............................ FAILURE [ 1.447 s] > [INFO] WildFly Elytron .................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:46 min > [INFO] Finished at: 2020-06-11T11:25:23+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0-jboss-1:testCompile (default-testCompile) on project wildfly-elytron-tests: Compilation failure: Compilation failure: > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[31,25] package java.security.acl does not exist > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[107,40] cannot find symbol > [ERROR] symbol: class Group > [ERROR] location: class org.wildfly.security.auth.TestLoginModule > [ERROR] -> [Help 1] {code} > If this is all that is failing for us maybe we can revisit the test and see how appropriate it is and if it can be adapted to use available APIs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1994) Ensure the Elytron build works on Java 14

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-1994?page=com.atlassian.jira.plugin.... ] Sonia Zaldana commented on ELY-1994: ------------------------------------ The impact is mainly related to _java.security.acl.Group_. Overview: * _TestLoginModule.java_: A _Group_ implementation is used in the tests to store the caller principal. * _JaasSecurityRealm.java_: _JaasSecurityRealm#getCallerPrincipal_ looks for a _Group_ and returns the first principal in the group. The _java.security.acl_ package has been replaced with [java.security.policy|[https://docs.oracle.com/javase/7/docs/api/jav... but I don't see a straightforward way to switch to the alternative. > Ensure the Elytron build works on Java 14 > ----------------------------------------- > > Key: ELY-1994 > URL: https://issues.redhat.com/browse/ELY-1994 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2 > > > Overall the build is not doing too badly and doesn't fail until we get to the main testsuite. > > {code:java} > [INFO] WildFly Elytron - Tests ............................ FAILURE [ 1.447 s] > [INFO] WildFly Elytron .................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:46 min > [INFO] Finished at: 2020-06-11T11:25:23+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0-jboss-1:testCompile (default-testCompile) on project wildfly-elytron-tests: Compilation failure: Compilation failure: > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[31,25] package java.security.acl does not exist > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[107,40] cannot find symbol > [ERROR] symbol: class Group > [ERROR] location: class org.wildfly.security.auth.TestLoginModule > [ERROR] -> [Help 1] {code} > If this is all that is failing for us maybe we can revisit the test and see how appropriate it is and if it can be adapted to use available APIs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1994) Ensure the Elytron build works on Java 14

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-1994?page=com.atlassian.jira.plugin.... ] Sonia Zaldana reassigned ELY-1994: ---------------------------------- Assignee: (was: Sonia Zaldana) > Ensure the Elytron build works on Java 14 > ----------------------------------------- > > Key: ELY-1994 > URL: https://issues.redhat.com/browse/ELY-1994 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.13.0.CR2 > > > Overall the build is not doing too badly and doesn't fail until we get to the main testsuite. > > {code:java} > [INFO] WildFly Elytron - Tests ............................ FAILURE [ 1.447 s] > [INFO] WildFly Elytron .................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:46 min > [INFO] Finished at: 2020-06-11T11:25:23+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0-jboss-1:testCompile (default-testCompile) on project wildfly-elytron-tests: Compilation failure: Compilation failure: > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[31,25] package java.security.acl does not exist > [ERROR] /home/darranl/src/community/wildfly-elytron/tests/base/src/test/java/org/wildfly/security/auth/TestLoginModule.java:[107,40] cannot find symbol > [ERROR] symbol: class Group > [ERROR] location: class org.wildfly.security.auth.TestLoginModule > [ERROR] -> [Help 1] {code} > If this is all that is failing for us maybe we can revisit the test and see how appropriate it is and if it can be adapted to use available APIs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020