November 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-35) Tests for interceptor binding types with members

by Marius Bogoevici (JIRA)

Tests for interceptor binding types with members ------------------------------------------------ Key: CDITCK-35 URL: https://jira.jboss.org/jira/browse/CDITCK-35 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta4 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.0.0.CR1 Must validate that: - interceptor binding types with members are applied according to the values set on those members - @Nonbinding is applied correctly. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (WELD-277) @Alternative is "inherited" from class bean by producers

by Pete Muir (JIRA)

@Alternative is "inherited" from class bean by producers -------------------------------------------------------- Key: WELD-277 URL: https://jira.jboss.org/jira/browse/WELD-277 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.0.0.GA -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Closed: (CDITCK-20) Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-20?page=com.atlassian.jira.plug... ] Pete Muir closed CDITCK-20. --------------------------- Resolution: Rejected Assignee: Pete Muir (was: Jozef Hartinger) Ok, I think I misinterpreted the spec here. Let's not add this test. > Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event > --------------------------------------------------------------------------------------------------------------------------- > > Key: CDITCK-20 > URL: https://jira.jboss.org/jira/browse/CDITCK-20 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.0.0.GA > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDITCK-20) Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-20?page=com.atlassian.jira.plug... ] Pete Muir commented on CDITCK-20: --------------------------------- Ok, I agree, I think this is a spec bug. Let me clarify with Gavin. Maybe check in the changes commented out for now? > Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event > --------------------------------------------------------------------------------------------------------------------------- > > Key: CDITCK-20 > URL: https://jira.jboss.org/jira/browse/CDITCK-20 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Jozef Hartinger > Fix For: 1.0.0.GA > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELDINT-27) interceptors/decorators for EJBs which are not web beans

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-27?page=com.atlassian.jira.plu... ] Marius Bogoevici updated WELDINT-27: ------------------------------------ Component/s: JBoss EJB 3.0 integration > interceptors/decorators for EJBs which are not web beans > -------------------------------------------------------- > > Key: WELDINT-27 > URL: https://jira.jboss.org/jira/browse/WELDINT-27 > Project: Weld Integration > Issue Type: Feature Request > Components: JBoss EJB 3.0 integration > Reporter: Gavin King > Assignee: Marius Bogoevici > Fix For: 5.2.0.Beta6 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-45) interceptors/decorators for EJBs which are not web beans

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-45?page=com.atlassian.jira.plugin... ] Marius Bogoevici updated WELD-45: --------------------------------- Parent: (was: WELD-41) Issue Type: Feature Request (was: Sub-task) > interceptors/decorators for EJBs which are not web beans > -------------------------------------------------------- > > Key: WELD-45 > URL: https://jira.jboss.org/jira/browse/WELD-45 > Project: Weld > Issue Type: Feature Request > Reporter: Gavin King > Assignee: Marius Bogoevici > Fix For: 5.2.0.Beta6 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDITCK-20) Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event

by Jozef Hartinger (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-20?page=com.atlassian.jira.plug... ] Jozef Hartinger commented on CDITCK-20: --------------------------------------- Pete, I am not sure I understand perfectly. I suppose you want to test that an event like this event.select(BreakInEvent.class).fire(new CriticalBreakInEvent()) causes breakInOccurred(@Observes @Any BreakInEvent event) to be invoked while it does not cause criticalBreakInOccured(@Observes @Any CriticalBreakInEvent event) to be invoked. I implemeted this by extending an existing test, but I am waiting for confirmation. Also, I am not sure if the spec describes this correctly, since it says "An event is delivered to an observer method if the event object is assignable to the observed event type, taking type parameters into consideration." (Not the "event object is assignable" instead of "specified type is assignable") > Write a test that actually checks that the subtype is used for Event.select(), and not the type of the payload to the event > --------------------------------------------------------------------------------------------------------------------------- > > Key: CDITCK-20 > URL: https://jira.jboss.org/jira/browse/CDITCK-20 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Jozef Hartinger > Fix For: 1.0.0.GA > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (WELDX-44) Fix war:inplace target for Tomcat for numberguess example

by Dan Allen (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-44?page=com.atlassian.jira.plugi... ] Dan Allen resolved WELDX-44. ---------------------------- Fix Version/s: Servlet Containers 1.0.0.CR2 (was: Servlet Containers 1.0.0.CR3) Resolution: Done > Fix war:inplace target for Tomcat for numberguess example > --------------------------------------------------------- > > Key: WELDX-44 > URL: https://jira.jboss.org/jira/browse/WELDX-44 > Project: Weld Extensions > Issue Type: Feature Request > Components: Servlet Containers > Reporter: Pete Muir > Assignee: Dan Allen > Fix For: Servlet Containers 1.0.0.CR2 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELDX-44) Fix war:inplace target for Tomcat for numberguess example

by Dan Allen (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-44?page=com.atlassian.jira.plugi... ] Dan Allen commented on WELDX-44: -------------------------------- We had a chicken and egg problem here, because you need the BeanManager to get the CDI ELResolver to register with JSF, but the BeanManager won't be available if JSF starts first. The following fix has been put in place. The BeanManager may not have been initialized at the time JSF is initializing. Therefore, we stick in a ForwardingELResolver that delegates to the BeanManager ELResolver, which will be plugged in when it becomes available. If the ELResolver is invoked before the BeanManager is available, an IllegalStateException is thrown. Here's the back story. We should probably report this bug in Mojarra, or take it to the spec. What this comes down to is a bug in Mojarra. By the time the BeanManager is available, it may be too late to register the ELResolver because Mojarra fixes it's composite ELResolver chain the first time Application.getELResolver() is called (after that, it's not considering the ELResolvers registered with Application.addELResolver() any longer). That happens when the Weld listener starts after the JSF listener, which is the case on Tomcat <= 6.0.18. Mojarra should be rebuilding it's composite resolver if a call is made to addELResolver(). The spec states that the ELResolvers must be consulted in the order in which they are registered. The only restriction is that ELResolvers cannot be registered *after* the first request has been serviced. We are registering before that time. And although the addELResolver in ApplicationImpl (Mojarra) verifies a request has not been serviced, it does not rebuild the composite EL resolver if the ELResolver is added legally. Actually, the spec isn't even really clear about the restriction about not calling addELResolver() after the first request is serviced. That is really an implied fact when you consider all other facts. It really should be stated explicitly in the JavaDoc (or, it should be allowed and the restriction removed in the impl). > Fix war:inplace target for Tomcat for numberguess example > --------------------------------------------------------- > > Key: WELDX-44 > URL: https://jira.jboss.org/jira/browse/WELDX-44 > Project: Weld Extensions > Issue Type: Feature Request > Components: Servlet Containers > Reporter: Pete Muir > Assignee: Dan Allen > Fix For: Servlet Containers 1.0.0.CR3 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-47) Rename isDeploymentError to isDeploymentProblem

by Pete Muir (JIRA)

Rename isDeploymentError to isDeploymentProblem ----------------------------------------------- Key: CDITCK-47 URL: https://jira.jboss.org/jira/browse/CDITCK-47 Project: CDI TCK Issue Type: Task Security Level: Public (Everyone can see) Reporter: Pete Muir Fix For: 1.0.0.CR7 -- 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, 4 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2009