June 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-905) @Alternative broken if multiple implementations are in the classpath

by Gerhard Petracek (JIRA)

@Alternative broken if multiple implementations are in the classpath -------------------------------------------------------------------- Key: WELD-905 URL: https://issues.jboss.org/browse/WELD-905 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.1.1.Final Reporter: Gerhard Petracek Priority: Critical example (broken): bean-archive #1: - BeanA - BeanA1 (@Alternative) - beans.xml (activates BeanA1 as alternative) bean-archive #2: - BeanA2 (@Typed()) - beans.xml (empty) BeanA1 doesn't get used (without an error or a warning BeanA is used instead - even though BeanA1 is activated as alternative in the same bean-archive) example (working): bean-archive #1: - BeanA - BeanA1 (@Alternative) - beans.xml (activates BeanA1 as alternative) jar #2 (no bean-archive): - BeanA2 (@Typed()) BeanA1 gets activated as alternative (as expected) because jar #2 isn't a bean-archive (that's the difference compared to the broken example). that prevents >e.g.< portable extensions from providing extension-points to work around the broken @Alternative spec. section. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
15
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-926) Weld Servlet still uses old Google Collections instead of Guava

by Sebastian Schaffert (JIRA)

Weld Servlet still uses old Google Collections instead of Guava --------------------------------------------------------------- Key: WELD-926 URL: https://issues.jboss.org/browse/WELD-926 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.1.1.Final Reporter: Sebastian Schaffert Even though WELD-564 is fixed, the latest version of Weld Servlet still includes the old Google Collections code. I think it should not contain the code at all and instead use a dependency on the library. Or at least update to the latest version of Guava. The problem is that it makes it impossible to use Guava in the same classpath as Weld. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (WELD-894) Around-Invoke interceptors should not wrap RuntimeException into WeldException

by Vlastimil Menčík (JIRA)

Around-Invoke interceptors should not wrap RuntimeException into WeldException ------------------------------------------------------------------------------ Key: WELD-894 URL: https://issues.jboss.org/browse/WELD-894 Project: Weld Issue Type: Feature Request Components: Interceptors and Decorators Affects Versions: 1.1.1.Final Reporter: Vlastimil Menčík Currently, org.jboss.weld.bean.InterceptorImpl always throws a WeldException when the invoked method throws an exception. This causes all exceptions in intercepted session bean methods to be treated as system exceptions by the EJB subsystem as WeldException is a system exception. If RuntimeExceptions were simply rethrown, such exceptions (annotated with javax.ejb.ApplicationException) could pass through the interceptor unwrapped and be recognized as application exception in the EJB sense. Of course, checked application exceptions are a bigger problem that would probably require a more sofisticated solution, that could be resolved later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2011