January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Reopened: (WELD-73) Seam2 integration 1.0.0.BETA1

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-73?page=com.atlassian.jira.plugin... ] Pete Muir reopened WELD-73: --------------------------- > Seam2 integration 1.0.0.BETA1 > ----------------------------- > > Key: WELD-73 > URL: https://jira.jboss.org/jira/browse/WELD-73 > Project: Weld > Issue Type: Component Upgrade > Reporter: Pete Muir > Assignee: Pete Muir > -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (WELD-73) Seam2 integration 1.0.0.BETA1

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-73?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-73. ------------------------- Resolution: Done > Seam2 integration 1.0.0.BETA1 > ----------------------------- > > Key: WELD-73 > URL: https://jira.jboss.org/jira/browse/WELD-73 > Project: Weld > Issue Type: Component Upgrade > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.0.1.CR1 > > -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (WELD-72) Update Web Beans Extensions

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-72?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-72. ------------------------- Fix Version/s: (was: 1.0.1.CR1) Resolution: Out of Date > Update Web Beans Extensions > --------------------------- > > Key: WELD-72 > URL: https://jira.jboss.org/jira/browse/WELD-72 > Project: Weld > Issue Type: Thirdparty Change > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Blocker > -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-4) Bean validation needs to be more verbose/exact

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-4?page=com.atlassian.jira.plugin.... ] Pete Muir updated WELD-4: ------------------------- Issue Type: Feature Request (was: Task) > Bean validation needs to be more verbose/exact > ---------------------------------------------- > > Key: WELD-4 > URL: https://jira.jboss.org/jira/browse/WELD-4 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API > Affects Versions: 1.0.0.ALPHA2 > Reporter: Nicklas Karlsson > Assignee: David Allen > Priority: Critical > Fix For: 1.0.1.CR1 > > > e.g. the checks for unproxyable dependencies all go through Proxies.isTypeProxyable, returning a boolean for several conditions that result in failures, making tracking down the true cause difficult -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-378) Rename beans.xsd to beans_1_0.xsd

by Pete Muir (JIRA)

Rename beans.xsd to beans_1_0.xsd --------------------------------- Key: WELD-378 URL: https://jira.jboss.org/jira/browse/WELD-378 Project: Weld Issue Type: Feature Request Components: CDI API Reporter: Pete Muir Fix For: 1.0.1.CR1 -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (WELDX-68) Should the JEE full archetype illustrate how to use @DataSourceDefinition pointing to an embedded DB?

by Steven Boscarine (JIRA)

Should the JEE full archetype illustrate how to use @DataSourceDefinition pointing to an embedded DB? ------------------------------------------------------------------------------------------------------- Key: WELDX-68 URL: https://jira.jboss.org/jira/browse/WELDX-68 Project: Weld Extensions Issue Type: Sub-task Components: Archetypes Affects Versions: Archetypes 1.0.0-BETA1 Reporter: Steven Boscarine If we include a persistence example, shouldn't we also include an example of how to use: http://java.sun.com/javaee/6/docs/api/javax/annotation/sql/DataSourceDefi... Also, I think any persistence examples should use an embedded database like JavaDB or HSQLDB. -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-318) Wrapping InjectionTarget does not work for Beans with a Producer field

by Stuart Douglas (JIRA)

Wrapping InjectionTarget does not work for Beans with a Producer field ---------------------------------------------------------------------- Key: WELD-318 URL: https://jira.jboss.org/jira/browse/WELD-318 Project: Weld Issue Type: Bug Reporter: Stuart Douglas I am trying to wrap InjectionTarget to set field values at bean creation time. This works perfectly unless the bean has a producer field. When the bean has a producer the InjectionTarget.postConstruct is never called (even though the PostConstruct method on the bean is called). -- 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

16 years, 2 months

2
15
0 / 0

[JBoss JIRA] Closed: (WELD-10) Some beans are correctly causing a validation failure, but with the wrong cause

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-10?page=com.atlassian.jira.plugin... ] Pete Muir closed WELD-10. ------------------------- Resolution: Out of Date Assignee: Pete Muir > Some beans are correctly causing a validation failure, but with the wrong cause > ------------------------------------------------------------------------------- > > Key: WELD-10 > URL: https://jira.jboss.org/jira/browse/WELD-10 > Project: Weld > Issue Type: Bug > Components: Class Beans (Managed and Session) > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.0.1.CR1 > > > Search for "ri-wrong-cause" test group in the TCK -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-352) EEFields connot inject into proxy

by he youlin (JIRA)

EEFields connot inject into proxy --------------------------------- Key: WELD-352 URL: https://jira.jboss.org/jira/browse/WELD-352 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: he youlin see http://www.seamframework.org/Community/EEFieldsConnotInjectIntoProxy -- 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

16 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-58) Issue with org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest

by Vivek Pandey (JIRA)

Issue with org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest ------------------------------------------------------------------------------- Key: CDITCK-58 URL: https://jira.jboss.org/jira/browse/CDITCK-58 Project: CDI TCK Issue Type: CTS Challenge Security Level: Public (Everyone can see) Affects Versions: 1.0.1.CR1 Environment: JDK 6 u15, Snow Leopard, GlassFish v3 b72, CDI TCK 1.0.1 RC1 Reporter: Vivek Pandey For context package test: org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest There are 2 assertions on glassfish v3: org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest.testRequestScopeActiveDuringCallToEjbTimeoutMethod(EJBRequestContextTest.java:36) org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest.testRequestScopeDestroyedAfterCallToEjbTimeoutMethod(EJBRequestContextTest.java:53) I think Weld is not doing the right thing here. See the analysis below: In FMSModeIII, the timer expire time is 200 ms. The test waits for 250 ms so that timeout() is invoked and sets requestScopeActive to true. In the EJBRequestcontextCode: flightManagementSystem.climb(); ==> a timer is created with 200 ms duration Thread.sleep(250); ==> sleep for 250 ms and timeout is called assert flightManagementSystem.isRequestScopeActive(); ==> Due to the exception below, the flag requestScopeActive, which was supposed to be set in timeout() method was never set. Caused by: javax.enterprise.context.ContextNotActiveException: No active contexts for scope type javax.enterprise.context.RequestScoped at org.jboss.weld.BeanManagerImpl.getContext(BeanManagerImpl.java:928) at org.jboss.jsr299.tck.tests.context.request.ejb.FMSModelIII.timeout(FMSModelIII.java:50) Under jsr 299 spec 6.7.1: -------- The request context is provided by a built-in context object for the built-in scope type @RequestScoped. The request scope is active: * during any remote method invocation of any EJB, during any asynchronous method invocation of any EJB, during any call to an EJB timeout method and during message delivery to any EJB message-driven bean, and ---------- However during timeout() method call beanManager.getContext(RequestScoped.class).isActive() returns false. Which seems to violate the above requirement in 6.7.1. -- 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

16 years, 2 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010