February 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-994) Passivating Beans do not allow Injection of non-serializable Instance injections

by Cody Lerum (Created) (JIRA)

Passivating Beans do not allow Injection of non-serializable Instance injections -------------------------------------------------------------------------------- Key: WELD-994 URL: https://issues.jboss.org/browse/WELD-994 Project: Weld Issue Type: Bug Environment: AS 7.0.2 WELD-000900 1.1.2 (Final) Reporter: Cody Lerum Given the following Code {code:java} @ConversationScoped @Named public class EmailTester implements Serializable { private static final long serialVersionUID = 1L; @Inject private Instance<MailMessage> mailMessage; @Inject private ActiveUser activeUser; @Inject private Messages messages; @Inject private Instance<Session> session; public void send() { MailMessage m = mailMessage.get(); m.from(activeUser.getUser()); m.to(activeUser.getUser()); m.subject("test"); m.bodyText("Blah blah blah"); m.send(session.get()); messages.info("Message Sent"); } } {code} Weld throws org.jboss.weld.exceptions.IllegalProductException: WELD-000054 Producers cannot produce non-serializable instances for injection into non-transient fields of passivating beans\\n\\nProducer\: Producer Method [Session] with qualifiers [@Any @Default] declared as [[method] @Produces @ExtensionManaged public org.jboss.seam.mail.core.MailSessionProducer.getMailSession(MailConfig)]\\nInjection Point\: org.jboss.weld.bean.builtin.InstanceImpl$InstanceInjectionPoint@2146ca: javax.faces.FacesException: #{emailTester.send()}: org.jboss.weld.exceptions.IllegalProductException: WELD-000054 Producers cannot produce non-serializable instances for injection into non-transient fields of passivating beans\\n\\nProducer\: Producer Method [Session] with qualifiers [@Any @Default] declared as [[method] @Produces @ExtensionManaged public org.jboss.seam.mail.core.MailSessionProducer.getMailSession(MailConfig)]\\nInjection Point\: org.jboss.weld.bean.builtin.InstanceImpl$InstanceInjectionPoin! t@2146ca Since a new instance is returned each time a get() is called it should not matter that the javax.mail.Session is not non-serializable -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

8
11
0 / 0

[JBoss JIRA] Created: (WELD-909) Dual faces mapping and cid parameter for conversational redirect

by Nicklas Karlsson (JIRA)

Dual faces mapping and cid parameter for conversational redirect ---------------------------------------------------------------- Key: WELD-909 URL: https://issues.jboss.org/browse/WELD-909 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.1.1.Final Reporter: Nicklas Karlsson Given a page like {code} <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core"> <h:head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> <title>Concept</title> </h:head> <h:body> <f:view> <h:form> <h:commandButton value="redirect" action="page?faces-redirect=true"/> <h:commandButton value="non-transient" action="#{backingBean.nonTransient}"/> </h:form> </f:view> </h:body> </html> {code} and a backing bean like {code} package fi.nik.concept; import javax.enterprise.context.Conversation; import javax.inject.Inject; import javax.inject.Named; @Named public class BackingBean { @Inject private Conversation conversation; public String nonTransient() { conversation.begin(); return "page?faces-redirect=true"; } } {code} clicking "redirect" with non-transient conversations work fine but clicking "non-transient" duplicates the faces mappings and cid to something like http://localhost:8080/concept/faces/faces/page.xhtml?cid=1&cid=1 and clicking "redirect" after keeps the URL like that. It works normally after that (since the faces mapping is still hit and the cid is repeated with the same value) but it looks a bit odd. Would have written a test for it but git on Windows is... a bit nonlinear at times. -- 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] (WELD-1016) Weld creates multiple interceptor instances per target instance

by Jozef Hartinger (Created) (JIRA)

Weld creates multiple interceptor instances per target instance --------------------------------------------------------------- Key: WELD-1016 URL: https://issues.jboss.org/browse/WELD-1016 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Fix For: 1.1.4.Final, 2.0.0.Final The CDI spec says: {quote} An interceptor instance is a dependent object of the object it inter-cepts. {quote} The Interceptors spec says: {quote} The lifecycle of an interceptor instance is the same as that of the target class instance with which it is associated. When the target instance is created, a corresponding interceptor instance is created for each associated interceptor class. These interceptor instances are destroyed when the target instance is removed. {quote} and also {quote} An interceptor instance may hold state. {quote} It is clear that at most one instance of an interceptor class should be created for an instance of a CDI bean. However, Weld currently creates an instance per method per target instance. Having a simple intercepted bean: {code:JAVA} @ApplicationScoped @LionBinding public class Lion public Object foo() { return null; } public Object bar() { return null; } } {code} * multiple invocations of a single method (e.g. foo()) are intercepted by the same interceptor instance * when invoking different methods on the same bean instance, every method is intercepted by a different interceptor instance - which is wrong -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

6
9
0 / 0

[JBoss JIRA] Created: (WELD-580) Around-Invoke Interceptors with wrong signature should cause DefinitionException

by Aslak Knutsen (JIRA)

Around-Invoke Interceptors with wrong signature should cause DefinitionException -------------------------------------------------------------------------------- Key: WELD-580 URL: https://jira.jboss.org/browse/WELD-580 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Aslak Knutsen Around-invoke methods have the following signature: Object <METHOD>(InvocationContext) throws Exception Interceptors that does not follow that should cause a DefinitionException. In current impl they are registered, enabled but can not be resolved on Bean lookup. -- 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
17
0 / 0

[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] (WELD-1070) WeldPhaseListener destroys conversation too soon

by Bernard Labno (JIRA)

Bernard Labno created WELD-1070: ----------------------------------- Summary: WeldPhaseListener destroys conversation too soon Key: WELD-1070 URL: https://issues.jboss.org/browse/WELD-1070 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.1.4.Final Environment: gentoo, java 1.6, AS7.1.0.Beta1, Seam 3.1.0.Final Reporter: Bernard Labno In JSF app when exception is thrown during RenderResponse phase then firstly there is a call to afterPhase and later to exception handlers. WeldPhaseListener.afterPhase is invoked before error handler (Seam Catch in my case). My error handler wants to promote conversation to long-running and do redirect to error page, but conversation context is not active anymore now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues February 2012