December 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-204) ProcessInjectionTarget not fired for Servlet, Filter, Servlet Listener and Tag Library Listener

by Jozef Hartinger (JIRA)

ProcessInjectionTarget not fired for Servlet, Filter, Servlet Listener and Tag Library Listener ----------------------------------------------------------------------------------------------- Key: WELD-204 URL: https://jira.jboss.org/jira/browse/WELD-204 Project: Weld Issue Type: Bug Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.CR2 org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForServletListener() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForTagLibraryListener() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForServlet() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ProcessInjectionTargetEventTest.testEventFiredForFilter() -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-357) @Inject constructor on session bean does not work

by David Allen (JIRA)

@Inject constructor on session bean does not work ------------------------------------------------- Key: WELD-357 URL: https://jira.jboss.org/jira/browse/WELD-357 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: David Allen Fix For: 1.0.1.CR1 The following test does not work in the JBoss AS containers: org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest::testConstructorAnnotatedInjectCalled -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (WELDINT-29) Add deployers for injection between Weld and MC

by Kabir Khan (JIRA)

Add deployers for injection between Weld and MC ----------------------------------------------- Key: WELDINT-29 URL: https://jira.jboss.org/jira/browse/WELDINT-29 Project: Weld Integration Issue Type: Feature Request Components: Deployer Reporter: Kabir Khan Assignee: Pete Muir Fix For: 5.2.0.Beta5 On 10 Nov 2009, at 10:39, Kabir Khan wrote: Hi Pete, I've done a fair bit of work on https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk/deployer which I need to commit. This falls into two parts. 1) Moving some of the hardcoded strings created by the deployers into DeployersUtils utility methods 2) New stuff for mc-weld integration I know you guys are busy releasing everything and don't want to fuck things up for you. So first of all, is there a code freeze on this repository at the moment? <pete>No code freeze officially. I did a new release of weld-int last night with the latest Weld 1.0.0 code. If you could hold until later today, so I can verify all, that would be great :-)</pete> Secondly, it looks like the AS 5.2 releases are taken from trunk? <pete>Yes.</pete> The stuff for 1) is pretty trivial. Apart from those the changes for 2) are all new classes, but this depends on snapshot versions of MC kernel and deployers. Unless you have any objections or better suggestions, I think I will create a new module for my 2) work which hardcodes the dependencies to those snapshot versions and which is excluded from the main build unless run with a special profile untill we have some proper MC releases. <pete>Yes, quite happy with that!</pete> -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (WELDINT-26) Correctly extract exception message from Tomcat

by Pete Muir (JIRA)

Correctly extract exception message from Tomcat ----------------------------------------------- Key: WELDINT-26 URL: https://jira.jboss.org/jira/browse/WELDINT-26 Project: Weld Integration Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir org.jboss.jsr299.tck.tests.lookup.injectionpoint.broken.not.bean.InjectionPointTest -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (CDITCK-67) test applications failed to deploy due to "unresolvable ambiguous EL name exists"

by Hong Zhang (JIRA)

test applications failed to deploy due to "unresolvable ambiguous EL name exists" --------------------------------------------------------------------------------- Key: CDITCK-67 URL: https://jira.jboss.org/jira/browse/CDITCK-67 Project: CDI TCK Issue Type: CTS Challenge Security Level: Public (Everyone can see) Affects Versions: 1.0.0.GA Environment: Ubuntu/X86 Reporter: Hong Zhang Priority: Critical I am investigation the test failures for org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest class. The deployment failed for the application due to some validation failure in weld RI code. >From the stack trace, it found two beans with name "farmer": Caused by: org.jboss.weld.DeploymentException: An unresolvable ambiguous EL name exists for farmer; found [org.jboss.weld.bean-/home/hzhang/files/sun/glassfishv3/glassfish/domains/domain1/applications/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest_jar/-SessionBean-LazyFarmer, org.jboss.weld.bean-/home/hzhang/files/sun/glassfishv3/glassfish/domains/domain1/applications/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest/org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest_jar/-SessionBean-Farmer] at org.jboss.weld.Validator.validateBeanNames(Validator.java:321) at org.jboss.weld.Validator.validateDeployment(Validator.java:273) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:389) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:166) So I tried to step into weld RI code to see why this happened. This is what I found so far: 1. The Farmer class has a @Named annotation, and AbstractBean.initName() would set its name as the default name (the simple name of the class): "farmer". 2. The LazyFarmer class extends from Farmer class and does not have a @Named annotation, so AbstractBean.initName() does not assign any name to it. Its name is later assigned in AbstractBean.postSpecialize using its specialized bean's name (this.name = getSpecializedBean().getName()). Its specialized bean is its super class Farmer, and Farmer's name is "farmer". So now LazyFarmer's name is also "farmer". Seems from the RI code, it's expected these two beans will have the same name "farmer". So not sure how this test would pass with the current TCK/RI. This is also the cause of the deployment failure for org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest -- 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, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (WELD-249) Review and update Getting Started Developing Weld wiki page

