February 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-452) Type parameter should not be required to be a concrete type

by Pieter Martin (JIRA)

Type parameter should not be required to be a concrete type ----------------------------------------------------------- Key: WELD-452 URL: https://jira.jboss.org/jira/browse/WELD-452 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: Linux, 1.6.0_15 Reporter: Pieter Martin When injecting parameterized types weld gives an error on start up. The code below fails with Exception in thread "main" org.jboss.weld.exceptions.DefinitionException: WELD-000023 Type parameter must be a concrete type: public com.rorotika.ci.model.ModelSolution com.rorotika.executor.ci.CIExecutor.getModelSolution() at org.jboss.weld.bean.AbstractProducerBean.checkProducerReturnType(AbstractProducerBean.java:180) @Inject @Parameterized Parameterized1<Parameterized2<Double>> parameterized; ... @Produces @Parameterized public Parameterized1<Parameterized2<Double>> getParameterized() { return new Parameterized1(); } -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Commented: (WELDINT-43) web.xml configured jsf error-page throws ContextNotActiveException

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDINT-43?page=com.atlassian.jira.plu... ] Pete Muir commented on WELDINT-43: ---------------------------------- Remy recommends using either a valve, or a filter mapped on ERROR. > web.xml configured jsf error-page throws ContextNotActiveException > ------------------------------------------------------------------ > > Key: WELDINT-43 > URL: https://jira.jboss.org/jira/browse/WELDINT-43 > Project: Weld Integration > Issue Type: Bug > Environment: glassfish V3 prelude, jsf 2.0.0-SNAPSHOT (May 17 2009) > Reporter: Guy Veraghtert > Assignee: Pete Muir > Fix For: 6.0.0.CR1 > > > An ContextNotActiveException is thrown by Web beans when the container tries to forward to a jsf error-page (configured in web.xml). See forum reference. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (WELD-450) Create portable Java SE bootstrap API

by Matthieu Chase Heimer (JIRA)

Create portable Java SE bootstrap API ------------------------------------- Key: WELD-450 URL: https://jira.jboss.org/jira/browse/WELD-450 Project: Weld Issue Type: Feature Request Components: Spec Affects Versions: 1.0.1.CR2 Environment: any Reporter: Matthieu Chase Heimer Priority: Minor Weld has a Java SE bootstrapping API see: https://jira.jboss.org/jira/browse/WELDX-50 It is not portable. The spec should outline a portable client bootstrap API for SE environments. Something like: CDIContainer cdi = CDIContainer.createCDIContainer(); Even before the spec includes one it would be nice if Weld included a *possible* implementation of a vendor neutral SE bootstrap API. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (WELD-384) Allow Portable Extensions to access qualifiers for fired Events

by Jordan Ganoff (JIRA)

Allow Portable Extensions to access qualifiers for fired Events --------------------------------------------------------------- Key: WELD-384 URL: https://jira.jboss.org/jira/browse/WELD-384 Project: Weld Issue Type: Feature Request Components: CDI API Affects Versions: 1.0.0.GA Reporter: Jordan Ganoff It is currently not possible to access the qualifiers on an event being fired. In order to support routing of Events outside the Weld-core the qualifiers need to be accessible. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Commented: (WELDX-23) Support servlet injection on Jetty

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-23?page=com.atlassian.jira.plugi... ] Pete Muir commented on WELDX-23: -------------------------------- Ok, Injection stuff makes sense. Can you add this explanation to the comments on the class? Update the patch with the TCCL chages (just upload a new patch with the same name, JIRA will take care of it then). > Support servlet injection on Jetty > ---------------------------------- > > Key: WELDX-23 > URL: https://jira.jboss.org/jira/browse/WELDX-23 > Project: Weld Extensions > Issue Type: Feature Request > Components: Servlet Containers > Reporter: Pete Muir > Assignee: Matija Mazi > Attachments: jetty-injection.patch, myapp-context.xml > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-117) release-notes.txt empty

by Jozef Hartinger (JIRA)

release-notes.txt empty ----------------------- Key: CDITCK-117 URL: https://jira.jboss.org/jira/browse/CDITCK-117 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.GA Reporter: Jozef Hartinger The release-notes.txt file bundled with the distribution does not contain any issues. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (WELD-449) Documentation issue

