November 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-227) InjectionPoint implementation not passivation capable

by Jozef Hartinger (JIRA)

InjectionPoint implementation not passivation capable ----------------------------------------------------- Key: WELD-227 URL: https://jira.jboss.org/jira/browse/WELD-227 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.CR2 FieldInjectionPoint and ParameterInjectionPoint are not serializable. -- 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

14 years, 6 months

2
5
0 / 0

[JBoss JIRA] Updated: (WELDINT-3) Support reporting wrapping exception to TCK

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-3?page=com.atlassian.jira.plug... ] Pete Muir updated WELDINT-3: ---------------------------- Fix Version/s: 5.2.0.Beta6 (was: 5.2.0.Beta5) > Support reporting wrapping exception to TCK > ------------------------------------------- > > Key: WELDINT-3 > URL: https://jira.jboss.org/jira/browse/WELDINT-3 > Project: Weld Integration > Issue Type: Bug > Reporter: Pete Muir > Fix For: 5.2.0.Beta6 > > > org.jboss.jsr299.tck.tests.deployment.lifecycle.broken.addDefinitionError.AddDefinitionErrorTest.testObserverDefinitionErrorTreatedAsDefinitionError() > org.jboss.jsr299.tck.tests.deployment.lifecycle.broken.addDeploymentProblem.AddDeploymentProblemTest.testObserverDeploymentProblemTreatedAsDeploymentError() > org.jboss.jsr299.tck.tests.deployment.lifecycle.broken.beanDiscoveryMethodThrowsException.BeforeBeanDiscoveryThrowsExceptionTest.testThrowsException() > org.jboss.jsr299.tck.tests.deployment.lifecycle.broken.exceptionInAfterBeanDiscoveryObserver.AfterBeanDiscoveryObserverExecutionFailureTest.testObserverFailureTreatedAsDefinitionError() > org.jboss.jsr299.tck.tests.deployment.lifecycle.broken.exceptionInAfterBeanValidationObserver.AfterDeploymentValidationObserverExecutionFailureTest.testObserverFailureTreatedAsDeploymentError() > org.jboss.jsr299.tck.tests.deployment.lifecycle.broken.passivatingScope.AddingPassivatingScopeTest.testAddingScopeType() -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELDINT-1) Implement module structure for JBoss AS

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-1?page=com.atlassian.jira.plug... ] Pete Muir updated WELDINT-1: ---------------------------- Fix Version/s: 5.2.0.Beta6 (was: 5.2.0.Beta5) > Implement module structure for JBoss AS > --------------------------------------- > > Key: WELDINT-1 > URL: https://jira.jboss.org/jira/browse/WELDINT-1 > Project: Weld Integration > Issue Type: Feature Request > Components: Deployer > Reporter: Pete Muir > Assignee: Ales Justin > Priority: Blocker > Fix For: 5.2.0.Beta6 > > > We need to provide the deployment structure to WB using BeanDeploymentArchive structure > http://anonsvn.jboss.org/repos/webbeans/ri/trunk/spi/src/main/java/org/jb... -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELDINT-2) Problems using WebBeans in multiple Applications (EARS)

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-2?page=com.atlassian.jira.plug... ] Pete Muir updated WELDINT-2: ---------------------------- Fix Version/s: 5.2.0.Beta6 (was: 5.2.0.Beta5) > Problems using WebBeans in multiple Applications (EARS) > ------------------------------------------------------- > > Key: WELDINT-2 > URL: https://jira.jboss.org/jira/browse/WELDINT-2 > Project: Weld Integration > Issue Type: Bug > Components: Deployer > Environment: JBoss 5.0.1.GA, > TEsted with WebBean 1.0.0.Preview and today snapshot > Reporter: Martin Eigenbrodt > Assignee: Ales Justin > Priority: Critical > Fix For: 5.2.0.Beta6 > > Attachments: bug.zip > > > Multiple EARS that use webbeans seem to interfer. > I've prepared a simple testcase. The zip contains an ear "earA.ear" that includes a war with a simple jsf page and a backing bean. > The backing beans has got a method that is used within the jsf page: > > public String getText() { > return "Hello World!"; > } > The second ear "empty.ear" does only contain an empty beans.xml in the META-INF dir. > If you deploy just earA.ear you can view the jsf page at http://localhost:8080/EarAWar/index.jsf . It display a Heading "Test" and the line "Hello World" below. > If you now deploy the earA.ear and the empty.ear and restart, the "Hello World" will be gone. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Assigned: (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 reassigned CDITCK-20: ------------------------------- Assignee: Jozef Hartinger Jozef, would you be able to write a quick test for this on Monday? If you can't find an assertion, mark it implied. > 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.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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (WELD-18) Documentation issues

