March 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-687) Refactoring InstantiatorFactory to allow per-deployment configuration

by Marius Bogoevici (JIRA)

Refactoring InstantiatorFactory to allow per-deployment configuration --------------------------------------------------------------------- Key: WELD-687 URL: https://jira.jboss.org/browse/WELD-687 Project: Weld Issue Type: Feature Request Affects Versions: 1.1.0.Beta1 Reporter: Marius Bogoevici Fix For: 1.1.0.Beta2 InstantiatorFactory is currently using static fields for storing the enabled/disabled status for unsafe instantiators, as well as the instantiator that should be used. In a shared library scenario, the instantiator factory will be enabled if at least one of the deployed applications contains the META-INF/org.jboss.weld.enableUnsafeProxies resource. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
14
0 / 0

[JBoss JIRA] Created: (WELD-571) Interceptors not working for dependent scoped beans when using InjectionTarget

by Francois Swiegers (JIRA)

Interceptors not working for dependent scoped beans when using InjectionTarget ------------------------------------------------------------------------------ Key: WELD-571 URL: https://jira.jboss.org/browse/WELD-571 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Francois Swiegers When creating an intercepted bean of dependent scope using an InjectionTarget, the interceptor is not active. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
18
0 / 0

[JBoss JIRA] Created: (WELD-655) maven-jetty-plugin not configured correctly

by Jozef Hartinger (JIRA)

maven-jetty-plugin not configured correctly ------------------------------------------- Key: WELD-655 URL: https://jira.jboss.org/browse/WELD-655 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.1.0.Beta1 Reporter: Jozef Hartinger Fix For: 1.1.0.Beta2 Following instructions from the reference documentation (Chapter 6.5. Deploying to Jetty) I get the following error after running "mvn war:inplace jetty:run -Pjetty" [ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.21:run (default-cli) on project weld-jsf-numberguess: jetty-env.xml file does not exist at location /home/jharting/jboss/testing/Weld-1.1.0.Beta1/weld-1.1.0.Beta1/examples/jsf/numberguess/src/main/resources/jetty-env.xml -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.21:run (default-cli) on project weld-jsf-numberguess: jetty-env.xml file does not exist at location /home/jharting/jboss/testing/Weld-1.1.0.Beta1/weld-1.1.0.Beta1/examples/jsf/numberguess/src/main/resources/jetty-env.xml at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: jetty-env.xml file does not exist at location /home/jharting/jboss/testing/Weld-1.1.0.Beta1/weld-1.1.0.Beta1/examples/jsf/numberguess/src/main/resources/jetty-env.xml at org.mortbay.jetty.plugin.AbstractJettyRunMojo.checkPomConfiguration(AbstractJettyRunMojo.java:258) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:382) at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210) at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) ... 19 more The jetty-env.xml file is present in src/main/webapp-jetty/WEB-INF/jetty-env.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
13
0 / 0

[JBoss JIRA] Created: (WELD-816) Adding interceptors and Decorators in the AfterBeanDiscovery event does not work

by Stuart Douglas (JIRA)

Adding interceptors and Decorators in the AfterBeanDiscovery event does not work -------------------------------------------------------------------------------- Key: WELD-816 URL: https://issues.jboss.org/browse/WELD-816 Project: Weld Issue Type: Bug Reporter: Stuart Douglas -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (WELD-853) @AroundInvoke annotations added by SPI are ignored

by Stuart Douglas (JIRA)

@AroundInvoke annotations added by SPI are ignored -------------------------------------------------- Key: WELD-853 URL: https://issues.jboss.org/browse/WELD-853 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Final Reporter: Stuart Douglas There should be a test for this however it has been reverted by this commit: https://github.com/weld/core/commit/562d55d27938f01b9f1a793f161540f681d51f47 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (WELD-731) Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5)

by Dan Allen (JIRA)

Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5) --------------------------------------------------------------------------------- Key: WELD-731 URL: https://jira.jboss.org/browse/WELD-731 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Dan Allen Fix For: 1.1.0.CR1 It's possible for the Weld servlet listener to be proactive and bind the BeanManager to JNDI when the naming context is read/write, as it is in JBoss AS and EAP 5. There's another good reason why this needs to be done. JBoss AS does not support defining naming resources in context.xml (which on JBoss AS is WEB-INF/context.xml). Therefore, there's no other way to push the BeanManager into JNDI. The logic for this feature is pretty straightforward. Look for the BeanManager in JNDI. If it's not there, attempt to put it there. If that fails, just log a warning message that the BeanManager will not be available in JNDI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

7
11
0 / 0

[JBoss JIRA] Created: (WELD-413) It is not possible to add identical beans through BeforeBeanDiscovery.addAnnotatedType

by Stuart Douglas (JIRA)

It is not possible to add identical beans through BeforeBeanDiscovery.addAnnotatedType -------------------------------------------------------------------------------------- Key: WELD-413 URL: https://jira.jboss.org/jira/browse/WELD-413 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.CR1 Reporter: Stuart Douglas Priority: Minor Adding a bean that is exactly the same as an existing bean results in the added bean being ignored. I can't think of a use case for having two beans exactly the same, however it still should work, and may be a symptom of a larger problem. -- 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

12 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (WELD-680) Weld tests fail on IBM JDK

by Peter Lenyi (JIRA)

Weld tests fail on IBM JDK -------------------------- Key: WELD-680 URL: https://jira.jboss.org/browse/WELD-680 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Beta2 Environment: Linux, IBM JDK 1.5 Reporter: Peter Lenyi Out of 3 test runs on IBM JDK, following failures occurred: * org.jboss.weld.atinject.tck - 1 failure - on 2 test runs * org.jboss.weld.environment.se.test - 10 failures - on 3 test runs * org.jboss.weld.tests.injectionPoint - 1 failure - on 1 test run None of these failures occurred on Sun JDK. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (WELD-820) When invoking a method that is not intercepted, invocations on this are intercepted/decorated

by Marius Bogoevici (JIRA)

When invoking a method that is not intercepted, invocations on this are intercepted/decorated --------------------------------------------------------------------------------------------- Key: WELD-820 URL: https://issues.jboss.org/browse/WELD-820 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.CR4 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Priority: Critical Fix For: 1.1.0.Final Invocations on 'this' should never be intercepted/decorated, but in the specific case when a method that is neither intercepted nor decorated invokes a method that would be otherwise intercepted, the latter is intercepted/decorated/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (WELD-665) Servlet injection not working on EAP 5.1

by Pete Muir (JIRA)

Servlet injection not working on EAP 5.1 ---------------------------------------- Key: WELD-665 URL: https://jira.jboss.org/browse/WELD-665 Project: Weld Issue Type: Bug Components: Servlet Container Support Reporter: Pete Muir Fix For: 1.1.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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2011