by Martin Gencur (JIRA)

Documentation issue ------------------- Key: WELD-449 URL: https://jira.jboss.org/jira/browse/WELD-449 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.GA Reporter: Martin Gencur Priority: Optional Section 18.1. (Using Weld with JBoss AS) of Weld documentation contains updating of JBoss AS with Weld. It is no more true that JBoss AS is being updated with "ant update" command. Now it is being updated with mvn -Pupdate-jboss-as. Maybe it should be documented although when you type "ant update" the error message is shown which leads you to using "mvn" command. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Commented: (WELDX-23) Support servlet injection on Jetty

by Matija Mazi (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-23?page=com.atlassian.jira.plugi... ] Matija Mazi commented on WELDX-23: ---------------------------------- The TCCL swap remained from early testing when it seemed necessary, but now I see it's redundant so I'll remove it. (Should I submit a new patch?) WeldInjection's superclass Injection is ment to represent an injection into a single field or setter method (an "injection point"). So for example, if there is a bean with three injection points, Jetty expects three Injection instances to be created, but instead we only create a single WeldInjection that takes care of it all. That is much easier to implement; otherwise we'd have to duplicate some logic that's already done by Weld, or do some more serious hacking into Jetty. The logic that determines which Injections will be used at all resides outside Injection (in InjectionCollection.add(..)); it checks whether the Injection seems valid. In order for WeldInjection to seem valid, it's enough to make sure that WeldInjection.getTarget() doesn't return null. It now returns the bean's toString() method that's always there. > Support servlet injection on Jetty > ---------------------------------- > > Key: WELDX-23 > URL: https://jira.jboss.org/jira/browse/WELDX-23 > Project: Weld Extensions > Issue Type: Feature Request > Components: Servlet Containers > Reporter: Pete Muir > Assignee: Matija Mazi > Attachments: jetty-injection.patch, myapp-context.xml > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (WELD-444) onMessage of MDB causes NullPointerException

by John Leed (JIRA)

