March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Yeray Borges commented on WFLY-5966: ------------------------------------ {{javaee.api}} requires the no longer exported libraries from {{javax.ejb.api}}, so the tasks on the following modules are to verify that they really need all the libraries exported by {{javaee.api}}: feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/main/module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/myfaces/module.xml jsf/subsystem/src/test/resources/modules2/com/sun/jsf-impl/myfaces2/module.xml > Validate requirement for modules previously exported by javax.ejb.api > --------------------------------------------------------------------- > > Key: WFLY-5966 > URL: https://issues.jboss.org/browse/WFLY-5966 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: > {code} >  > <module name="javax.api"/> > <module name="javax.transaction.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > <module name="org.omg.api"/> > {code} > If a module already had a dep on one of those, it's not in the block. > This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. > Affected modules: > -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml > The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: > feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml > jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml > jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml > feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml > jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/main/module.xml > jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/myfaces/module.xml > jsf/subsystem/src/test/resources/modules2/com/sun/jsf-impl/myfaces2/module.xml > The following modules were fixed or verified as correct (moved from the first list): > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Yeray Borges updated WFLY-5966: ------------------------------- Description: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/main/module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/myfaces/module.xml jsf/subsystem/src/test/resources/modules2/com/sun/jsf-impl/myfaces2/module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml was: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/main/module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/myfaces/module.xml jsf/subsystem/src/test/resources/modules2/com/sun/jsf-impl/myfaces2/module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml > Validate requirement for modules previously exported by javax.ejb.api > --------------------------------------------------------------------- > > Key: WFLY-5966 > URL: https://issues.jboss.org/browse/WFLY-5966 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: > {code} >  > <module name="javax.api"/> > <module name="javax.transaction.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > <module name="org.omg.api"/> > {code} > If a module already had a dep on one of those, it's not in the block. > This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. > Affected modules: > -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml > The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: > feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml > jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml > jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml > feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml > jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/main/module.xml > jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/myfaces/module.xml > jsf/subsystem/src/test/resources/modules2/com/sun/jsf-impl/myfaces2/module.xml > The following modules were fixed or verified as correct (moved from the first list): > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Yeray Borges updated WFLY-5966: ------------------------------- Description: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/main/module.xml jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/myfaces/module.xml jsf/subsystem/src/test/resources/modules2/com/sun/jsf-impl/myfaces2/module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml was: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml > Validate requirement for modules previously exported by javax.ejb.api > --------------------------------------------------------------------- > > Key: WFLY-5966 > URL: https://issues.jboss.org/browse/WFLY-5966 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: > {code} >  > <module name="javax.api"/> > <module name="javax.transaction.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > <module name="org.omg.api"/> > {code} > If a module already had a dep on one of those, it's not in the block. > This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. > Affected modules: > feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- > The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: > feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml > jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml > jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml > jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/main/module.xml > jsf/subsystem/src/test/resources/modules/com/sun/jsf-impl/myfaces/module.xml > jsf/subsystem/src/test/resources/modules2/com/sun/jsf-impl/myfaces2/module.xml > The following modules were fixed or verified as correct (moved from the first list): > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Ondra Chaloupka edited comment on WFLY-11858 at 3/21/19 5:36 AM: ----------------------------------------------------------------- [~manovotn] the condition is there because of https://issues.jboss.org/browse/JBTM-3044. Narayana was hard coded with {{InitialContext}} and the idea here was to allow Weld SE application to provide transaction manager as an injectable bean which is not dependent on the {{IntialContext}} lookup. For WFLY we need {{IntialContext}} for looking up while for Java SE app is right the opposite. [~ljnelson] I personally like what [~mkouba] affirmed. I understand the idea of the "user-supplied InitialContext bean implementations" but I don't think there is some reasonable demand for it. Or use what you proposed here: https://github.com/ochaloup/narayana/commit/964222d60c6f64849430057cd744d... But it's really a complicated code and I'm still not sure if there is somebody who like to provide the IntialContext as bean. was (Author: ochaloup): [~manovotn] the condition is there because of https://issues.jboss.org/browse/JBTM-3044. Narayana was hard coded with {{InitialContext}} and the idea here was to allow Weld SE application to provide transaction manager as an injectable bean which is not dependent on the {{IntialContext}} lookup. For WFLY we need {{IntialContext}} for looking up while for Java SE app is right the opposite. [~ljnelson] I personally like what [~mkouba] affirmed. I understand the idea of the "user-supplied InitialContext bean implementations" but I don't think there is some reasonable demand for it. > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh K. Cherukuri > Assignee: Matej Novotny > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Yeray Borges updated WFLY-5966: ------------------------------- Description: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml was: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml > Validate requirement for modules previously exported by javax.ejb.api > --------------------------------------------------------------------- > > Key: WFLY-5966 > URL: https://issues.jboss.org/browse/WFLY-5966 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: > {code} >  > <module name="javax.api"/> > <module name="javax.transaction.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > <module name="org.omg.api"/> > {code} > If a module already had a dep on one of those, it's not in the block. > This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. > Affected modules: > feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- > The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: > feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml > jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml > jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml > The following modules were fixed or verified as correct (moved from the first list): > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Ondra Chaloupka edited comment on WFLY-11858 at 3/21/19 5:22 AM: ----------------------------------------------------------------- [~manovotn] the condition is there because of https://issues.jboss.org/browse/JBTM-3044. Narayana was hard coded with {{InitialContext}} and the idea here was to allow Weld SE application to provide transaction manager as an injectable bean which is not dependent on the {{IntialContext}} lookup. For WFLY we need {{IntialContext}} for looking up while for Java SE app is right the opposite. [~ljnelson] I personally like what [~mkouba] affirmed. I understand the idea of the "user-supplied InitialContext bean implementations" but I don't think there is some reasonable demand for it. was (Author: ochaloup): [~manovotn] the condition is there because of https://issues.jboss.org/browse/JBTM-3044. Narayana was hard coded with `InitialContext` and the idea here was to allow Weld SE application to provide transaction manager as an injectable bean which is not dependent on the `IntialContext` lookup. For WFLY we need IntialContext for looking up while for Java SE app is right the opposite. [~ljnelson] I personally like what [~mkouba] affirmed. I understand the idea of the "user-supplied InitialContext bean implementations" but I don't think there is some reasonable demand for it. > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh K. Cherukuri > Assignee: Matej Novotny > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Yeray Borges updated WFLY-5966: ------------------------------- Description: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml was: The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: {code}  <module name="javax.api"/> <module name="javax.transaction.api"/> <module name="javax.xml.rpc.api"/> <module name="javax.rmi.api"/> <module name="org.omg.api"/> {code} If a module already had a dep on one of those, it's not in the block. This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. Affected modules: feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml The following modules were fixed or verified as correct (moved from the first list): feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml > Validate requirement for modules previously exported by javax.ejb.api > --------------------------------------------------------------------- > > Key: WFLY-5966 > URL: https://issues.jboss.org/browse/WFLY-5966 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this: > {code} >  > <module name="javax.api"/> > <module name="javax.transaction.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > <module name="org.omg.api"/> > {code} > If a module already had a dep on one of those, it's not in the block. > This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed. > Affected modules: > feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml- > -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml- > The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api: > feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml > -feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml- > feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml > jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml > jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml > The following modules were fixed or verified as correct (moved from the first list): > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Ondra Chaloupka commented on WFLY-11858: ---------------------------------------- [~manovotn] the condition is there because of https://issues.jboss.org/browse/JBTM-3044. Narayana was hard coded with `InitialContext` and the idea here was to allow Weld SE application to provide transaction manager as an injectable bean which is not dependent on the `IntialContext` lookup. For WFLY we need IntialContext for looking up while for Java SE app is right the opposite. [~ljnelson] I personally like what [~mkouba] affirmed. I understand the idea of the "user-supplied InitialContext bean implementations" but I don't think there is some reasonable demand for it. > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh K. Cherukuri > Assignee: Matej Novotny > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Martin Kouba (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Martin Kouba commented on WFLY-11858: ------------------------------------- I believe you should not share an instance of {{InitialContext}} - the instance is not synchronized. So {{@Singleton}} is a wrong choice. To be honest, I don't see a good reason for the existence of the "InitialContext" bean. I would just use {{javax.naming.InitialContext.doLookup(Name)}} when needed. I also think that Java EE naming context is thread-specific and so it's not a good idea to perform a lookup "outside the current invocation". > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh K. Cherukuri > Assignee: Matej Novotny > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Matej Novotny (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Matej Novotny commented on WFLY-11858: -------------------------------------- Hmm, the addition of the {{InitialContext}} bean is conditional though, see [this line|https://github.com/jbosstm/narayana/blob/5.9.3.Final/ArjunaJTA/cdi/c...]. I wonder if that might be the cause of the intermittent failures? Because the exception is unsatisfied dependency which means that the bean wasn't picked up (again, intermittently). To me that seems like the registration didn't go through at all. If I get it correctly, the "visibility" shouldn't be an issue here since both beans are within the same module, both are Narayana beans. [~ljnelson] why was the addition conditional in the first place? > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh K. Cherukuri > Assignee: Matej Novotny > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 2019