June 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-205) Add test to verify extensions in non-bean archives are loaded

by Dan Allen (JIRA)

Add test to verify extensions in non-bean archives are loaded ------------------------------------------------------------- Key: CDITCK-205 URL: https://issues.jboss.org/browse/CDITCK-205 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Dan Allen Priority: Minor Add a test to answers this question: Does an extension have to be in an bean archive in order to be loaded? Section 11.5 states: "An extension is a service provider of the service javax.enterprise.inject.spi.Extension declared in META-INF/services." If one assumes that "service provider" refers to the term defined in the jar specification [1], then one would conclude that an extension does not have to be in a bean archive to be recognized (these are orthogonal concerns). A test for this scenario is available in the OpenTCK project and may be ported to the CDI TCK. [2] [1] http://download.oracle.com/javase/6/docs/technotes/guides/jar/jar.html#Se... [2] https://github.com/opentck/javaee_cdi/tree/master/src/test/java/org/opent... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (CDITCK-206) Add test to verify visibly of beans registered explicitly through an extension in non-bean archives

by Dan Allen (JIRA)

Add test to verify visibly of beans registered explicitly through an extension in non-bean archives --------------------------------------------------------------------------------------------------- Key: CDITCK-206 URL: https://issues.jboss.org/browse/CDITCK-206 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Dan Allen Add a test that answers this question: Can an extension register a bean programmatically for a class that resides in another non-bean archive? This question requires a short example which is available in the OpenTCK test suite and may be ported to the CDI TCK [1]. Assume one archive, a.jar, has the following contents: org/opentck/javaee/cdi/spi/beforebeandiscovery/BeanClassToRegister.class A second archive, b.jar, has the following contents: org/opentck/javaee/cdi/spi/beforebeandiscovery/AnotherBeanClassToRegister.class org/opentck/javaee/cdi/spi/beforebeandiscovery/AnotherManualBeanRegistrationExtension.class org/opentck/javaee/cdi/spi/beforebeandiscovery/ManualBeanRegistrationExtension.class META-INF/services/javax.enterprise.inject.spi.Extension AnotherBeanClassToRegister has an injection point of type BeanClassToRegister: public class AnotherBeanClassToRegister { @Inject private BeanClassToRegister collaborator; } BeanClassToRegister and AnotherBeanClassToRegister are added as beans programmatically in respective extensions listed in the service provider descriptor: public class ManualBeanRegistrationExtension implements Extension { public void registerBeans(@Observes BeforeBeanDiscovery event, BeanManager bm) { event.addAnnotatedType(bm.createAnnotatedType(BeanClassToRegister.class)); } } public class AnotherManualBeanRegistrationExtension implements Extension { public void registerBeans(@Observes BeforeBeanDiscovery event, BeanManager bm) { event.addAnnotatedType(bm.createAnnotatedType(AnotherBeanClassToRegister.class)); } } The two libraries, a.jar and b.jar are bundled in a web archive, test.war WEB-INF/lib/a.jar WEB-INF/lib/b.jar WEB-INF/beans.xml Deploying this archive to the reference implementation fails with an error message that the injection point from above cannot be satisfied. There appears to be a visibility problem across bean archives in this case. Adding META-INF/beans.xml to a.jar and removing the ManualBeanRegistrationExtension from b.jar resolves the issue in the reference implementation. [1] https://github.com/opentck/javaee_cdi/tree/master/src/test/java/org/opent... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-878) WeldPhaseListener fails to activate conversation context if conversation is not found

by Jarkko Hyöty (JIRA)

