May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4200) WAR MDB cannot obtain superclass on module classpath

by Eduardo Silva (JIRA)

[ https://issues.jboss.org/browse/WFLY-4200?page=com.atlassian.jira.plugin.... ] Eduardo Silva edited comment on WFLY-4200 at 5/2/15 5:42 PM: ------------------------------------------------------------- The error is on getMessageListenerInterface of MessageDrivenComponentDescriptionFactory: private String getMessageListenerInterface(final CompositeIndex compositeIndex, final AnnotationInstance messageBeanAnnotation) throws DeploymentUnitProcessingException { final AnnotationValue value = messageBeanAnnotation.value("messageListenerInterface"); if (value != null) return value.asClass().name().toString(); final ClassInfo beanClass = (ClassInfo) messageBeanAnnotation.target(); final Set<DotName> interfaces = new HashSet<DotName>(getPotentialViewInterfaces(beanClass)); // check super class(es) of the bean DotName superClassDotName = beanClass.superName(); while (interfaces.isEmpty() && superClassDotName != null && !superClassDotName.toString().equals(Object.class.getName())) { final ClassInfo superClass = compositeIndex.getClassByName(superClassDotName); if (superClass == null) { break; } interfaces.addAll(getPotentialViewInterfaces(superClass)); // move to next super class superClassDotName = superClass.superName(); } if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); return interfaces.iterator().next().toString(); } >>>>>>>>>>>> beanClass = org.warmdbtest.MyWarMDB superClassDotName = org.mdbtest.MySuperListener compositeIndexValues => {org.warmdbtest.MyWarMDB=org.warmdbtest.MyWarMDB} So superClassDotName org.mdbtest.MySuperListener is not indexed, This breaks and the DeploymentUnitProcessingException is called if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); was (Author: esantana): The error is on getMessageListenerInterface of MessageDrivenComponentDescriptionFactory: private String getMessageListenerInterface(final CompositeIndex compositeIndex, final AnnotationInstance messageBeanAnnotation) throws DeploymentUnitProcessingException { final AnnotationValue value = messageBeanAnnotation.value("messageListenerInterface"); if (value != null) return value.asClass().name().toString(); final ClassInfo beanClass = (ClassInfo) messageBeanAnnotation.target(); final Set<DotName> interfaces = new HashSet<DotName>(getPotentialViewInterfaces(beanClass)); // check super class(es) of the bean DotName superClassDotName = beanClass.superName(); while (interfaces.isEmpty() && superClassDotName != null && !superClassDotName.toString().equals(Object.class.getName())) { final ClassInfo superClass = compositeIndex.getClassByName(superClassDotName); if (superClass == null) { break; } interfaces.addAll(getPotentialViewInterfaces(superClass)); // move to next super class superClassDotName = superClass.superName(); } if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); return interfaces.iterator().next().toString(); } beanClass = org.warmdbtest.MyWarMDB superClassDotName = org.mdbtest.MySuperListener compositeIndexValues => {org.warmdbtest.MyWarMDB=org.warmdbtest.MyWarMDB} So superClassDotName org.mdbtest.MySuperListener is not indexed, This breaks anc the DeploymentUnitProcessingException is called if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); > WAR MDB cannot obtain superclass on module classpath > ---------------------------------------------------- > > Key: WFLY-4200 > URL: https://issues.jboss.org/browse/WFLY-4200 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EJB > Affects Versions: 8.2.0.Final > Reporter: John Mazzitelli > Priority: Minor > Attachments: mdb-test.zip > > > see the forum post for details: > https://developer.jboss.org/message/914355 > but suffice it to say this is similar to https://issues.jboss.org/browse/AS7-2638 which appears to have come back again. > In my WAR, I have an MDB which extends a class (in which that superclass implements MessageListener) and that superclass is in a module that my WAR depends on; the MDB fails to deploy. I have to explicitly add an annotation attribute to workaround the problem. > Again, see the forum for the very easy steps to replicate with a small zip file that contains the replication code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4200) WAR MDB cannot obtain superclass on module classpath

by Eduardo Silva (JIRA)

[ https://issues.jboss.org/browse/WFLY-4200?page=com.atlassian.jira.plugin.... ] Eduardo Silva edited comment on WFLY-4200 at 5/2/15 5:41 PM: ------------------------------------------------------------- The error is on getMessageListenerInterface of MessageDrivenComponentDescriptionFactory: private String getMessageListenerInterface(final CompositeIndex compositeIndex, final AnnotationInstance messageBeanAnnotation) throws DeploymentUnitProcessingException { final AnnotationValue value = messageBeanAnnotation.value("messageListenerInterface"); if (value != null) return value.asClass().name().toString(); final ClassInfo beanClass = (ClassInfo) messageBeanAnnotation.target(); final Set<DotName> interfaces = new HashSet<DotName>(getPotentialViewInterfaces(beanClass)); // check super class(es) of the bean DotName superClassDotName = beanClass.superName(); while (interfaces.isEmpty() && superClassDotName != null && !superClassDotName.toString().equals(Object.class.getName())) { final ClassInfo superClass = compositeIndex.getClassByName(superClassDotName); if (superClass == null) { break; } interfaces.addAll(getPotentialViewInterfaces(superClass)); // move to next super class superClassDotName = superClass.superName(); } if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); return interfaces.iterator().next().toString(); } beanClass = org.warmdbtest.MyWarMDB superClassDotName = org.mdbtest.MySuperListener compositeIndexValues => {org.warmdbtest.MyWarMDB=org.warmdbtest.MyWarMDB} So superClassDotName org.mdbtest.MySuperListener is not indexed, This breaks anc the DeploymentUnitProcessingException is called if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); was (Author: esantana): The error is getMessageListenerInterface of MessageDrivenComponentDescriptionFactory: private String getMessageListenerInterface(final CompositeIndex compositeIndex, final AnnotationInstance messageBeanAnnotation) throws DeploymentUnitProcessingException { final AnnotationValue value = messageBeanAnnotation.value("messageListenerInterface"); if (value != null) return value.asClass().name().toString(); final ClassInfo beanClass = (ClassInfo) messageBeanAnnotation.target(); final Set<DotName> interfaces = new HashSet<DotName>(getPotentialViewInterfaces(beanClass)); // check super class(es) of the bean DotName superClassDotName = beanClass.superName(); while (interfaces.isEmpty() && superClassDotName != null && !superClassDotName.toString().equals(Object.class.getName())) { final ClassInfo superClass = compositeIndex.getClassByName(superClassDotName); if (superClass == null) { break; } interfaces.addAll(getPotentialViewInterfaces(superClass)); // move to next super class superClassDotName = superClass.superName(); } if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); return interfaces.iterator().next().toString(); } beanClass = org.warmdbtest.MyWarMDB superClassDotName = org.mdbtest.MySuperListener compositeIndexValues => {org.warmdbtest.MyWarMDB=org.warmdbtest.MyWarMDB} So superClassDotName org.mdbtest.MySuperListener is not indexed, This breaks anc the DeploymentUnitProcessingException is called if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); > WAR MDB cannot obtain superclass on module classpath > ---------------------------------------------------- > > Key: WFLY-4200 > URL: https://issues.jboss.org/browse/WFLY-4200 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EJB > Affects Versions: 8.2.0.Final > Reporter: John Mazzitelli > Priority: Minor > Attachments: mdb-test.zip > > > see the forum post for details: > https://developer.jboss.org/message/914355 > but suffice it to say this is similar to https://issues.jboss.org/browse/AS7-2638 which appears to have come back again. > In my WAR, I have an MDB which extends a class (in which that superclass implements MessageListener) and that superclass is in a module that my WAR depends on; the MDB fails to deploy. I have to explicitly add an annotation attribute to workaround the problem. > Again, see the forum for the very easy steps to replicate with a small zip file that contains the replication code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4200) WAR MDB cannot obtain superclass on module classpath

by Eduardo Silva (JIRA)

[ https://issues.jboss.org/browse/WFLY-4200?page=com.atlassian.jira.plugin.... ] Eduardo Silva commented on WFLY-4200: ------------------------------------- The error is getMessageListenerInterface of MessageDrivenComponentDescriptionFactory: private String getMessageListenerInterface(final CompositeIndex compositeIndex, final AnnotationInstance messageBeanAnnotation) throws DeploymentUnitProcessingException { final AnnotationValue value = messageBeanAnnotation.value("messageListenerInterface"); if (value != null) return value.asClass().name().toString(); final ClassInfo beanClass = (ClassInfo) messageBeanAnnotation.target(); final Set<DotName> interfaces = new HashSet<DotName>(getPotentialViewInterfaces(beanClass)); // check super class(es) of the bean DotName superClassDotName = beanClass.superName(); while (interfaces.isEmpty() && superClassDotName != null && !superClassDotName.toString().equals(Object.class.getName())) { final ClassInfo superClass = compositeIndex.getClassByName(superClassDotName); if (superClass == null) { break; } interfaces.addAll(getPotentialViewInterfaces(superClass)); // move to next super class superClassDotName = superClass.superName(); } if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); return interfaces.iterator().next().toString(); } beanClass = org.warmdbtest.MyWarMDB superClassDotName = org.mdbtest.MySuperListener compositeIndexValues => {org.warmdbtest.MyWarMDB=org.warmdbtest.MyWarMDB} So superClassDotName org.mdbtest.MySuperListener is not indexed, This breaks anc the DeploymentUnitProcessingException is called if (interfaces.size() != 1) throw EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass); > WAR MDB cannot obtain superclass on module classpath > ---------------------------------------------------- > > Key: WFLY-4200 > URL: https://issues.jboss.org/browse/WFLY-4200 > Project: WildFly > Issue Type: Bug > Components: Class Loading, EJB > Affects Versions: 8.2.0.Final > Reporter: John Mazzitelli > Priority: Minor > Attachments: mdb-test.zip > > > see the forum post for details: > https://developer.jboss.org/message/914355 > but suffice it to say this is similar to https://issues.jboss.org/browse/AS7-2638 which appears to have come back again. > In my WAR, I have an MDB which extends a class (in which that superclass implements MessageListener) and that superclass is in a module that my WAR depends on; the MDB fails to deploy. I have to explicitly add an annotation attribute to workaround the problem. > Again, see the forum for the very easy steps to replicate with a small zip file that contains the replication code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-670?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-670: -------------------------------------- It looks like this was the commit that introduced the issue, https://github.com/wildfly/wildfly-core/commit/4f9da95373c27b70fea193778e.... > Node type is not complete at index 0 after tab completion on an empty resource > ------------------------------------------------------------------------------ > > Key: WFCORE-670 > URL: https://issues.jboss.org/browse/WFCORE-670 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 1.0.0.CR2 > > > Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working. > {code:title=Example Output} > [standalone@localhost:9990 /] /system-property= > The operation name is missing or the format of the operation request is wrong. > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] exit > Node type is not complete at index 0 > [standalone@localhost:9990 /] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-207) Add start/stop operations to hornetq-server resource

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-207?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-207: ------------------------------ Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Add start/stop operations to hornetq-server resource > ---------------------------------------------------- > > Key: WFLY-207 > URL: https://issues.jboss.org/browse/WFLY-207 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 9.0.0.CR2 > > > Currently it is not possible to start/stop a hornetq-server resource without removing or adding it. > For HornetQ replicated nodes, it'd be useful to be able to start/stop the node (runtime operations) without changing its configuration. That'd be necessary to restart replicated backup servers that have fallen back -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-143) Improve testing of Infinispan subsystem management features

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-143?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-143: ------------------------------ Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Improve testing of Infinispan subsystem management features > ----------------------------------------------------------- > > Key: WFLY-143 > URL: https://issues.jboss.org/browse/WFLY-143 > Project: WildFly > Issue Type: Bug > Components: Clustering, Domain Management > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 9.0.0.CR2 > > > We current use InfinispanSubsystemTest to test the integrity of the Infinispan subsystem implementation. > From the documentation: > {noformat} > Tests the ability to create a model from an xml configuration, marshal the model back to xml, re-read that marshalled model > into a new model that matches the first one, execute a "describe" operation for the model, create yet another model > from executing the results of that describe operation, and compare that model to first model. > {noformat} > Over and above these tests, we need more specific tests which cover use cases such as: > - every attribute can be read/written as required and that the subsequent reload-required state is as expected > - operation sequences such as add/remove/add, add/add give expected results for all resources in the subsystem > - validating that the XML configuration specified gets translated into the desired Infinispan configuration > - and many others -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-80) Product Version should not prepend product name with JBoss

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-80?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated WFLY-80: ----------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Product Version should not prepend product name with JBoss > ---------------------------------------------------------- > > Key: WFLY-80 > URL: https://issues.jboss.org/browse/WFLY-80 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: NadirX > Assignee: Jason Greene > Priority: Minor > Fix For: 9.0.0.CR2 > > > version/src/main/java/org/jboss/as/version/ProductConfig.java prepends the Product Name with 'JBoss' which is inappropriate for community projects. The result is that at startup I get the following > "INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) started in 3059ms" > where instead I should see > "INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) started in 3059ms" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-224) Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*"

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-224?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-224: ------------------------------ Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*" > ---------------------------------------------------------------------------------------- > > Key: WFLY-224 > URL: https://issues.jboss.org/browse/WFLY-224 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Security > Affects Versions: 8.0.0.Alpha1 > Reporter: Harald Pehl > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 9.0.0.CR2 > > > The attribute "cache-type" in "/subsystem=security/security-domain=*" can either be "default" or "infinispan". Please add the allowed value to the resource description. > In order to generate the UI based on the management model, it is essential that information like this is present. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-216) Include Infinispan CDI as a JBoss module

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-216?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-216: ------------------------------ Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Include Infinispan CDI as a JBoss module > ---------------------------------------- > > Key: WFLY-216 > URL: https://issues.jboss.org/browse/WFLY-216 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Avelino Martins > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2 > > > CDI has become an invaluable technology on any JavaEE project. I find hard to justify having to include infinispan-cdi as a compile dependency on every project that uses ISPN. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-214) Consider logging "Number of cluster members" on view change like is done at server startup

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-214?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-214: ------------------------------ Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Consider logging "Number of cluster members" on view change like is done at server startup > ------------------------------------------------------------------------------------------ > > Key: WFLY-214 > URL: https://issues.jboss.org/browse/WFLY-214 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 9.0.0.CR2 > > > See https://community.jboss.org/message/754829#754829 > Could we just do the same as for the startup? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 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 May 2015