January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBAOP-815) AOP generates invalid join point class

by Kirill Paliy (JIRA)

Kirill Paliy created JBAOP-815: ---------------------------------- Summary: AOP generates invalid join point class Key: JBAOP-815 URL: https://issues.jboss.org/browse/JBAOP-815 Project: JBoss AOP Issue Type: Bug Affects Versions: 2.1.1.GA Environment: Jboss 5.1.0 Reporter: Kirill Paliy Priority: Critical Aspect method like this (non-void) causes error @Nullable @Bind(pointcut = "execution(* *->@com.myproject.utils.annotations.Activity(..))") public Object exec(final MethodInvocation invocation) throws Throwable { 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) java.lang.ClassFormatError: StackMapTable format error: bad type array size in method com.myproject.patchers.ejb.JoinPoint_patch1937572184742986621_2.invokeNext()Ljava/lang/Object; 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at java.lang.Class.getDeclaredConstructors0(Native Method) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at java.lang.Class.getDeclaredConstructors(Class.java:2020) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at org.jboss.aop.instrument.JoinPointGenerator$GeneratedClassInfo.<init>(JoinPointGenerator.java:1553) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:381) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:284) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at org.jboss.aop.instrument.JoinPointGenerator.access$300(JoinPointGenerator.java:76) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1729) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:249) 2016-01-06 21:19:09,564 ERROR [STDERR] (Thread-30) at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1044) It happens because method body generated for invokeNext contains unreachable code (see break after return): { try{ switch(++super.currentInterceptor){ case 1: return ($w) around1.exec(this); break; default: return ($w)this.dispatch(); } } finally { --super.currentInterceptor; } return null; } Fix is pretty simple, but as I understand project is frozen, so I'll just post it here: JoinPointGenerator.java 1940,1941c1940,1942 < < call.append(" break;"); --- > if (generator.isVoid()) { > call.append(" break;"); > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBEE-160) jboss-transaction-api OSGi bundle requiring optional packages

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/JBEE-160?page=com.atlassian.jira.plugin.s... ] Brett Meyer commented on JBEE-160: ---------------------------------- [~smarlow], yep. Above <Export-Package>, add something like the following: {code} <Import-Package> javax.enterprise.context;resolution:=optional, * </Import-Package> {code} If you could give that a shot, built the jar, and paste the Manifest.MF here, more than happy to verify it. > jboss-transaction-api OSGi bundle requiring optional packages > ------------------------------------------------------------- > > Key: JBEE-160 > URL: https://issues.jboss.org/browse/JBEE-160 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Scott Marlow > > The jboss-transaction-api_1.2_spec OSGi bundle requires the 'javax.enterprise.context'. Instead, that should be optional, right? cdi-api shouldn't be required to simply use jta. Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5042) Two persistence.xml in two EJB projects within one EAR don't work

by Martin Rauscher (JIRA)

