January 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDI-3) Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes

by Stuart Douglas (JIRA)

Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes ------------------------------------------------------------------------------------------------------------ Key: CDI-3 URL: https://jira.jboss.org/browse/CDI-3 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Stuart Douglas At the moment AnnotatedTypes can only be added in the BeforeBeanDiscovery phase. This means that if you want to install additional beans based on the beans processed in the ProcessAnnotatedType phase you must instead add implementations of the Bean interface in the AfterBeanDiscovery phase. This interface is more limited than annotated type, and does not let you exactly mimic the behaviour of beans added as AnnotatedTypes. Some of the things that the bean interface will not let you mimic are: - Interceptors - Disposal methods - Producer fields for normal scoped beans -- 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

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] Updated: (CDI-1) Clarify how resource producer fields (for persistence contexts) interact with transaction propagation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-1?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-1: ------------------------ Issue Type: Bug (was: Task) Component/s: Java EE integration > Clarify how resource producer fields (for persistence contexts) interact with transaction propagation > ----------------------------------------------------------------------------------------------------- > > Key: CDI-1 > URL: https://issues.jboss.org/browse/CDI-1 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (CDI-2) Interceptor bindings defined at method level should override those at the class level

by Pete Muir (JIRA)

Interceptor bindings defined at method level should override those at the class level ------------------------------------------------------------------------------------- Key: CDI-2 URL: https://jira.jboss.org/browse/CDI-2 Project: CDI Specification Issues Issue Type: Bug Components: Specification Reporter: Pete Muir We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec. In section 9.5.2 of the spec: If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error. -- 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

13 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Marius Bogoevici (JIRA)

Clarify the usage of EJB3 interceptors as managed beans ------------------------------------------------------- Key: CDI-82 URL: https://issues.jboss.org/browse/CDI-82 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Marius Bogoevici Fix For: 1.1 Background: http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-837) AbstractConversationContext.deactivate() throws ConcurrentModificationException

by Juergen Zimmermann (JIRA)

AbstractConversationContext.deactivate() throws ConcurrentModificationException ------------------------------------------------------------------------------- Key: WELD-837 URL: https://issues.jboss.org/browse/WELD-837 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.1.0.Final Reporter: Juergen Zimmermann I try to use a Conversation in JBossAS 6.0.1 Hudson build 2296 which contains Weld 1.1.0. However, I get the following stacktrace: 16:05:31,795 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/swe2].[FacesServlet]] Servlet.service() for servlet FacesServlet threw exception: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) [:1.6.0_23] at java.util.HashMap$EntryIterator.next(HashMap.java:834) [:1.6.0_23] at java.util.HashMap$EntryIterator.next(HashMap.java:832) [:1.6.0_23] at org.jboss.weld.context.AbstractConversationContext.deactivate(AbstractConversationContext.java:250) [:6.0.1-SNAPSHOT] at org.jboss.weld.jsf.WeldPhaseListener.deactivateConversations(WeldPhaseListener.java:131) [:6.0.1-SNAPSHOT] at org.jboss.weld.jsf.WeldPhaseListener.afterPhase(WeldPhaseListener.java:92) [:6.0.1-SNAPSHOT] at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:185) [:2.0.3-] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:103) [:2.0.3-] at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:135) [:2.0.3-] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:309) [:2.0.3-] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.1-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.1-SNAPSHOT] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [:] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.1-SNAPSHOT] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.1-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.1-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.1-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:] at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:893) [:] at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:600) [:] at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2019) [:] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (CDI-81) Allow a pseudo scoped bean to access the InjectionPoint in the create() and destroy() method

by Pete Muir (JIRA)

Allow a pseudo scoped bean to access the InjectionPoint in the create() and destroy() method -------------------------------------------------------------------------------------------- Key: CDI-81 URL: https://issues.jboss.org/browse/CDI-81 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-836) WELD should try to resolve injection points in webapp's .jars

by Krzysztof Maslak (JIRA)