by Dan Allen (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-18?page=com.atlassian.jira.plugin... ] Dan Allen resolved WELD-18. --------------------------- Resolution: Done Peter's revisions look good. We are all set! > Documentation issues > -------------------- > > Key: WELD-18 > URL: https://jira.jboss.org/jira/browse/WELD-18 > Project: Weld > Issue Type: Bug > Components: Documentation > Affects Versions: 1.0.0.PREVIEW1 > Reporter: Jozef Hartinger > Assignee: Dan Allen > Fix For: 1.0.0.GA > > > Here are some documentation issues: > 1.) Unordered lists: > In many places in documentation, I can see list items containing commas and periods at the end of line as well as "and" at the last but one item. These should not be there. Some occurences: 1.2.1, , 1.3.1, 1.3.2, etc > 2.) Outdated source code for Game.java in section 3.4 > 3.) Java ServerFaces instead of JavaServer Faces in 3.4.2 > 4.) Section 1.3.2 unclear > Third paragraph talks about a "remove" method or "remove method annotated with @Destructor". However, the source code excerpt that follows this paragraph shows "destroy" method annotated with "@Remove". -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDITCK-19) Add a test verifying that @Current is inherited in specialization

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/CDITCK-19?page=com.atlassian.jira.plug... ] Pete Muir closed CDITCK-19. --------------------------- Fix Version/s: (was: 1.0.0.CR7) Resolution: Out of Date Assignee: Pete Muir > Add a test verifying that @Current is inherited in specialization > ----------------------------------------------------------------- > > Key: CDITCK-19 > URL: https://jira.jboss.org/jira/browse/CDITCK-19 > Project: CDI TCK > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tests > Reporter: Pete Muir > Assignee: Pete Muir > > Given > class Bean1 { > } > @Binding1 > @Specializes > class Bean2 extends Bean1{ > } > verify that Bean2 has binding @Binding1 only > Given > @Binding1 > class Bean1 { > } > @Specializes > class Bean2 extends Bean1{ > } > verify that Bean2 has bindings @Current @Binding1 only > Given > @Binding2 > class Bean1 { > } > class Bean2 extends Bean1{ > } > @Binding2 is @Inherited > Verify that Bean2 has bindings @Binding2 only -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-246) Cannot add a custom bean from a portable extension.

by Binod PG (JIRA)

Cannot add a custom bean from a portable extension. --------------------------------------------------- Key: WELD-246 URL: https://jira.jboss.org/jira/browse/WELD-246 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.CR1 Environment: GlassFish v3 and Weld 1.0.0-CR1-SP1 Reporter: Binod PG Adding a CustomBean using the AfterBeanDiscovery doesnt seem to work. The portable extension defines an interface (and a bean class that implements it) and tries to inject an instance of the interface to the servlet implementation. But it fails with the following extension. Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: interface org.glassfish.test299.ABeanInterface; binding types = [@Default]Unable to resolve any Managed Beans at org.jboss.weld.BeanManagerImpl.getBean(BeanManagerImpl.java:996) at org.jboss.weld.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:966) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:78) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:683) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:695) at org.jboss.weld.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:108) at org.glassfish.weld.services.InjectionServicesImpl.aroundInject(InjectionServicesImpl.java:123) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:47) at org.jboss.weld.SimpleInjectionTarget.inject(SimpleInjectionTarget.java:102) at org.glassfish.weld.services.JCDIServiceImpl.createManagedObject(JCDIServiceImpl.java:174) at com.sun.enterprise.container.common.impl.managedbean.ManagedBeanManagerImpl.createManagedBe an(ManagedBeanManagerImpl.java:456) at com.sun.enterprise.container.common.impl.managedbean.ManagedBeanManagerImpl.createManagedBe an(ManagedBeanManagerImpl.java:423) at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManagedObject(InjectionM anagerImpl.java:295) I have attached a test case with glassfish issue here. https://glassfish.dev.java.net/issues/show_bug.cgi?id=10658 -- 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

14 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-233) A sub-set of events are reported to Extension classes defined in jar files that are in WEB-INF/lib

by Paul Sandoz (JIRA)

A sub-set of events are reported to Extension classes defined in jar files that are in WEB-INF/lib -------------------------------------------------------------------------------------------------- Key: WELD-233 URL: https://jira.jboss.org/jira/browse/WELD-233 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.CR1 Environment: GlassFish v3 and Weld 1.0.0-CR1-SP1 Reporter: Paul Sandoz Attachments: jcditest.zip Only the following events are reported: BEFORE BEAN DISCOVERY, PROCESS ANNOTATED TYPE, AFTER BEAN DISCOVERY and AFTER DEPLOYMENT VALIDATION -- 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

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-263) Infrastructure for standard format logging and exception messages

by Pete Muir (JIRA)

Infrastructure for standard format logging and exception messages ----------------------------------------------------------------- Key: WELD-263 URL: https://jira.jboss.org/jira/browse/WELD-263 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.0.CR2 We need to support the standard format with some utility classes. http://www.seamframework.org/Weld/WeldLogAndExceptionMessageGuidelines -- 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

14 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2009