by Pete Muir (JIRA)

Review and update Getting Started Developing Weld wiki page ----------------------------------------------------------- Key: WELD-249 URL: https://jira.jboss.org/jira/browse/WELD-249 Project: Weld Issue Type: Feature Request Components: Documentation 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

14 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (WELDX-52) Support Servlet injection on Jetty

by Pete Muir (JIRA)

Support Servlet injection on Jetty ---------------------------------- Key: WELDX-52 URL: https://jira.jboss.org/jira/browse/WELDX-52 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Reporter: Pete Muir Priority: Critical 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-215) Deployment issues with numberguess example

by Christian Bauer (JIRA)

Deployment issues with numberguess example ------------------------------------------ Key: WELD-215 URL: https://jira.jboss.org/jira/browse/WELD-215 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.CR1 Reporter: Christian Bauer Priority: Minor The CR1 release has the following issues with /examples/wicket/numberguess: 1. There is an empty org/jboss/webbeans/examples/ directory in the src/ folder. 2. slf4j is completely missing in the WAR, neither API nor implementation is deployed. 3. The main Weld JARs are also missing, only weld-wicket.jar is being deployed. 4. After copying slf4j, log4j, and weld-servlet.jar, I get this exception on startup: Oct 19, 2009 4:17:20 PM org.apache.catalina.core.StandardContext filterStart SEVERE: Exception starting filter wicket.numberguess-example org.apache.wicket.WicketRuntimeException: There is no application attached to current thread main at org.apache.wicket.Application.get(Application.java:179) at org.jboss.weld.wicket.BeanManagerLookup.getBeanManager(BeanManagerLookup.java:76) at org.jboss.weld.wicket.WeldApplication.<init>(WeldApplication.java:39) at org.jboss.weld.examples.wicket.SampleApplication.<init>(SampleApplication.java:5) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:678) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3800) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4450) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:987) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:583) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) (Which is btw the same I get in my own weld-wicket test app after upgrading from webbeans 10-day-old-SVN trunk.) -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (WELDX-36) Dependence on portlet-api due to scanning of a class

by Pete Muir (JIRA)

Dependence on portlet-api due to scanning of a class ---------------------------------------------------- Key: WELDX-36 URL: https://jira.jboss.org/jira/browse/WELDX-36 Project: Weld Extensions Issue Type: Bug Components: Wicket support Reporter: Pete Muir Fix For: Wicket 1.0.0.BETA2 -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-348) Conversation implementation is not context-aware

by Nicklas Karlsson (JIRA)

Conversation implementation is not context-aware ------------------------------------------------ Key: WELD-348 URL: https://jira.jboss.org/jira/browse/WELD-348 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Assignee: Nicklas Karlsson Priority: Minor Fix For: 1.0.1.CR1 The spec says "If any method of Conversation is called when the conversation scope is not active, a ContextNotActiveException is thrown" this is not the case currently. ConversationImpl needs a reference to the current conversation scope (or lookup it) in order to check the active state on entry There is apparently no TCK coverage for this yet? -- 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, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2009