WeldPhaseListener fails to activate conversation context if conversation is not found ------------------------------------------------------------------------------------- Key: WELD-878 URL: https://issues.jboss.org/browse/WELD-878 Project: Weld Issue Type: Bug Components: Conversations, Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.1.0.Final Environment: Glassfish 3.1 B43 updated with weld-1.1.0-SNAPSHOT (weld-osgi-bundle-1.1.0-20110329.041630-9.jar) Reporter: Jarkko Hyöty It seems that org.jboss.weld.jsf.WeldPhaseListener fails to activate conversation context if a conversation is not found by the supplied conversation id. This problem is potentially related to [SEAMCATCH-46],[WELD-855]. JSR-299 6.7.4 Conversation context lifecycle has a requirement that 'If the propagated conversation cannot be restored, the container _must associate the request with a new transient conversation_ and throw an exception of type javax.enterprise.context.NonexistentConversationException from the restore view phase of the JSF lifecycle.'. However, the implementation of org.jboss.weld.jsf.WeldPhaseListener.activateConversations fails to do that if a conversation is not found by the conversation id. {code} private void activateConversations(FacesContext facesContext) { ConversationContext conversationContext = instance().select(HttpConversationContext.class).get(); String cid = getConversationId(facesContext, conversationContext); log.debug(RESUMING_CONVERSATION, cid); if (cid != null && conversationContext.getConversation(cid) == null) { throw new NonexistentConversationException(NO_CONVERSATION_FOUND_TO_RESTORE, cid); } conversationContext.activate(cid); } {code} Recovering from the exception becomes difficult since the context is not active. Typical symptom is 'java.lang.IllegalStateException: Unable to load current conversations from the associated request, something went badly wrong when associate() was called at org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413)' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

6
8
0 / 0

[JBoss JIRA] Created: (CDITCK-214) Managed bean not given a @Named annotation in Non-Contextual injection test

by Bob Nettleton (JIRA)

Managed bean not given a @Named annotation in Non-Contextual injection test --------------------------------------------------------------------------- Key: CDITCK-214 URL: https://issues.jboss.org/browse/CDITCK-214 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Bob Nettleton The following test case: org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.InjectionIntoNonContextualComponentTest.testInjectionIntoJSFManagedBean verifies that a JSF managed bean can be a target for CDI injection. The .jsp in the test case (ManagedBeanTestPage.jsp) relies on an Expression Langage name ("farm") in order to locate this bean. The managed bean in question: org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.Farm does not include a @Named annotation. Section 2.5.3 of the CDI Specification states that: "If @Named is not declared by the bean, nor by its stereotypes, a bean has no EL name." Based on this line in the spec, it appears that this test may be in error. If the bean does not have an EL name, the bean cannot be located by the EL Resolver. If my interpretation of the spec is correct here, I request that this test be excluded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (CDITCK-175) Tests from org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor should be separated

by Marius Bogoevici (JIRA)

Tests from org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor should be separated -------------------------------------------------------------------------------------------------------------- Key: CDITCK-175 URL: https://jira.jboss.org/browse/CDITCK-175 Project: CDI TCK Issue Type: Bug Reporter: Marius Bogoevici The package contains a few tests that exercise deployment errors due to invalid intercepted class definitions. The tests must be separated (perhaps in individual packages) in order to make sure that the test cases run in isolation (since there are multiple sources of errors, the deployment will fail if at least one is satisfied, but we want to test all). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-347) META-INF/beans.xml not sufficient to activate CDI in WAR

by Dan Allen (JIRA)

META-INF/beans.xml not sufficient to activate CDI in WAR -------------------------------------------------------- Key: WELD-347 URL: https://jira.jboss.org/jira/browse/WELD-347 Project: Weld Issue Type: Bug Components: GlassFish Integration Affects Versions: 1.0.0.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 1.0.1.CR1 In GlassFish V3, if a WAR is deployed containing WEB-INF/classes/META-INF/beans.xml, CDI does not get activated (no beans are detected). Activation only happens if the WAR contains WEB-INF/beans.xml. I'm not sure why GlassFish V3 is having a problem finding beans.xml in the META-INF directory of the WAR classpath. I can't tell if it is a problem in Weld or a problem in GlassFish V3 somewhere. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (CDITCK-176) Decorator Elements in beans.xml use <decorator> not <class>

by Pete Muir (JIRA)

