December 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-53) Remove library version definitions from build.properties

by Jozef Hartinger (JIRA)

Remove library version definitions from build.properties -------------------------------------------------------- Key: CDITCK-53 URL: https://jira.jboss.org/jira/browse/CDITCK-53 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.GA Reporter: Jozef Hartinger Priority: Minor Fix For: 1.0.1.CR1 Library version definitions like weld-deployer.version=5.2.0-SNAPSHOT weld.version=1.0.0-SNAPSHOT are present in the jsr299-tck-1.0.0/weld/jboss-as/build.properties although they are not used and confusing. -- 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

15 years, 1 month

2
4
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

15 years, 1 month

2
15
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

15 years, 1 month

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

15 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (WELD-353) MDBs throw DeploymentException

by Nicklas Karlsson (JIRA)

MDBs throw DeploymentException ------------------------------ Key: WELD-353 URL: https://jira.jboss.org/jira/browse/WELD-353 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API, Class Beans (Managed and Session) Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson 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

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (WELD-359) EJBs without local interfaces throws NPEs

by Nicklas Karlsson (JIRA)

EJBs without local interfaces throws NPEs ----------------------------------------- Key: WELD-359 URL: https://jira.jboss.org/jira/browse/WELD-359 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson EJBs without local interfaces appear to throw NPE: java.lang.NullPointerException at org.jboss.weld.ejb.InternalEjbDescriptor.<init>(InternalEjbDescriptor.java:48) at org.jboss.weld.ejb.EjbDescriptors.add(EjbDescriptors.java:111) at org.jboss.weld.ejb.EjbDescriptors.addAll(EjbDescriptors.java:166) at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:78) at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:197) at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:174) at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:295) at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.initialize(BootstrapBean.java:136) -- 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

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (WELD-351) Provide relevant failure message when using old maven

by Ondrej Skutka (JIRA)

Provide relevant failure message when using old maven ----------------------------------------------------- Key: WELD-351 URL: https://jira.jboss.org/jira/browse/WELD-351 Project: Weld Issue Type: Feature Request Components: Infrastructure Affects Versions: 1.0.0.GA Environment: Maven version: 2.0.8 Reporter: Ondrej Skutka Fix For: 1.0.1.CR1 When building (core) with maven <2.0.10, a fatal error is thrown with message "Failed to validate POM for project org.jboss.weld:weld-core" before the maven-enforcer-plugin comes into use. So the message doesn't indicate that the problem is in fact in maven's version. I suggest using maven's <prerequisite> tag to enforce maven >=2.0.10. -- 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

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (WELD-283) Documentation issues

by Jozef Hartinger (JIRA)

Documentation issues -------------------- Key: WELD-283 URL: https://jira.jboss.org/jira/browse/WELD-283 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.0.GA Reporter: Jozef Hartinger Fix For: 1.0.0.GA Global problems - a significant number of links is missing the value of href attribute (these links point nowhere) - the JBoss AS 5.2.x have become obsolete recently (changed to 6.0.0.M1) - the documentation references this obsolete version. i.e. Chapters 6, section 18.1 - there is a number of unnecessary blank pages in the PDF version - Section 2.1.2. Scope - there is a missing *want* in the Note in the sentence: "If you don't the bean to live in the session indefinitely..." - Section 6.2 Deploying to JBoss AS - there is a missing space in the sentence "Create a new file namedlocal.build.properties ..." - Section 6.2 Deploying to JBoss AS - is not finished - there is a TODO at the very end of the section - Secion 7.1. The numberguess example in depth - the numbers which mark an important line of a code sample (1), (2), etc... are broken in the second sample of the section (web.xml). They are placed on wrong places (wrong line, beggining of the line instead of end) and they are followed by "ml_plain">" in the HTML version. Besides, I would emphasize more the benefit of the typesafe resolution i.e. in section 1.2 - (that all the unsatisfied and ambiguous dependencies are discovered at the deployment time - you do not need to click anything to find out that the you set some dependencies wrong - more formal verification) - I don't say it is not there already. I just had a feeling that it is not stated explicitly enough. -- 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

15 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (WELD-320) JBoss links & version invalid in getting started guide

by Steven Boscarine (JIRA)

JBoss links & version invalid in getting started guide ------------------------------------------------------ Key: WELD-320 URL: https://jira.jboss.org/jira/browse/WELD-320 Project: Weld Issue Type: Bug Components: Documentation Reporter: Steven Boscarine The download link is wrong. Also, isn't it supposed to be JBoss 6? <p> <a id="jbossas"> To deploy the examples to JBoss AS, you'll need </a><a class="ulink" href="">JBoss AS 5.2.0.Beta1</a> or above. If a release of the JBoss AS 5.2 line isn't yet available, you can download a <a class="ulink" href="">nightly snapshot</a>. The reason JBoss AS 5.2.0.Beta1 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go! </p> -- 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

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (WELD-278) Fix distribution management so that release plugin transforms properly

by Pete Muir (JIRA)

Fix distribution management so that release plugin transforms properly ---------------------------------------------------------------------- Key: WELD-278 URL: https://jira.jboss.org/jira/browse/WELD-278 Project: Weld Issue Type: Task Components: Infrastructure 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

15 years, 1 month

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2009