[weld-issues] [JBoss JIRA] Resolved: (WELD-839) weld-servlet
[
https://issues.jboss.org/browse/WELD-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Douglas resolved WELD-839.
-
Assignee: Stuart Douglas
Fix Version/s: 1.2.0.Beta1
Resolution: Done
https://github.com/weld/core/pull/106
> weld-servlet
>
>
> Key: WELD-839
> URL: https://issues.jboss.org/browse/WELD-839
> Project: Weld
> Issue Type: Bug
> Components: Web Tier integration (JSF, JSP, EL and Servlet)
>Affects Versions: 1.1.0.Final
> Environment: Windows 7 64, GAE, java version "1.6.0_23" 64, JSF 2.0.3
>Reporter: Ara Minosian
>Assignee: Stuart Douglas
> Fix For: 1.2.0.Beta1
>
>
> Weld-servlet 1.0.1. works fine. I try to find common issue without success. I
> investigated examples but saw only JSF 1.2 support. I post to forum without
> any answer, so decided that problem exists.
> 25.01.2011 21:58:20 com.google.apphosting.utils.jetty.JettyLogger info
> INFO: Logging to JettyLogger(null) via
> com.google.apphosting.utils.jetty.JettyLogger
> 25.01.2011 21:58:20 com.google.apphosting.utils.config.AppEngineWebXmlReader
> readAppEngineWebXml
> INFO: Successfully processed
> G:\ideaworkspace\ideal\agost\target\agost-1.0\WEB-INF/appengine-web.xml
> 25.01.2011 21:58:20
> com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
> INFO: Successfully processed
> G:\ideaworkspace\ideal\agost\target\agost-1.0\WEB-INF/web.xml
> 25.01.2011 21:58:20 com.google.apphosting.utils.jetty.JettyLogger info
> INFO: jetty-6.1.x
> 25.01.2011 21:58:22 org.jboss.weld.bootstrap.WeldBootstrap
> INFO: WELD-000900 1.1.0 (Final)
> 25.01.2011 21:58:22 org.jboss.weld.environment.servlet.Listener
> contextInitialized
> WARNING: @Resource injection not available in simple beans
> 25.01.2011 21:58:22 org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject
> UserTransaction not available. Transactional observers will be invoked
> synchronously.
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: failed
> com.google.apphosting.utils.jetty.DevAppEngineWebAppContext@2d189c{/,G:\ideaworkspace\ideal\agost\target\agost-1.0}:
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: failed JettyContainerService$ApiProxyHandler@1bfa3d3:
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: Error starting handlers
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> at
> org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.getStandardContext(WeldForwardingAnnotationProcessor.java:92)
> at
> org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.replaceAnnotationProcessor(WeldForwardingAnnotationProcessor.java:69)
> at
> org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:192)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> com.google.appengine.tools.development.JettyContainerService.startContainer(JettyContainerService.java:185)
> at
> com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java:149)
> at
> com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:219)
> at
> com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:164)
> at
> com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:48)
> at
> com.google.appengine.tools.development.DevAppServerMain.(DevAppServerMain.java:113)
> at
> com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:89)
> Caused by: java.lang.ClassNotFoundException:
[weld-issues] [JBoss JIRA] Updated: (WELD-839) weld-servlet
[
https://issues.jboss.org/browse/WELD-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ales Justin updated WELD-839:
-
JBoss Forum Reference:
http://seamframework.org/Community/ArticleOnRunningWeldWithGoogleAppEngine#comment147710
> weld-servlet
>
>
> Key: WELD-839
> URL: https://issues.jboss.org/browse/WELD-839
> Project: Weld
> Issue Type: Bug
> Components: Web Tier integration (JSF, JSP, EL and Servlet)
>Affects Versions: 1.1.0.Final
> Environment: Windows 7 64, GAE, java version "1.6.0_23" 64, JSF 2.0.3
>Reporter: Ara Minosian
>
> Weld-servlet 1.0.1. works fine. I try to find common issue without success. I
> investigated examples but saw only JSF 1.2 support. I post to forum without
> any answer, so decided that problem exists.
> 25.01.2011 21:58:20 com.google.apphosting.utils.jetty.JettyLogger info
> INFO: Logging to JettyLogger(null) via
> com.google.apphosting.utils.jetty.JettyLogger
> 25.01.2011 21:58:20 com.google.apphosting.utils.config.AppEngineWebXmlReader
> readAppEngineWebXml
> INFO: Successfully processed
> G:\ideaworkspace\ideal\agost\target\agost-1.0\WEB-INF/appengine-web.xml
> 25.01.2011 21:58:20
> com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
> INFO: Successfully processed
> G:\ideaworkspace\ideal\agost\target\agost-1.0\WEB-INF/web.xml
> 25.01.2011 21:58:20 com.google.apphosting.utils.jetty.JettyLogger info
> INFO: jetty-6.1.x
> 25.01.2011 21:58:22 org.jboss.weld.bootstrap.WeldBootstrap
> INFO: WELD-000900 1.1.0 (Final)
> 25.01.2011 21:58:22 org.jboss.weld.environment.servlet.Listener
> contextInitialized
> WARNING: @Resource injection not available in simple beans
> 25.01.2011 21:58:22 org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject
> UserTransaction not available. Transactional observers will be invoked
> synchronously.
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: failed
> com.google.apphosting.utils.jetty.DevAppEngineWebAppContext@2d189c{/,G:\ideaworkspace\ideal\agost\target\agost-1.0}:
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: failed JettyContainerService$ApiProxyHandler@1bfa3d3:
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: Error starting handlers
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> at
> org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.getStandardContext(WeldForwardingAnnotationProcessor.java:92)
> at
> org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.replaceAnnotationProcessor(WeldForwardingAnnotationProcessor.java:69)
> at
> org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:192)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> com.google.appengine.tools.development.JettyContainerService.startContainer(JettyContainerService.java:185)
> at
> com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java:149)
> at
> com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:219)
> at
> com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:164)
> at
> com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:48)
> at
> com.google.appengine.tools.development.DevAppServerMain.(DevAppServerMain.java:113)
> at
> com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:89)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.catalina.core.ApplicationContextFacade
> at java.net.URLClassLoader$1.run(
[weld-issues] [JBoss JIRA] Commented: (WELD-839) weld-servlet
[
https://issues.jboss.org/browse/WELD-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578136#comment-12578136
]
Ales Justin commented on WELD-839:
--
This looks strange, as it looks like you're actually using Tomcat code.
Do you perhaps package org.apache.AnnotationProcessor class?
boolean tomcat = true;
boolean tomcat7;
try
{
Reflections.classForName("org.apache.AnnotationProcessor");
}
catch (IllegalArgumentException e)
{
tomcat = false;
}
if (tomcat)
{
try
{
WeldForwardingAnnotationProcessor.replaceAnnotationProcessor(sce,
manager); // < line 192
log.info("Tomcat 6 detected, CDI injection will be available in
Servlets and Filters. Injection into Listeners is not supported");
}
catch (Exception e)
{
log.error("Unable to replace Tomcat AnnotationProcessor. CDI
injection will not be available in Servlets, Filters, or Listeners", e);
}
}
> weld-servlet
>
>
> Key: WELD-839
> URL: https://issues.jboss.org/browse/WELD-839
> Project: Weld
> Issue Type: Bug
> Components: Web Tier integration (JSF, JSP, EL and Servlet)
>Affects Versions: 1.1.0.Final
> Environment: Windows 7 64, GAE, java version "1.6.0_23" 64, JSF 2.0.3
>Reporter: Ara Minosian
>
> Weld-servlet 1.0.1. works fine. I try to find common issue without success. I
> investigated examples but saw only JSF 1.2 support. I post to forum without
> any answer, so decided that problem exists.
> 25.01.2011 21:58:20 com.google.apphosting.utils.jetty.JettyLogger info
> INFO: Logging to JettyLogger(null) via
> com.google.apphosting.utils.jetty.JettyLogger
> 25.01.2011 21:58:20 com.google.apphosting.utils.config.AppEngineWebXmlReader
> readAppEngineWebXml
> INFO: Successfully processed
> G:\ideaworkspace\ideal\agost\target\agost-1.0\WEB-INF/appengine-web.xml
> 25.01.2011 21:58:20
> com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
> INFO: Successfully processed
> G:\ideaworkspace\ideal\agost\target\agost-1.0\WEB-INF/web.xml
> 25.01.2011 21:58:20 com.google.apphosting.utils.jetty.JettyLogger info
> INFO: jetty-6.1.x
> 25.01.2011 21:58:22 org.jboss.weld.bootstrap.WeldBootstrap
> INFO: WELD-000900 1.1.0 (Final)
> 25.01.2011 21:58:22 org.jboss.weld.environment.servlet.Listener
> contextInitialized
> WARNING: @Resource injection not available in simple beans
> 25.01.2011 21:58:22 org.jboss.weld.bootstrap.WeldBootstrap startContainer
> INFO: WELD-000101 Transactional services not available. Injection of @Inject
> UserTransaction not available. Transactional observers will be invoked
> synchronously.
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: failed
> com.google.apphosting.utils.jetty.DevAppEngineWebAppContext@2d189c{/,G:\ideaworkspace\ideal\agost\target\agost-1.0}:
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: failed JettyContainerService$ApiProxyHandler@1bfa3d3:
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> 25.01.2011 21:58:23 com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: Error starting handlers
> java.lang.NoClassDefFoundError:
> org/apache/catalina/core/ApplicationContextFacade
> at
> org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.getStandardContext(WeldForwardingAnnotationProcessor.java:92)
> at
> org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.replaceAnnotationProcessor(WeldForwardingAnnotationProcessor.java:69)
> at
> org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:192)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> com.google.appengine.tools.development.JettyContainerSer
[weld-issues] [JBoss JIRA] Assigned: (WELD-840) Weld 1.1 breaks compatibility with groovy objects
[ https://issues.jboss.org/browse/WELD-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin reassigned WELD-840: Assignee: Stuart Douglas > Weld 1.1 breaks compatibility with groovy objects > - > > Key: WELD-840 > URL: https://issues.jboss.org/browse/WELD-840 > Project: Weld > Issue Type: Bug > Components: Proxies >Affects Versions: 1.1.0.Final > Environment: Groovy 1.7.6, tomcat 6, weld 1.1, JSF 2 (mojarra 2.0.3) >Reporter: Jeff Howard >Assignee: Stuart Douglas > Labels: groovy > Attachments: weld11_partial_groovy_support.diff > > > Weld created proxies need to know how to work with groovy objects. > Currently, weld is attempting to proxy the methods from the > groovy.lang.GroovyObject interface which is confusing the groovy runtime. > Groovy objects have a per-class metaclass that is getting used with the wrong > class instances. > Also, weld is using hyphen characters in the generated proxy class names, > which breaks groovy's dynamic invoke mechanism. > The referenced forum thread contains a patch that addresses the groovy > incompatabilities in weld's ProxyFactory.java -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-96) Ability to override attributes of a Bean
[ https://issues.jboss.org/browse/CDI-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-96: - Affects Version/s: 1.0 > Ability to override attributes of a Bean > > > Key: CDI-96 > URL: https://issues.jboss.org/browse/CDI-96 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-91) Allow a producer to specialize a regular bean
[ https://issues.jboss.org/browse/CDI-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-91: - Affects Version/s: 1.0 > Allow a producer to specialize a regular bean > - > > Key: CDI-91 > URL: https://issues.jboss.org/browse/CDI-91 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Inheritance and Specialization >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-101) Use Module object, instead of Class for inter-module dependency resolution
[ https://issues.jboss.org/browse/CDI-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-101: -- Affects Version/s: 1.0 > Use Module object, instead of Class for inter-module dependency resolution > -- > > Key: CDI-101 > URL: https://issues.jboss.org/browse/CDI-101 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-90) Improve handling of Ambiguous Dependencies
[ https://issues.jboss.org/browse/CDI-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-90: - Affects Version/s: 1.0 > Improve handling of Ambiguous Dependencies > -- > > Key: CDI-90 > URL: https://issues.jboss.org/browse/CDI-90 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-95) Ability to obtain a container-created bean for a Producer or InjectionTarget or for an AnnotatedType
[ https://issues.jboss.org/browse/CDI-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-95: - Affects Version/s: 1.0 > Ability to obtain a container-created bean for a Producer or InjectionTarget > or for an AnnotatedType > > > Key: CDI-95 > URL: https://issues.jboss.org/browse/CDI-95 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-98) Ability to wrap the InjectionPoint
[ https://issues.jboss.org/browse/CDI-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-98: - Affects Version/s: 1.0 > Ability to wrap the InjectionPoint > -- > > Key: CDI-98 > URL: https://issues.jboss.org/browse/CDI-98 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-100) Allow injection of Instance into portable extensions
[ https://issues.jboss.org/browse/CDI-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-100: -- Affects Version/s: 1.0 > Allow injection of Instance into portable extensions > --- > > Key: CDI-100 > URL: https://issues.jboss.org/browse/CDI-100 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-97) Ability to process modules
[ https://issues.jboss.org/browse/CDI-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-97: - Affects Version/s: 1.0 > Ability to process modules > -- > > Key: CDI-97 > URL: https://issues.jboss.org/browse/CDI-97 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-94) Producer field initializers
[ https://issues.jboss.org/browse/CDI-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-94: - Affects Version/s: 1.0 > Producer field initializers > --- > > Key: CDI-94 > URL: https://issues.jboss.org/browse/CDI-94 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-99) Obtain Extension instances from BeanManager
[ https://issues.jboss.org/browse/CDI-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-99: - Affects Version/s: 1.0 > Obtain Extension instances from BeanManager > --- > > Key: CDI-99 > URL: https://issues.jboss.org/browse/CDI-99 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-92) Allow injection of Bean object for a bean
[ https://issues.jboss.org/browse/CDI-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-92: - Affects Version/s: 1.0 > Allow injection of Bean object for a bean > - > > Key: CDI-92 > URL: https://issues.jboss.org/browse/CDI-92 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-102) Support Injection of Servlet Contexts
[ https://issues.jboss.org/browse/CDI-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-102: -- Affects Version/s: 1.0 > Support Injection of Servlet Contexts > - > > Key: CDI-102 > URL: https://issues.jboss.org/browse/CDI-102 > Project: CDI Specification Issues > Issue Type: Feature Request >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-93) Support producers with a type variable bean type
[ https://issues.jboss.org/browse/CDI-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-93: - Affects Version/s: 1.0 > Support producers with a type variable bean type > > > Key: CDI-93 > URL: https://issues.jboss.org/browse/CDI-93 > Project: CDI Specification Issues > Issue Type: Feature Request >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-102) Support Injection of Servlet Contexts
Support Injection of Servlet Contexts - Key: CDI-102 URL: https://issues.jboss.org/browse/CDI-102 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-80) Support conversations in Servlet
[ https://issues.jboss.org/browse/CDI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-80: - JBoss Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-ConversationsForServlets > Support conversations in Servlet > > > Key: CDI-80 > URL: https://issues.jboss.org/browse/CDI-80 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts, Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-25) Support @Inject FacesContext facesContext;
[ https://issues.jboss.org/browse/CDI-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-25: - SourceForge Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-SupportInjectionOfTtFacesContexttt > Support @Inject FacesContext facesContext; > -- > > Key: CDI-25 > URL: https://issues.jboss.org/browse/CDI-25 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-53) Datasources defined on alternatives
[ https://issues.jboss.org/browse/CDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-53: - JBoss Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-TtDataSourceDefinitionttAndTtAlternativett > Datasources defined on alternatives > --- > > Key: CDI-53 > URL: https://issues.jboss.org/browse/CDI-53 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > > http://download.oracle.com/javaee/6/api/javax/annotation/sql/DataSourceDefinition.html > -- if this is used on an alternative class, only enable it if the > alternative is enabled. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-66) Clarify that EJB and web service references are truly @Dependent scoped (instance per injection)
[ https://issues.jboss.org/browse/CDI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-66: - JBoss Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-ClarifyLifecycleOfResources > Clarify that EJB and web service references are truly @Dependent scoped > (instance per injection) > > > Key: CDI-66 > URL: https://issues.jboss.org/browse/CDI-66 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-67) Clarify destruction of resources
[ https://issues.jboss.org/browse/CDI-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-67: - JBoss Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-ClarifyLifecycleOfResources > Clarify destruction of resources > > > Key: CDI-67 > URL: https://issues.jboss.org/browse/CDI-67 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > > Remove "When the destroy() method is called, the container discards this > internal reference and performs any cleanup required of state associated with > the client or transaction." -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-65) Clarify that stateful EJB references are not automatically destroyed by the container (the app must call the @Remove method explicitly)
[ https://issues.jboss.org/browse/CDI-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-65: - JBoss Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-ClarifyLifecycleOfResources > Clarify that stateful EJB references are not automatically destroyed by the > container (the app must call the @Remove method explicitly) > --- > > Key: CDI-65 > URL: https://issues.jboss.org/browse/CDI-65 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-64) Clarify that the instance of EntityManager associated with a resource declaration is the same instance that would be injected using @PersistenceContext
[ https://issues.jboss.org/browse/CDI-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-64: - JBoss Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-ClarifyLifecycleOfResources > Clarify that the instance of EntityManager associated with a resource > declaration is the same instance that would be injected using > @PersistenceContext > --- > > Key: CDI-64 > URL: https://issues.jboss.org/browse/CDI-64 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > > i.e. the JPA transaction-scoped container-managed persistence context > reference (Section 7.3.6) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-100) Allow injection of Instance into portable extensions
[ https://issues.jboss.org/browse/CDI-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-100: -- Component/s: Portable Extensions > Allow injection of Instance into portable extensions > --- > > Key: CDI-100 > URL: https://issues.jboss.org/browse/CDI-100 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-101) Use Module object, instead of Class for inter-module dependency resolution
Use Module object, instead of Class for inter-module dependency resolution -- Key: CDI-101 URL: https://issues.jboss.org/browse/CDI-101 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-99) Obtain Extension instances from BeanManager
[ https://issues.jboss.org/browse/CDI-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-99: - Component/s: Portable Extensions > Obtain Extension instances from BeanManager > --- > > Key: CDI-99 > URL: https://issues.jboss.org/browse/CDI-99 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-100) Allow injection of Instance into portable extensions
Allow injection of Instance into portable extensions --- Key: CDI-100 URL: https://issues.jboss.org/browse/CDI-100 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-58) Clarify that there can be multiple AnnotatedType instances per Java class
[ https://issues.jboss.org/browse/CDI-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-58: - JBoss Forum Reference: http://www.seamframework.org/Weld/PortableExtensionWishlist#H-ClarifyThatThereCanBeMultipleTtAnnotatedTypettInstancesPerJavaClass > Clarify that there can be multiple AnnotatedType instances per Java class > - > > Key: CDI-58 > URL: https://issues.jboss.org/browse/CDI-58 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans, Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-98) Ability to wrap the InjectionPoint
Ability to wrap the InjectionPoint -- Key: CDI-98 URL: https://issues.jboss.org/browse/CDI-98 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-99) Obtain Extension instances from BeanManager
Obtain Extension instances from BeanManager --- Key: CDI-99 URL: https://issues.jboss.org/browse/CDI-99 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-97) Ability to process modules
Ability to process modules -- Key: CDI-97 URL: https://issues.jboss.org/browse/CDI-97 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-96) Ability to override attributes of a Bean
Ability to override attributes of a Bean Key: CDI-96 URL: https://issues.jboss.org/browse/CDI-96 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-97) Ability to process modules
[ https://issues.jboss.org/browse/CDI-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-97: - Component/s: Portable Extensions > Ability to process modules > -- > > Key: CDI-97 > URL: https://issues.jboss.org/browse/CDI-97 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-95) Ability to obtain a container-created bean for a Producer or InjectionTarget or for an AnnotatedType
[ https://issues.jboss.org/browse/CDI-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-95: - Component/s: Portable Extensions > Ability to obtain a container-created bean for a Producer or InjectionTarget > or for an AnnotatedType > > > Key: CDI-95 > URL: https://issues.jboss.org/browse/CDI-95 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-94) Producer field initializers
Producer field initializers --- Key: CDI-94 URL: https://issues.jboss.org/browse/CDI-94 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-28) Abstract methods on decorators
[ https://issues.jboss.org/browse/CDI-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-28: - SourceForge Reference: http://www.seamframework.org/Weld/InterceptorsDecoratorsWishlist#H-MethodsOfAbstractDecorators > Abstract methods on decorators > -- > > Key: CDI-28 > URL: https://issues.jboss.org/browse/CDI-28 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators >Affects Versions: 1.0 >Reporter: Pete Muir > > If a method is abstract: > * if it is a method of a decorated type, it has a generated implementation > that calls the delegate > * otherwise, definition error -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-95) Ability to obtain a container-created bean for a Producer or InjectionTarget or for an AnnotatedType
Ability to obtain a container-created bean for a Producer or InjectionTarget or for an AnnotatedType Key: CDI-95 URL: https://issues.jboss.org/browse/CDI-95 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-93) Support producers with a type variable bean type
Support producers with a type variable bean type Key: CDI-93 URL: https://issues.jboss.org/browse/CDI-93 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-92) Allow injection of Bean object for a bean
Allow injection of Bean object for a bean - Key: CDI-92 URL: https://issues.jboss.org/browse/CDI-92 Project: CDI Specification Issues Issue Type: Feature Request Components: Beans Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-91) Allow a producer to specialize a regular bean
Allow a producer to specialize a regular bean - Key: CDI-91 URL: https://issues.jboss.org/browse/CDI-91 Project: CDI Specification Issues Issue Type: Feature Request Components: Inheritance and Specialization Reporter: Pete Muir -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-54) Abstract Producer methods
[ https://issues.jboss.org/browse/CDI-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-54: - JBoss Forum Reference: http://www.seamframework.org/Weld/DependencyInjectionWishlist#H-AbstractProducerMethods > Abstract Producer methods > - > > Key: CDI-54 > URL: https://issues.jboss.org/browse/CDI-54 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-90) Improve handling of Ambiguous Dependencies
[ https://issues.jboss.org/browse/CDI-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-90: - Component/s: Resolution > Improve handling of Ambiguous Dependencies > -- > > Key: CDI-90 > URL: https://issues.jboss.org/browse/CDI-90 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-90) Improve handling of Ambiguous Dependencies
Improve handling of Ambiguous Dependencies -- Key: CDI-90 URL: https://issues.jboss.org/browse/CDI-90 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 ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-51) Support static injection
[ https://issues.jboss.org/browse/CDI-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-51: - JBoss Forum Reference: http://www.seamframework.org/Weld/DependencyInjectionWishlist#H-StaticInjection > Support static injection > > > Key: CDI-51 > URL: https://issues.jboss.org/browse/CDI-51 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (WELD-840) Weld 1.1 breaks compatibility with groovy objects
[ https://issues.jboss.org/browse/WELD-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Howard updated WELD-840: - Attachment: weld11_partial_groovy_support.diff Patch to fix the ProxyFactory.java file > Weld 1.1 breaks compatibility with groovy objects > - > > Key: WELD-840 > URL: https://issues.jboss.org/browse/WELD-840 > Project: Weld > Issue Type: Bug > Components: Proxies >Affects Versions: 1.1.0.Final > Environment: Groovy 1.7.6, tomcat 6, weld 1.1, JSF 2 (mojarra 2.0.3) >Reporter: Jeff Howard > Labels: groovy > Attachments: weld11_partial_groovy_support.diff > > > Weld created proxies need to know how to work with groovy objects. > Currently, weld is attempting to proxy the methods from the > groovy.lang.GroovyObject interface which is confusing the groovy runtime. > Groovy objects have a per-class metaclass that is getting used with the wrong > class instances. > Also, weld is using hyphen characters in the generated proxy class names, > which breaks groovy's dynamic invoke mechanism. > The referenced forum thread contains a patch that addresses the groovy > incompatabilities in weld's ProxyFactory.java -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (WELD-840) Weld 1.1 breaks compatibility with groovy objects
Weld 1.1 breaks compatibility with groovy objects - Key: WELD-840 URL: https://issues.jboss.org/browse/WELD-840 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.Final Environment: Groovy 1.7.6, tomcat 6, weld 1.1, JSF 2 (mojarra 2.0.3) Reporter: Jeff Howard Weld created proxies need to know how to work with groovy objects. Currently, weld is attempting to proxy the methods from the groovy.lang.GroovyObject interface which is confusing the groovy runtime. Groovy objects have a per-class metaclass that is getting used with the wrong class instances. Also, weld is using hyphen characters in the generated proxy class names, which breaks groovy's dynamic invoke mechanism. The referenced forum thread contains a patch that addresses the groovy incompatabilities in weld's ProxyFactory.java -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Created: (CDI-89) Add @Unwraps from Seam Solder
Add @Unwraps from Seam Solder -- Key: CDI-89 URL: https://issues.jboss.org/browse/CDI-89 Project: CDI Specification Issues Issue Type: Feature Request Components: Concepts Affects Versions: 1.0 Reporter: Stuart Douglas @Unwraps allows for an essentially stateless scope for producer methods and fields. At injection time a dependent scoped proxy is injected into the injection point. When a methods is invoked on this proxy it calls the corresponding @Unwraps methods to get the instance to invoke the method on. Because the proxy is @Dependent scoped, the @Unwraps method can inject the corresponding InjectionPoint. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-18) cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives
[ https://issues.jboss.org/browse/CDI-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-18: - Component/s: Beans Decorators Interceptors Packaging and Deployment > cleanup Bean Archive behaviour (BDA) of interceptors, decorators and > alternatives > - > > Key: CDI-18 > URL: https://issues.jboss.org/browse/CDI-18 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans, Decorators, Interceptors, Packaging and Deployment >Affects Versions: 1.0 >Reporter: Mark Struberg >Priority: Critical > Fix For: 1.1 > > > Currently the spec defines that , and > affect only the Bean Archives where they are configured in > (via beans.xml). > Thus if you e.g. enable an Alternative in a WEB-INF/beans.xml, it does NOT > count for the jars in it's WEB-INF/lib folder! > This is pretty unhandy because you would need to repackage all your jars in > your WEB-INF/lib folder and add/expand the sections in their > beans.xml. > Needless to say that this is not only hard to do in a company build but is > also impossibly to handle at deploy time in an OSGi environment! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-88) Fix ProcessObserverMethod javadoc to match spec
[ https://issues.jboss.org/browse/CDI-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-88: - Component/s: Javadoc and API Portable Extensions > Fix ProcessObserverMethod javadoc to match spec > --- > > Key: CDI-88 > URL: https://issues.jboss.org/browse/CDI-88 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API, Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-87) Declarative control over classes including in bean archive scanning
[ https://issues.jboss.org/browse/CDI-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-87: - Component/s: Packaging and Deployment > Declarative control over classes including in bean archive scanning > --- > > Key: CDI-87 > URL: https://issues.jboss.org/browse/CDI-87 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Packaging and Deployment >Affects Versions: 1.0 >Reporter: Pete Muir > > Weld introduced a XML syntax for this -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-10) Add ability to access a bean instance from a proxy
[ https://issues.jboss.org/browse/CDI-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-10: - Component/s: Beans > Add ability to access a bean instance from a proxy > -- > > Key: CDI-10 > URL: https://issues.jboss.org/browse/CDI-10 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans >Affects Versions: 1.0 >Reporter: Stuart Douglas > > There are occasions when it would be useful to access a bean instance > directly from a proxy. This could be achieved by making all proxies > assignable to an interface (say BeanProxy) that provides a getBeanInstance() > method. > Client code that needs access to the actual instance can check if the object > is assignable to the BeanProxy interface and then call getBeanInstance() to > get the actual instance if required. > This is something that is probably more useful to extension writers than the > end user, but there have already been a few requests on the weld forum about > this so it is probably worth considering. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-84) Non EE modules should be able to trigger creation of a BeanManager
[ https://issues.jboss.org/browse/CDI-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-84: - Component/s: Java EE integration Packaging and Deployment Aslak could you expand on this, I don't quite follow. > Non EE modules should be able to trigger creation of a BeanManager > -- > > Key: CDI-84 > URL: https://issues.jboss.org/browse/CDI-84 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration, Packaging and Deployment >Affects Versions: 1.0 >Reporter: Aslak Knutsen > > EE.5.19 > A bean manager is only available in modules in which CDI has been enabled. > Where EE modules are defined to be; ejb-jar, rar, client jar and war. > This is a missmatch between the EE spec and the CDI spec. According to the > CDI spec, any archive with a beans.xml is defined as a BeanArchive and should > be included in a BeanManager, EE define it to be only EE modules should > trigger BeanManager creation. > Opening this up to follow the CDI spec will let any library use the > BeanManager to introspect other BeanArchives without having to involve the > owning EE module in the loop. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-85) Clarify use of "to" and "from" when refering to assignments in section 5.2.3
[ https://issues.jboss.org/browse/CDI-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-85: - Component/s: Resolution > Clarify use of "to" and "from" when refering to assignments in section 5.2.3 > > > Key: CDI-85 > URL: https://issues.jboss.org/browse/CDI-85 > Project: CDI Specification Issues > Issue Type: Bug > Components: Resolution >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-86) Support firing general purpose lifecycle events in Java EE environments
[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-86: - Component/s: Java EE integration > Support firing general purpose lifecycle events in Java EE environments > --- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-83) Clarify that BeanManager.createAnnotatedType() should return any modifications made by lifecycle events.
[ https://issues.jboss.org/browse/CDI-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-83: - Component/s: Portable Extensions > Clarify that BeanManager.createAnnotatedType() should return any > modifications made by lifecycle events. > > > Key: CDI-83 > URL: https://issues.jboss.org/browse/CDI-83 > Project: CDI Specification Issues > Issue Type: Bug > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-80) Support conversations in Servlet
[ https://issues.jboss.org/browse/CDI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-80: - Component/s: Contexts > Support conversations in Servlet > > > Key: CDI-80 > URL: https://issues.jboss.org/browse/CDI-80 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts, Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-78) Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator
[ https://issues.jboss.org/browse/CDI-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-78: - Component/s: Decorators > Clarify how isDelegate() behaves on InjectionPoint, and what happens when an > InjectionPoint is injected into a Decorator > > > Key: CDI-78 > URL: https://issues.jboss.org/browse/CDI-78 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators >Affects Versions: 1.0 >Reporter: Pete Muir > > The InjectionPoint should be that of the injection into the consumer, and > isDelegate() should return false. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-79) Allow you to inspect the decorator chain
[ https://issues.jboss.org/browse/CDI-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-79: - Component/s: Decorators > Allow you to inspect the decorator chain > > > Key: CDI-79 > URL: https://issues.jboss.org/browse/CDI-79 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans
[
https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Muir updated CDI-77:
-
Summary: Clarify what happens when the user creates a unbound recursive
injection with Dependent scoped beans (was: Clarify what happens when the user
creates a unbound recursive injection with Dependent scoped beans@)
Component/s: Resolution
> Clarify what happens when the user creates a unbound recursive injection with
> Dependent scoped beans
>
>
> Key: CDI-77
> URL: https://issues.jboss.org/browse/CDI-77
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Resolution
>Affects Versions: 1.0
>Reporter: Pete Muir
>
> for example
> class Foo {
> @Inject Bar bar;
> }
> class bar {
> @Inject Foo foo;
> }
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-80) Support conversations in Servlet
[ https://issues.jboss.org/browse/CDI-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-80: - Component/s: Java EE integration > Support conversations in Servlet > > > Key: CDI-80 > URL: https://issues.jboss.org/browse/CDI-80 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-75) Clarify what happens to a bean which belongs to inactive when it observes an event
[ https://issues.jboss.org/browse/CDI-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-75: - Component/s: Events > Clarify what happens to a bean which belongs to inactive when it observes an > event > -- > > Key: CDI-75 > URL: https://issues.jboss.org/browse/CDI-75 > Project: CDI Specification Issues > Issue Type: Bug > Components: Events >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-76) JavaDocs regarding adding scopes are weak
[
https://issues.jboss.org/browse/CDI-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Muir updated CDI-76:
-
Component/s: Portable Extensions
> JavaDocs regarding adding scopes are weak
> -
>
> Key: CDI-76
> URL: https://issues.jboss.org/browse/CDI-76
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Javadoc and API, Portable Extensions
>Affects Versions: 1.0
>Reporter: Lincoln Baxter III
>
> JavaDocs for adding scopes via the eventing API are a bit weak.
>public void addScope(@Observes final BeforeBeanDiscovery event)
>{
> event.addScope(ProjectScoped.class, true, false);
>}
> Currently it is not clear that using this method is only required when not
> using the @NormalScoped annotation, and that it will in fact override the
> annotation if present. Additional docs should probably be placed on both
> sides of this relationship, to that affect.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-74) State explicitely that Decorators and Interceptors of must be implemented via subclassing
[ https://issues.jboss.org/browse/CDI-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-74: - Component/s: Decorators Interceptors > State explicitely that Decorators and Interceptors of must be implemented via > subclassing > - > > Key: CDI-74 > URL: https://issues.jboss.org/browse/CDI-74 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators, Interceptors >Affects Versions: 1.0 >Reporter: Marius Bogoevici > Fix For: 1.1 > > > Subclassing should be mandatory for Decorators and Interceptors of managed > beans which are not session beans (no restrictions in the case of the latter). > This ensures that: > - fields on pseudo scoped managed beans are accessible > - there's no restriction on what kinds of constructors may a managed bean > have > - no extra bean instances are created when a managed bean is created -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-72) Clarify what InjectionPoint should return when the injection point is Instance<>
[ https://issues.jboss.org/browse/CDI-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-72: - Component/s: Resolution > Clarify what InjectionPoint should return when the injection point is > Instance<> > > > Key: CDI-72 > URL: https://issues.jboss.org/browse/CDI-72 > Project: CDI Specification Issues > Issue Type: Bug > Components: Resolution >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-71) Make it possible to obtain the qualifiers used when the currently observed event was fired
[ https://issues.jboss.org/browse/CDI-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-71: - Component/s: Events > Make it possible to obtain the qualifiers used when the currently observed > event was fired > -- > > Key: CDI-71 > URL: https://issues.jboss.org/browse/CDI-71 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-73) Specify that the BM should be available from the Servlet context for ease of access
[ https://issues.jboss.org/browse/CDI-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-73: - Component/s: Java EE integration > Specify that the BM should be available from the Servlet context for ease of > access > --- > > Key: CDI-73 > URL: https://issues.jboss.org/browse/CDI-73 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-68) Clarify that there is only one instance of a Context object per application deployment for built in contexts
[ https://issues.jboss.org/browse/CDI-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-68: - Component/s: Contexts > Clarify that there is only one instance of a Context object per application > deployment for built in contexts > > > Key: CDI-68 > URL: https://issues.jboss.org/browse/CDI-68 > Project: CDI Specification Issues > Issue Type: Bug > Components: Contexts >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-70) Clarify that if an extension provides an Annotated* then it is considered "metadata complete"
[ https://issues.jboss.org/browse/CDI-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-70: - Component/s: Portable Extensions > Clarify that if an extension provides an Annotated* then it is considered > "metadata complete" > - > > Key: CDI-70 > URL: https://issues.jboss.org/browse/CDI-70 > Project: CDI Specification Issues > Issue Type: Bug > Components: Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > > I think the correct behavior is to ignore any members that are missing from > the AnnotatedType. You should not be directly accessing the reflection API at > all. If the parameters for a method or a constructor don't match the > underlying class, it should be considered a definition error. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-67) Clarify destruction of resources
[ https://issues.jboss.org/browse/CDI-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-67: - Component/s: Java EE integration > Clarify destruction of resources > > > Key: CDI-67 > URL: https://issues.jboss.org/browse/CDI-67 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > > Remove "When the destroy() method is called, the container discards this > internal reference and performs any cleanup required of state associated with > the client or transaction." -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-69) Clarify that POST_ACTIVATE and PRE_PASSIVATE on InterceptorType are only for EJBs
[ https://issues.jboss.org/browse/CDI-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-69: - Component/s: Java EE integration > Clarify that POST_ACTIVATE and PRE_PASSIVATE on InterceptorType are only for > EJBs > - > > Key: CDI-69 > URL: https://issues.jboss.org/browse/CDI-69 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-66) Clarify that EJB and web service references are truly @Dependent scoped (instance per injection)
[ https://issues.jboss.org/browse/CDI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-66: - Component/s: Java EE integration > Clarify that EJB and web service references are truly @Dependent scoped > (instance per injection) > > > Key: CDI-66 > URL: https://issues.jboss.org/browse/CDI-66 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-65) Clarify that stateful EJB references are not automatically destroyed by the container (the app must call the @Remove method explicitly)
[ https://issues.jboss.org/browse/CDI-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-65: - Component/s: Java EE integration > Clarify that stateful EJB references are not automatically destroyed by the > container (the app must call the @Remove method explicitly) > --- > > Key: CDI-65 > URL: https://issues.jboss.org/browse/CDI-65 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-64) Clarify that the instance of EntityManager associated with a resource declaration is the same instance that would be injected using @PersistenceContext
[ https://issues.jboss.org/browse/CDI-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-64: - Component/s: Java EE integration > Clarify that the instance of EntityManager associated with a resource > declaration is the same instance that would be injected using > @PersistenceContext > --- > > Key: CDI-64 > URL: https://issues.jboss.org/browse/CDI-64 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > > i.e. the JPA transaction-scoped container-managed persistence context > reference (Section 7.3.6) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-63) Add section on cyclic dependencies to the spec
[ https://issues.jboss.org/browse/CDI-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-63: - Component/s: Beans Resolution > Add section on cyclic dependencies to the spec > -- > > Key: CDI-63 > URL: https://issues.jboss.org/browse/CDI-63 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans, Resolution >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-62) Clarify @Resource/@PersistenceContext/etc. on disabled alternatives
[ https://issues.jboss.org/browse/CDI-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-62: - Component/s: Java EE integration > Clarify @Resource/@PersistenceContext/etc. on disabled alternatives > --- > > Key: CDI-62 > URL: https://issues.jboss.org/browse/CDI-62 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > > Is it expected that the container validates these dependencies and fails > deployment if they don't exist? I think it is, right? At least, I think some > containers behave this way. Then we should say that this validation should > *not* happen if the annotation appears in a class annotated @Alternative. I > have no idea what the right language would be... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-60) In lifecycle chapter, clarify creation of interceptors/decorator
[ https://issues.jboss.org/browse/CDI-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-60: - Component/s: Decorators Interceptors > In lifecycle chapter, clarify creation of interceptors/decorator > > > Key: CDI-60 > URL: https://issues.jboss.org/browse/CDI-60 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators, Interceptors >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-61) Producers and beans that are under construction
[ https://issues.jboss.org/browse/CDI-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-61: - Component/s: Beans > Producers and beans that are under construction > --- > > Key: CDI-61 > URL: https://issues.jboss.org/browse/CDI-61 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans >Affects Versions: 1.0 >Reporter: Pete Muir > > I think we need the spec to say something about cases where an injection > point of a bean resolves to a producer method of the same bean. The > implementation should detect that this is a definition error. It shouldn't > try to call a producer method on a non-fully-initialized bean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-59) Clarify that interceptors/decorators don't apply to producers in resolution rules
[ https://issues.jboss.org/browse/CDI-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-59: - Component/s: Beans Decorators Interceptors Resolution > Clarify that interceptors/decorators don't apply to producers in resolution > rules > - > > Key: CDI-59 > URL: https://issues.jboss.org/browse/CDI-59 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans, Decorators, Interceptors, Resolution >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-57) Clarify that not all classes in a bean archive are bean classes
[ https://issues.jboss.org/browse/CDI-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-57: - Component/s: Beans Packaging and Deployment > Clarify that not all classes in a bean archive are bean classes > --- > > Key: CDI-57 > URL: https://issues.jboss.org/browse/CDI-57 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans, Packaging and Deployment >Affects Versions: 1.0 >Reporter: Pete Muir > > We should be clearer and say that you can put non-bean classes (e.g.MDBs) in > a bean archive. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-58) Clarify that there can be multiple AnnotatedType instances per Java class
[ https://issues.jboss.org/browse/CDI-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-58: - Component/s: Beans Portable Extensions > Clarify that there can be multiple AnnotatedType instances per Java class > - > > Key: CDI-58 > URL: https://issues.jboss.org/browse/CDI-58 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans, Portable Extensions >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-56) Clarify that scope types should not have members
[ https://issues.jboss.org/browse/CDI-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-56: - Component/s: Concepts > Clarify that scope types should not have members > > > Key: CDI-56 > URL: https://issues.jboss.org/browse/CDI-56 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts >Affects Versions: 1.0 >Reporter: Pete Muir > > The spec should mention that @NormalScope annotations should not have > annotation members. Perhaps this should be a definition error. > javax.inject.Scope already mentions this. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-55) Bean declaration at constructor level
[ https://issues.jboss.org/browse/CDI-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-55: - Component/s: Beans > Bean declaration at constructor level > - > > Key: CDI-55 > URL: https://issues.jboss.org/browse/CDI-55 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-835) Make sure all examples have instructions for importing and deploying via JBoss Tools.
[ https://issues.jboss.org/browse/WELD-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578088#comment-12578088 ] Max Rydahl Andersen commented on WELD-835: -- no, we don't enable any profile anywhere - just using default m2eclipse import. And what you are using is web overlays which m2eclipse/wtp integration does not support yet - i've worked with fbricon on getting it added in; but for now this will probably cause problems for the deployment part in any case - thus if the above works and makes webapp the WTP webcontent then things in the VPE will at least work and to do working deployment you would need to use maven anyway. Would be good if we could reduce the usage of weboverlays in examples to a minimum until this can be proper handled. > Make sure all examples have instructions for importing and deploying via > JBoss Tools. > - > > Key: WELD-835 > URL: https://issues.jboss.org/browse/WELD-835 > Project: Weld > Issue Type: Task >Reporter: Pete Muir >Priority: Critical > Fix For: 1.2.0.Beta1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-835) Make sure all examples have instructions for importing and deploying via JBoss Tools.
[ https://issues.jboss.org/browse/WELD-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578087#comment-12578087 ] Max Rydahl Andersen commented on WELD-835: -- no, we don't enable any profile anywhere - just using default m2eclipse import. And what you are using is web overlays which m2eclipse/wtp integration does not support yet - i've worked with fbricon on getting it added in; but for now this will probably cause problems for the deployment part in any case - thus if the above works and makes webapp the WTP webcontent then things in the VPE will at least work and to do working deployment you would need to use maven anyway. Would be good if we could reduce the usage of weboverlays in examples to a minimum until this can be proper handled. > Make sure all examples have instructions for importing and deploying via > JBoss Tools. > - > > Key: WELD-835 > URL: https://issues.jboss.org/browse/WELD-835 > Project: Weld > Issue Type: Task >Reporter: Pete Muir >Priority: Critical > Fix For: 1.2.0.Beta1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-835) Make sure all examples have instructions for importing and deploying via JBoss Tools.
[ https://issues.jboss.org/browse/WELD-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578086#comment-12578086 ] Dan Allen commented on WELD-835: To make sure we're on the same page, I'm assuming that you have the tomcat profile enabled in the Maven settings panel. Otherwise, JBoss Tools shouldn't be seeing this configuration since it's inside of a profile. Is my assumption correct that we are talking about when the tomcat profile is enabled? You are correct that the webapp-tomcat folder is being explicitly defined as the web directory in the configuration. This happens to work in the Maven build because of a quirk (I suppose) in the war plugin, which assumes the resources listed are additive. Meaning, src/main/webapp is assumed to be a web resource always. That's obviously not a good assumption. As it turns out, it's possible to still list src/main/webapp in the Maven configuration. Thus, the configuration in the pom.xml should be: org.apache.maven.plugins maven-war-plugin src/main/webapp-tomcat false src/main/webapp-tomcat false Note that it's not one or the other. Both directories are needed for the example to work on Tomcat. This is how we are able to configure the build to target different containers, including AS, Tomcat and Jetty. > Make sure all examples have instructions for importing and deploying via > JBoss Tools. > - > > Key: WELD-835 > URL: https://issues.jboss.org/browse/WELD-835 > Project: Weld > Issue Type: Task >Reporter: Pete Muir >Priority: Critical > Fix For: 1.2.0.Beta1 > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-780) Place beans.xml under WEB-INF instead of WEB-INF/classes/META-INF in jsf/permalink example
[ https://issues.jboss.org/browse/WELD-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578082#comment-12578082 ] Dan Allen commented on WELD-780: Proposed fix: https://github.com/weld/core/pull/105 Please test by following the deployment instructions in readme.txt. > Place beans.xml under WEB-INF instead of WEB-INF/classes/META-INF in > jsf/permalink example > -- > > Key: WELD-780 > URL: https://issues.jboss.org/browse/WELD-780 > Project: Weld > Issue Type: Task > Components: Examples >Affects Versions: 1.1.0.Beta2 >Reporter: Sivakumar Thyagarajan >Priority: Minor > Labels: examples > Fix For: 1.2.0.Beta1 > > > As per Section 12.1 of CDI 1.0 specification: > > • The WEB-INF/classes directory of a war is a bean archive if there is a > > file named beans.xml in the WEB-INF directory of the war. > > • A directory in the JVM classpath is a bean archive if it has a file named > > beans.xml in the META-INF directory. > However the jsf/permalink sample bundles beans.xml under > WEB-INF/classes/META-INF. This may not work in other containers (for instance > see http://java.net/jira/browse/GLASSFISH-15009 ). So request to move the > file (in weld-core): from > examples/jsf/permalink/src/main/resources/META-INF/beans.xml > to > examples/jsf/permalink/src/main/webapp/WEB-INF/beans.xml -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-49) The availability of the BeanManager should follow the normal EE visibility rules
[ https://issues.jboss.org/browse/CDI-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-49: - Component/s: Packaging and Deployment Resolution > The availability of the BeanManager should follow the normal EE visibility > rules > > > Key: CDI-49 > URL: https://issues.jboss.org/browse/CDI-49 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration, Packaging and Deployment, Resolution >Affects Versions: 1.0 > Environment: JSR-000316 Java Platform, Enterprise Edition 6 > Specification >Reporter: Aslak Knutsen > > EE 6 spec > EE.5.19 > A bean manager is only available in modules in which CDI has been enabled. > In e.g. a EAR deployment, a WAR module can see a EJB module. With CDI enabled > in the EJB, the WAR can only see the BeanManager if the WAR itself is also > CDI enabled. In cases where you want to do dynamic introspection of available > beans etc, this is a bit cumbersome, especially since the introspecting code > can be in a packaged jar inside a unknown WAR.. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-49) The availability of the BeanManager should follow the normal EE visibility rules
[ https://issues.jboss.org/browse/CDI-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-49: - Component/s: Java EE integration > The availability of the BeanManager should follow the normal EE visibility > rules > > > Key: CDI-49 > URL: https://issues.jboss.org/browse/CDI-49 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration, Packaging and Deployment, Resolution >Affects Versions: 1.0 > Environment: JSR-000316 Java Platform, Enterprise Edition 6 > Specification >Reporter: Aslak Knutsen > > EE 6 spec > EE.5.19 > A bean manager is only available in modules in which CDI has been enabled. > In e.g. a EAR deployment, a WAR module can see a EJB module. With CDI enabled > in the EJB, the WAR can only see the BeanManager if the WAR itself is also > CDI enabled. In cases where you want to do dynamic introspection of available > beans etc, this is a bit cumbersome, especially since the introspecting code > can be in a packaged jar inside a unknown WAR.. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-50) Add annotation version of veto()
[ https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-50: - Component/s: Concepts Packaging and Deployment > Add annotation version of veto() > > > Key: CDI-50 > URL: https://issues.jboss.org/browse/CDI-50 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts, Packaging and Deployment >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-54) Abstract Producer methods
[ https://issues.jboss.org/browse/CDI-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-54: - Component/s: Beans > Abstract Producer methods > - > > Key: CDI-54 > URL: https://issues.jboss.org/browse/CDI-54 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-51) Support static injection
[ https://issues.jboss.org/browse/CDI-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-51: - Component/s: Concepts > Support static injection > > > Key: CDI-51 > URL: https://issues.jboss.org/browse/CDI-51 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-53) Datasources defined on alternatives
[ https://issues.jboss.org/browse/CDI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-53: - Component/s: Java EE integration > Datasources defined on alternatives > --- > > Key: CDI-53 > URL: https://issues.jboss.org/browse/CDI-53 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration >Affects Versions: 1.0 >Reporter: Pete Muir > > http://download.oracle.com/javaee/6/api/javax/annotation/sql/DataSourceDefinition.html > -- if this is used on an alternative class, only enable it if the > alternative is enabled. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean
[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-52: - Component/s: Beans > Make it clearer that an InjectionPoint injected into a disposer method refers > to the producer method bean and not to the declaring bean > --- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans >Affects Versions: 1.0 >Reporter: Pete Muir > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-45) Optional Injection Points
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-45: - Component/s: Resolution > Optional Injection Points > - > > Key: CDI-45 > URL: https://issues.jboss.org/browse/CDI-45 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution >Affects Versions: 1.0 >Reporter: Stuart Douglas > > There are occoasions where it may be useful for some injection points to be > optional, e.g. > @Inject > @Optional > MyBean bean; > This would behave the same as a normal injection point, however it will not > cause the deployment to fail if it is not satisified. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-48) Global Interceptor/Decorator ordering
[ https://issues.jboss.org/browse/CDI-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-48: - Component/s: Decorators Interceptors Packaging and Deployment > Global Interceptor/Decorator ordering > - > > Key: CDI-48 > URL: https://issues.jboss.org/browse/CDI-48 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators, Interceptors, Packaging and Deployment >Affects Versions: 1.0 >Reporter: Stuart Douglas > > Currently interceptor/decorator ordering is specified on a per bean archive > level. In the majority of cases the correct ordering is the same for every > BDA in the application, so this violates DRY and opens the door to nasty bugs > due to different ordering per module if beans.xml files get out of sync. > We should look at allowing the user to define interceptor and decorator > ordering once per app and have this applied to all modules in the deployment. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-47) Add required attribute to tag in beans.xml
[ https://issues.jboss.org/browse/CDI-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-47: - Component/s: Interceptors Packaging and Deployment > Add required attribute to tag in beans.xml > - > > Key: CDI-47 > URL: https://issues.jboss.org/browse/CDI-47 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Interceptors, Packaging and Deployment >Affects Versions: 1.0 >Reporter: Stuart Douglas > > Currently the deployment will fail if an interceptor is not present, which > means that it is not conventient to use interceptors from optional modules, > as the end user will need to open up the jar file and edit the beans.xml file > manually. > Adding a required="true|false" attribute to the element in > beans.xml would allow an archive to specify that the interceptor is not > essential, and if it is not found it should simply be ignored. > For example, currently Seam Security has a hard dependency on Seam > Persistence because it uses the Transaction interceptor, and the deployment > will fail if Seam Persistence is not present. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-46) Clarify in the specification that extensions do not require a beans.xml file
[ https://issues.jboss.org/browse/CDI-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-46: - Component/s: Packaging and Deployment > Clarify in the specification that extensions do not require a beans.xml file > > > Key: CDI-46 > URL: https://issues.jboss.org/browse/CDI-46 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Packaging and Deployment >Affects Versions: 1.0 >Reporter: Shane Bryzak > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Updated: (CDI-44) Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation
[ https://issues.jboss.org/browse/CDI-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Muir updated CDI-44: - Component/s: Interceptors > Clarify that interceptors must be implemented using subclassing, and clarify > the behaviour of self-invocation > - > > Key: CDI-44 > URL: https://issues.jboss.org/browse/CDI-44 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Interceptors >Affects Versions: 1.0 >Reporter: Stuart Douglas > > When implementing interception using proxying the behaour of self invocation > is quite well defined, if a method is invoked on the proxy it is intercepted, > if it is invoked on the actual bean (usually through self-invocation) it is > not. > When implementing interception though sub classing this is much less well > definied, and the only way to track if an invocation is intercepted or not is > through a thread local flag. At the moment in weld this is reset when a call > is made on a client proxy, so if we have an intercepted bean A and a > SessionScoped bean B and A invokes B when invokes A the second call to A is > intercepted. If however B is pseudo scoped, then the second invocation is not > intercepted. The correct behaviour here should be specified by the > specification. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
