April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging

by Brad Maxwell (Jira)

[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFLY-10612: -------------------------------- Attachment: WFLY-10612.jar > Include EJB's IIOP Binding when EJB is deployed logging > ------------------------------------------------------- > > Key: WFLY-10612 > URL: https://issues.redhat.com/browse/WFLY-10612 > Project: WildFly > Issue Type: Enhancement > Components: IIOP > Affects Versions: 12.0.0.Final > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > Attachments: WFLY-10612.jar, java.policy > > > It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings. > <iiop enable-by-default="true" use-qualified-name="true"/> > {code} > INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > {code} > Something like this when use-qualified-name="true" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > iiop-eap7/HelloSessionBean > {code} > or use-qualified-name="false" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > HelloSessionBean > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging

by Brad Maxwell (Jira)

[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFLY-10612: -------------------------------- Attachment: java.policy > Include EJB's IIOP Binding when EJB is deployed logging > ------------------------------------------------------- > > Key: WFLY-10612 > URL: https://issues.redhat.com/browse/WFLY-10612 > Project: WildFly > Issue Type: Enhancement > Components: IIOP > Affects Versions: 12.0.0.Final > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > Attachments: WFLY-10612.jar, java.policy > > > It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings. > <iiop enable-by-default="true" use-qualified-name="true"/> > {code} > INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome > java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote > {code} > Something like this when use-qualified-name="true" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > iiop-eap7/HelloSessionBean > {code} > or use-qualified-name="false" > {code} > IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows: > HelloSessionBean > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-268) Upgrade jboss-modules to 1.10.1.Final

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-268?page=com.atlassian.jira.plugi... ] James Perkins updated LOGMGR-268: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/298, https://github.com/jboss-logging/jboss-logmanager/pull/299 (was: https://github.com/jboss-logging/jboss-logmanager/pull/298) > Upgrade jboss-modules to 1.10.1.Final > ------------------------------------- > > Key: LOGMGR-268 > URL: https://issues.redhat.com/browse/LOGMGR-268 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Components: core > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade {{org.jboss.modules:jboss-modules}} to 1.10.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-270) Upgrade jboss-parent to 36

by James Perkins (Jira)

James Perkins created LOGMGR-270: ------------------------------------ Summary: Upgrade jboss-parent to 36 Key: LOGMGR-270 URL: https://issues.redhat.com/browse/LOGMGR-270 Project: JBoss Log Manager Issue Type: Component Upgrade Components: core Reporter: James Perkins Upgrade jboss-parent to 36. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5248) DMN utility method for inspecting "root" leafs DRGElements

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5248?page=com.atlassian.jira.plug... ] Matteo Mortari deleted DROOLS-5248: ----------------------------------- > DMN utility method for inspecting "root" leafs DRGElements > ---------------------------------------------------------- > > Key: DROOLS-5248 > URL: https://issues.redhat.com/browse/DROOLS-5248 > Project: Drools > Issue Type: Task > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1123) 3Scale tests backport to 1.1

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1123?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan moved OSSM-181 to SWSQE-1123: -------------------------------------------- Project: Kiali QE (was: OpenShift Service Mesh) Key: SWSQE-1123 (was: OSSM-181) Workflow: classic default workflow (was: OpenShift Service Mesh - GitHub Workflow) > 3Scale tests backport to 1.1 > ---------------------------- > > Key: SWSQE-1123 > URL: https://issues.redhat.com/browse/SWSQE-1123 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-268) Upgrade jboss-modules to 1.10.1.Final

by James Perkins (Jira)

James Perkins created LOGMGR-268: ------------------------------------ Summary: Upgrade jboss-modules to 1.10.1.Final Key: LOGMGR-268 URL: https://issues.redhat.com/browse/LOGMGR-268 Project: JBoss Log Manager Issue Type: Component Upgrade Components: core Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.modules:jboss-modules}} to 1.10.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-269) Upgrade JSON-P to Jakarta JSON-P

by James Perkins (Jira)

James Perkins created LOGMGR-269: ------------------------------------ Summary: Upgrade JSON-P to Jakarta JSON-P Key: LOGMGR-269 URL: https://issues.redhat.com/browse/LOGMGR-269 Project: JBoss Log Manager Issue Type: Component Upgrade Components: ext Reporter: James Perkins Assignee: James Perkins Migrate the JSON-P API and implementation over to Jakarta. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13380) Upgrade dom4j from 2.1.1 to 2.1.3

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13380?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13380: ------------------------------------- Updated relationship of link to HHH-13953, from blocked by, to is related to. The dom4j upgrade is upstream now in Hibernate master + 5.3 branches, that should be enough. > Upgrade dom4j from 2.1.1 to 2.1.3 > --------------------------------- > > Key: WFLY-13380 > URL: https://issues.redhat.com/browse/WFLY-13380 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.1.Final, 20.0.0.Beta1 > > > https://github.com/dom4j/dom4j/compare/version-2.1.1...version-2.1.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3737) JavaEE appclient "Main" replace "System.in"

by Wolfgang Knauf (Jira)

[ https://issues.redhat.com/browse/WFLY-3737?page=com.atlassian.jira.plugin... ] Wolfgang Knauf commented on WFLY-3737: -------------------------------------- Same for WildFly 19 > JavaEE appclient "Main" replace "System.in" > ------------------------------------------- > > Key: WFLY-3737 > URL: https://issues.redhat.com/browse/WFLY-3737 > Project: WildFly > Issue Type: Bug > Components: Application Client > Affects Versions: 8.1.0.Final, 11.0.0.CR1, 19.0.0.Final > Reporter: Wolfgang Knauf > Assignee: James Perkins > Priority: Major > > "org.jboss.as.appclient.subsystem.Main.main" replaces System.in with a "NullInputStream" and thus you cannot use it to read user inputs. > I don't whether this is intentional, but it sounds like a bug to me -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 April 2020