Decorator Elements in beans.xml use <decorator> not <class> ----------------------------------------------------------- Key: CDITCK-176 URL: https://jira.jboss.org/browse/CDITCK-176 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR2 Reporter: Pete Muir Fix For: 1.0.2.CR3 Affected tests: testPassivationCapableBeanWithNonPassivatingDecoratorBeanConstructorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingBeanConstructor.DecoratorWithNonPassivatingBeanConstructorTest) testPassivationCapableBeanWithNonPassivatingInitializerInDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInitializerMethod.DecoratorWithNonPassivatingInitializerMethodTest) testPassivationCapableBeanWithNonPassivatingDecoratorInjectedFieldFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField.DecoratorWithNonPassivatingInjectedFieldTest) testEnterpriseBeanWithNonPassivatingDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingDecorator.EnterpriseBeanWithNonPassivatingDecoratorTest) testDecoratorListedTwiceInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.decoratorListedTwiceInBeansXml.DecoratorListedTwiceInBeansXmlTest) testNonExistantDecoratorClassInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.nonExistantClassInBeansXml.NonExistantDecoratorClassInBeansXmlTest) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-897) java.lang.ClassFormatError: Illegal classname - org/jboss/jsr299/tck/tests/extensions/alternative...

by Kyle Grucci (JIRA)

java.lang.ClassFormatError: Illegal classname - org/jboss/jsr299/tck/tests/extensions/alternative... ---------------------------------------------------------------------------------------------------- Key: WELD-897 URL: https://issues.jboss.org/browse/WELD-897 Project: Weld Issue Type: Bug Environment: All platforms - but noticed on Solaris x86 Reporter: Kyle Grucci The CDI TCK passes all tests when run using Glassfish 3.x with Oracle's JDK 1.6.0_24. However, when we change to use Oracle's JDK 1.6.0_25 patch, deployment of some of the test war files to the autodeploy directory of Glassfish results in the errors below. Talking with Pete Muir, it appears that the JDK has tightened something and is now exposing a bug in Weld. [#|2011-05-03T13:02:50.870-0400|SEVERE|glassfish3.2|javax.enterprise.system.to ols.admin.org.glassfish.deployment.admin|_ThreadID=17;_ThreadName=Thread-1;|Ex ception while loading the app : by java.lang.ClassFormatError: Illegal class name "org/jboss/jsr299/tck/tests/extensions/alternative/metadata/org$jboss$weld$bea n-org$jboss$jsr299$tck$tests$extensions$alternative$metadata$AlternativeMetada taTest-ManagedBean-org$jboss$jsr299$tck$tests$extensions$alternative$metadata$ Grocery[@javax$enterprise$context$RequestScoped()@org$jboss$jsr299$tck$tests$e xtensions$alternative$metadata$Cheap()@org$jboss$jsr299$tck$tests$extensions$a lternative$metadata$GroceryInterceptorBinding()@org$jboss$jsr299$tck$tests$ext ensions$alternative$metadata$NamedStereotype()]{org$jboss$jsr299$tck$tests$ext ensions$alternative$metadata$Grocery$bread[@javax$enterprise$inject$Produces() ]$org$jboss$jsr299$tck$tests$extensions$alternative$metadata$Grocery$fruit[@ja vax$inject$Inject()@org$jboss$jsr299$tck$tests$extensions$alternative$metadata $Cheap()]$org$jboss$jsr299$tck$tests$extensions$alternative$meta data$Grocery$vegetables[@javax$inject$Inject()]$org$jboss$jsr299$tck$tests$ext ensions$alternative$metadata$Grocery$getMilk[@javax$enterprise$inject$Produces ()]( org.jboss.weld.exceptions.WeldException: by java.lang.ClassFormatError: Illegal class name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-707) Intercepted bean method notifyAll() cannot be declared final

by Adam Warski (JIRA)

Intercepted bean method notifyAll() cannot be declared final ------------------------------------------------------------ Key: WELD-707 URL: https://jira.jboss.org/browse/WELD-707 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Adam Warski This started showing up after upgrading from M4 to M5, so to Weld 1.1.0. I'm using weldx, and as per the conversation on IRC with Pete this may be the cause. Exact message: WELD-001504 Intercepted bean method [method] public final native pl.softwaremill.service.organization.OrganizationService.notifyAll() (intercepted by pl.softwaremill.cdiext.transaction.TransactionalInterceptor) cannot be declared final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (WELD-744) Interceptor and Decorator validation assumes that producer fields and methods will be public

by Pete Muir (JIRA)

Interceptor and Decorator validation assumes that producer fields and methods will be public -------------------------------------------------------------------------------------------- Key: WELD-744 URL: https://jira.jboss.org/browse/WELD-744 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Pete Muir Fix For: 1.1.0.CR1 Needs to iterate over the class hierarchy looking at declared methods -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2011