[ https://issues.jboss.org/browse/WFLY-5042?page=com.atlassian.jira.plugin.... ] Martin Rauscher commented on WFLY-5042: --------------------------------------- I have yet to try to reproduce with the reduced example that I provided, but at least my original application still did not work won WildFly 10CR4 > Two persistence.xml in two EJB projects within one EAR don't work > ------------------------------------------------------------------ > > Key: WFLY-5042 > URL: https://issues.jboss.org/browse/WFLY-5042 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 9.0.0.Final > Reporter: Martin Rauscher > Assignee: Scott Marlow > > We have an EAR containing a JAR in /lib and two EJBs and one WAR each referencing the JAR. The rest of the dependencies is: WAR->EJB1->EJB2. > If each of the EJB JARs has its own persistence.xml the EAR cannot be deployed anymore to WildFly. (It worked on WebSphere) > This works fine as long as no persistence.xml exists. As soon as each EJB gets its own persistence.xml (in our full project they point to different DSs) we're not able to deploy anymore. > Wildfly doesn't seem to be able to resolve dependencies between modules as soon as there are two persistence.xml's. Despite the (repro) project doesn't even use it (yet). If you remove the persistence.xml's the project works fine. From the error (see below) it looks like the services defined in EJB1 try to use the persistence unit defined in EJB2 despite there not being any kind of reference. > Repro on [GitHub|https://github.com/Hades32/wildfly-issues]. > Forum discussion [here|https://developer.jboss.org/thread/261445], including logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1202) LDAP authentication/authorization fails due to making unneeded role lookup requests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1202?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1202: ------------------------------------------------- dhorton(a)redhat.com changed the Status of [bug 1196343|https://bugzilla.redhat.com/show_bug.cgi?id=1196343] from ASSIGNED to POST > LDAP authentication/authorization fails due to making unneeded role lookup requests > ----------------------------------------------------------------------------------- > > Key: WFCORE-1202 > URL: https://issues.jboss.org/browse/WFCORE-1202 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brad Maxwell > Assignee: Derek Horton > Fix For: 2.0.5.CR1 > > > LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5967) Have web services add javax.xml.rpic.api dependency to deployments instead of EjbDependencyDeploymentUnitProcessor

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-5967: -------------------------------------- Summary: Have web services add javax.xml.rpic.api dependency to deployments instead of EjbDependencyDeploymentUnitProcessor Key: WFLY-5967 URL: https://issues.jboss.org/browse/WFLY-5967 Project: WildFly Issue Type: Task Components: Web Services Affects Versions: 10.0.0.CR5 Reporter: Brian Stansberry Assignee: Alessio Soldano Prior to WFLY-5922, the packages in the javax.xml.rpic.api module were being made available to deployments because EjbDependencyDeploymentUnitProcessor added the javax.ejb.api module, and javax.ejb.api *exported* javax.xml.rpc.api. WFLY-5922 removed that export, which broke the TCK signature tests. So I'm about to put up a workaround PR that has EjbDependencyDeploymentUnitProcessor directly add a dep on javax.xml.rpc.api. That's a workaround for 10.0.0.Final, but Jason noted he thought it would make more sense for this dep to come from the ws subsystem. So this JIRA is to track looking into that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5967) Have web services add javax.xml.rpic.api dependency to deployments instead of EjbDependencyDeploymentUnitProcessor

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5967?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5967: ----------------------------------- Component/s: EJB > Have web services add javax.xml.rpic.api dependency to deployments instead of EjbDependencyDeploymentUnitProcessor > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5967 > URL: https://issues.jboss.org/browse/WFLY-5967 > Project: WildFly > Issue Type: Task > Components: EJB, Web Services > Affects Versions: 10.0.0.CR5 > Reporter: Brian Stansberry > Assignee: Alessio Soldano > > Prior to WFLY-5922, the packages in the javax.xml.rpic.api module were being made available to deployments because EjbDependencyDeploymentUnitProcessor added the javax.ejb.api module, and javax.ejb.api *exported* javax.xml.rpc.api. > WFLY-5922 removed that export, which broke the TCK signature tests. So I'm about to put up a workaround PR that has EjbDependencyDeploymentUnitProcessor directly add a dep on javax.xml.rpc.api. > That's a workaround for 10.0.0.Final, but Jason noted he thought it would make more sense for this dep to come from the ws subsystem. So this JIRA is to track looking into that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Brian Stansberry 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/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/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 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/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/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 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 > 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: Jason Greene > > 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/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/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 > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ] Brian Stansberry 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/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/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 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 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/ejb/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/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/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 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 > 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: Jason Greene > > 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/jpa/main/module.xml > feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/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 > 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 > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-5966: -------------------------------------- Summary: 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: Jason Greene 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/ejb/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/jpa/main/module.xml feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/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 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 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5689) EJB subsystem security domain mapping

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-5689?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-5689: ----------------------------- Description: Allow the EJB subsystem to declare which Elytron security domains it uses. Sample configuration: {code:xml} <application-security-domains> <application-security-domain name="other" security-domain="ApplicationDomain"/> </application-security-domains> {code} was: Allow the EJB subsystem to declare which Elytron security domains it uses. Sample configuration: {code:xml} <security-domains default="ApplicationDomain"> <security-domain name="ApplicationDomain" alias="MyDomain"/> <security-domain name="ManagementDomain"/> </security-domains> {code} > EJB subsystem security domain mapping > ------------------------------------- > > Key: WFLY-5689 > URL: https://issues.jboss.org/browse/WFLY-5689 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > Fix For: 11.0.0.Alpha1 > > > Allow the EJB subsystem to declare which Elytron security domains it uses. > Sample configuration: > {code:xml} > <application-security-domains> > <application-security-domain name="other" security-domain="ApplicationDomain"/> > </application-security-domains> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 January 2016