onMessage of MDB causes NullPointerException --------------------------------------------- Key: WELD-444 URL: https://jira.jboss.org/jira/browse/WELD-444 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Affects Versions: 1.0.1.CR2 Environment: Glassfish v3 with weld-integration 3.0.1b05 (self-patched to fix https://glassfish.dev.java.net/issues/show_bug.cgi?id=11435) Reporter: John Leed Unlike with Weld 1.0.0 SP4, I can now deploy my EJB module that has an MDB. However, when onMessage gets called I get the following: SEVERE: MDB00050: Message-driven bean [Core_Framework:EmailConsumerBean]: Exception in creating message-driven ejb : [java.lang.NullPointerException] SEVERE: java.lang.NullPointerException java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.createInjectionTarget(BeanManagerImpl.java:1132) at org.glassfish.weld.services.JCDIServiceImpl.injectEJBInstance(JCDIServiceImpl.java:138) at com.sun.ejb.containers.BaseContainer.injectEjbInstance(BaseContainer.java:1603) at com.sun.ejb.containers.MessageBeanContainer.createMessageDrivenEJB(MessageBeanContainer.java:697) at com.sun.ejb.containers.MessageBeanContainer.access$100(MessageBeanContainer.java:95) at com.sun.ejb.containers.MessageBeanContainer$MessageBeanContextFactory.create(MessageBeanContainer.java:478) at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:200) at com.sun.ejb.containers.MessageBeanContainer._getContext(MessageBeanContainer.java:542) at com.sun.ejb.containers.BaseContainer.getContext(BaseContainer.java:2418) at com.sun.ejb.containers.MessageBeanContainer.beforeMessageDelivery(MessageBeanContainer.java:979) at com.sun.ejb.containers.MessageBeanListenerImpl.beforeMessageDelivery(MessageBeanListenerImpl.java:72) at com.sun.enterprise.connectors.inbound.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:134) at $Proxy521.beforeDelivery(Unknown Source) at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:245) at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:92) at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:492) at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:528) SEVERE: MQRA:OMR:run:Caught Exception from onMessage():Redelivering:Core_Framework:EmailConsumerBean: Message-driven bean invocation closed by container SEVERE: MDB00042: [Core_Framework:EmailConsumerBean]: No invocation for message [] SEVERE: MDB00050: Message-driven bean [Core_Framework:EmailConsumerBean]: Exception in creating message-driven ejb : [java.lang.NullPointerException] SEVERE: java.lang.NullPointerException java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.createInjectionTarget(BeanManagerImpl.java:1132) at org.glassfish.weld.services.JCDIServiceImpl.injectEJBInstance(JCDIServiceImpl.java:138) at com.sun.ejb.containers.BaseContainer.injectEjbInstance(BaseContainer.java:1603) at com.sun.ejb.containers.MessageBeanContainer.createMessageDrivenEJB(MessageBeanContainer.java:697) at com.sun.ejb.containers.MessageBeanContainer.access$100(MessageBeanContainer.java:95) at com.sun.ejb.containers.MessageBeanContainer$MessageBeanContextFactory.create(MessageBeanContainer.java:478) at com.sun.ejb.containers.util.pool.NonBlockingPool.getObject(NonBlockingPool.java:200) at com.sun.ejb.containers.MessageBeanContainer._getContext(MessageBeanContainer.java:542) at com.sun.ejb.containers.BaseContainer.getContext(BaseContainer.java:2418) at com.sun.ejb.containers.MessageBeanContainer.beforeMessageDelivery(MessageBeanContainer.java:979) at com.sun.ejb.containers.MessageBeanListenerImpl.beforeMessageDelivery(MessageBeanListenerImpl.java:72) at com.sun.enterprise.connectors.inbound.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:134) at $Proxy521.beforeDelivery(Unknown Source) at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:245) at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:92) at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:492) at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:528) SEVERE: MQRA:OMR:run:Caught Exception from onMessage():Redelivering:Core_Framework:EmailConsumerBean: Message-driven bean invocation closed by container SEVERE: MQRA:OMR:run:Exhausted redeliveryAttempts-msg=com.sun.messaging.jms.ra.DirectObjectPacket@1656ed6 SEVERE: MQRA:OMR:run:Exhausted redeliveryAttempts-spec=ActvationSpec configuration= DestinationType =javax.jms.Queue Destination =EmailQueue MessageSelector =null AcknowledgeMode =Auto-acknowledge SubscriptionDurability =NonDurable useSharedSubscriptionInClusteredContainer=true ClientId =null SubscriptionName =null EndpointPoolMaxSize =32 EndpointPoolSteadySize =0 EndpointPoolResizeCount =8 EndpointPoolResizeTimeout =600 EndpointExceptionRedeliveryAttempts =1 EndpointExceptionRedeliveryInterval =500 SendUndeliverableMsgsToDMQ =true GroupName =null RAUID =null InClusteredContainer =false MdbName =null UserName =null EnableRADirect =true EnableAPIDirect =false AddressList (in effect) =localhost:26703,localhost options =null SEVERE: MQRA:OMR:run:Message returned & marked for routing to the DMQ SEVERE: MQRA:OMR:run:omrId=0:Acked Undeliverable-Msg=com.sun.messaging.jms.ra.DirectObjectPacket@1656ed6 SEVERE: MDB00042: [Core_Framework:EmailConsumerBean]: No invocation for message [] WARNING: [MDBContainer] Current thread done cleanup()... If I remove the beans.xml, everything works fine. -- 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, 1 month

2
9
0 / 0

[JBoss JIRA] Commented: (WELDX-23) Support servlet injection on Jetty

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-23?page=com.atlassian.jira.plugi... ] Pete Muir commented on WELDX-23: -------------------------------- I reviewed the patch. Could you explain a bit more why you need to adjust the TCCL? And also about the hack on WeldInjection? > Support servlet injection on Jetty > ---------------------------------- > > Key: WELDX-23 > URL: https://jira.jboss.org/jira/browse/WELDX-23 > Project: Weld Extensions > Issue Type: Feature Request > Components: Servlet Containers > Reporter: Pete Muir > Assignee: Matija Mazi > Attachments: jetty-injection.patch, myapp-context.xml > > -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues February 2010