WELD should try to resolve injection points in webapp's .jars ------------------------------------------------------------- Key: WELD-836 URL: https://issues.jboss.org/browse/WELD-836 Project: Weld Issue Type: Feature Request Reporter: Krzysztof Maslak Having following example scenario: webapp.war - /WEB-INF/lib/jar-with-some-nice-business-logic.jar - contains some injection points ( i.e. ICacheManager ) and using DefaultBean shipped with SeamSolder a default implementation ( as the injection points have to be satisfied ) - /WEB-INF/lib/caching-solution-provider.jar - provides CacheManagerImpl Having this simple example I would like to have this injection point satisfied by this caching-solution-provider.jar. With such solution I would be able to change my caching-solution-provider.jar without any code modification just by changing dependency in pom.xml for another cache provider which would be able to satisfy my contract. Then my development process would be similar to development in OSGi and blueprint as DI provider. I would care only about fulfilling the contracts by various artefacts. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
13
0 / 0

[JBoss JIRA] Updated: (WELD-833) ConcurrentModificationException while deactivating conversations

by Jan Groth (JIRA)

[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.s... ] Jan Groth updated WELD-833: --------------------------- Attachment: fix_deletion_of_conversations.patch > ConcurrentModificationException while deactivating conversations > ---------------------------------------------------------------- > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations > Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC > Reporter: Jan Groth > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map of conversations in org.jboss.weld.context.AbstractConversationContext is erroneous and easily runs into a ConcurrentModificationException if there is more than one conversation. We consider this a pretty serious defect because its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-825) Pastecode application fails to deploy on JBoss 6.0.0.Final

by Ondrej Skutka (JIRA)

Pastecode application fails to deploy on JBoss 6.0.0.Final ---------------------------------------------------------- Key: WELD-825 URL: https://issues.jboss.org/browse/WELD-825 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.1.0.Final Reporter: Ondrej Skutka Priority: Critical Using `mvn -Pftest-jboss-remote-6,jboss6 clean verify' I got an exception during deploy (server.log included) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (WELD-827) Weld SE examples are missing slf4j impl dependency

by Ondrej Skutka (JIRA)

Weld SE examples are missing slf4j impl dependency -------------------------------------------------- Key: WELD-827 URL: https://issues.jboss.org/browse/WELD-827 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.1.0.Final Reporter: Ondrej Skutka When running 'mvn -Drun' on SE examples, it fails not being able to find org.slf4j.impl.StaticMarkerBinder class. When added org.slf4j:slf4j-simple dependency to pom.xml, the examples work fine. [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java (run) on project weld-se-hello-world: An exception occured while executing the Java class. null: InvocationTargetException: org/slf4j/impl/StaticMarkerBinder: org.slf4j.impl.StaticMarkerBinder -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java (run) on project weld-se-hello-world: An exception occured while executing the Java class. null at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) 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: An exception occured while executing the Java class. null at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:338) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) ... 19 more Caused by: java.lang.reflect.InvocationTargetException 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.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NoClassDefFoundError: org/slf4j/impl/StaticMarkerBinder at org.slf4j.MarkerFactory.<clinit>(MarkerFactory.java:51) at org.slf4j.cal10n.LocLogger.<clinit>(LocLogger.java:48) at org.slf4j.cal10n.LocLoggerFactory.getLocLogger(LocLoggerFactory.java:59) at org.jboss.weld.logging.LoggerFactory.getLogger(LoggerFactory.java:47) at org.jboss.weld.bootstrap.WeldBootstrap.<clinit>(WeldBootstrap.java:124) 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.jboss.weld.environment.se.Weld.initialize(Weld.java:70) at org.jboss.weld.environment.se.StartMain.go(StartMain.java:45) at org.jboss.weld.environment.se.StartMain.main(StartMain.java:57) ... 6 more Caused by: java.lang.ClassNotFoundException: org.slf4j.impl.StaticMarkerBinder at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 20 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2011