May 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Reopened: (CDI-46) Clarify in the specification that extensions do not require a beans.xml file

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-46?page=com.atlassian.jira.plugin.sys... ] Pete Muir reopened CDI-46: -------------------------- Assignee: Pete Muir > 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: Clarification > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Shane Bryzak > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-46) Clarify in the specification that extensions do not require a beans.xml file

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-46?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-46: ------------------------- Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) > 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: Clarification > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Shane Bryzak > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-46) Clarify in the specification that extensions do not require a beans.xml file

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-46?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-46. ------------------------ Resolution: Done > 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: Clarification > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Shane Bryzak > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-46) Clarify in the specification that extensions do not require a beans.xml file

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-46?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-46. ------------------------ Resolution: Done > 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: Clarification > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Shane Bryzak > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-78) Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-78?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-78: ------------------------- Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) > 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: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > > 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (CDI-131) Correct the signature of Interceptor.intercept() in the API

by Marius Bogoevici (JIRA)

Correct the signature of Interceptor.intercept() in the API ----------------------------------------------------------- Key: CDI-131 URL: https://issues.jboss.org/browse/CDI-131 Project: CDI Specification Issues Issue Type: Bug Components: Interceptors Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.1 (Confirmed) In addition to the corrections made by CDI-115 to the *text* of the specification, update the *API* with a correct definition for Interceptor.intercept() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-130) interceptor that return void, unclear in 1.0 specification, needs clarification in 1.1

by Richard Hightower (JIRA)

interceptor that return void, unclear in 1.0 specification, needs clarification in 1.1 -------------------------------------------------------------------------------------- Key: CDI-130 URL: https://issues.jboss.org/browse/CDI-130 Project: CDI Specification Issues Issue Type: Clarification Components: Interceptors Affects Versions: 1.1 (Proposed) Reporter: Richard Hightower Fix For: 1.1 (Proposed) The specification has an example in 9.5.1 that returns a void. AspectJ/AspectWerks annotation allow this (prior art). Can interceptors return void? The specification seem unclear on this. Well, it shows an example but there is no further verbiage. I get three different behaviors for this interceptor: package org.cdi.advocacy.security; import javax.inject.Inject; import javax.interceptor.AroundInvoke; import javax.interceptor.Interceptor; import javax.interceptor.InvocationContext; /** * @author Richard Hightower */ @Secure @Interceptor public class SecurityAdvice { @Inject private SecurityService securityManager; @AroundInvoke public void checkSecurity(InvocationContext joinPoint) throws Exception { System.out.println("In SecurityAdvice"); /* If the user is not logged in, don't let them use this method */ if(!securityManager.isLoggedIn()){ throw new SecurityViolationException(); } /* Get the name of the method being invoked. */ String operationName = joinPoint.getMethod().getName(); /* Get the name of the object being invoked. */ String objectName = joinPoint.getTarget().getClass().getName(); /* * Invoke the method or next Interceptor in the list, * if the current user is allowed. */ if (!securityManager.isAllowed(objectName, operationName)){ throw new SecurityViolationException(); } joinPoint.proceed(); } } Weld does not recognize it because it returns void. It fails silently. Candi recognizes it and uses it. OpenWebBeans throws an exception as follows: org.apache.webbeans.exception.WebBeansConfigurationException: @AroundInvoke annotated method : checkSecurity in class : org.cdi.advocacy.security.SecurityAdvice must return Object type at org.apache.webbeans.util.WebBeansUtil.checkAroundInvokeAnnotationCriterias(WebBeansUtil.java:1094) at org.apache.webbeans.util.WebBeansUtil.configureInterceptorMethods(WebBeansUtil.java:1241) at org.apache.webbeans.intercept.WebBeansInterceptorConfig.addMethodInterceptors(WebBeansInterceptorConfig.java:349) at org.apache.webbeans.intercept.WebBeansInterceptorConfig.configure(WebBeansInterceptorConfig.java:250) at org.apache.webbeans.config.DefinitionUtil.defineBeanInterceptorStack(DefinitionUtil.java:1058) at org.apache.webbeans.config.BeansDeployer.validate(BeansDeployer.java:365) at org.apache.webbeans.config.BeansDeployer.validateInjectionPoints(BeansDeployer.java:326) at org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:179) at org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:123) at org.cdiadvocate.beancontainer.OpenWebBeansBeanContainer.doStart(OpenWebBeansBeanContainer.java:26) at org.cdiadvocate.beancontainer.AbstractBeanContainer.start(AbstractBeanContainer.java:111) at org.cdi.advocacy.AtmMain.<clinit>(AtmMain.java:25) Exception in thread "main" java.lang.ExceptionInInitializerError Caused by: org.cdiadvocate.beancontainer.BeanContainerInitializationException: Unable to start BeanContainer : @AroundInvoke annotated method : checkSecurity in class : org.cdi.advocacy.security.SecurityAdvice must return Object type at org.cdiadvocate.beancontainer.AbstractBeanContainer.start(AbstractBeanContainer.java:113) at org.cdi.advocacy.AtmMain.<clinit>(AtmMain.java:25) Caused by: org.apache.webbeans.exception.WebBeansConfigurationException: @AroundInvoke annotated method : checkSecurity in class : org.cdi.advocacy.security.SecurityAdvice must return Object type at org.apache.webbeans.util.WebBeansUtil.checkAroundInvokeAnnotationCriterias(WebBeansUtil.java:1094) at org.apache.webbeans.util.WebBeansUtil.configureInterceptorMethods(WebBeansUtil.java:1241) at org.apache.webbeans.intercept.WebBeansInterceptorConfig.addMethodInterceptors(WebBeansInterceptorConfig.java:349) at org.apache.webbeans.intercept.WebBeansInterceptorConfig.configure(WebBeansInterceptorConfig.java:250) at org.apache.webbeans.config.DefinitionUtil.defineBeanInterceptorStack(DefinitionUtil.java:1058) at org.apache.webbeans.config.BeansDeployer.validate(BeansDeployer.java:365) at org.apache.webbeans.config.BeansDeployer.validateInjectionPoints(BeansDeployer.java:326) at org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.java:179) at org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication(AbstractLifeCycle.java:123) at org.cdiadvocate.beancontainer.OpenWebBeansBeanContainer.doStart(OpenWebBeansBeanContainer.java:26) at org.cdiadvocate.beancontainer.AbstractBeanContainer.start(AbstractBeanContainer.java:111) ... 1 more I think CDI 1.1 should clarify the behavior and I think it should support return types of void. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
10
0 / 0

[JBoss JIRA] Closed: (CDI-5) 9.5.1 Around-Invoke Interceptor example have wrong signature

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-5?page=com.atlassian.jira.plugin.syst... ] Pete Muir closed CDI-5. ----------------------- > 9.5.1 Around-Invoke Interceptor example have wrong signature > ------------------------------------------------------------ > > Key: CDI-5 > URL: https://issues.jboss.org/browse/CDI-5 > Project: CDI Specification Issues > Issue Type: Bug > Components: Interceptors > Affects Versions: 1.0 > Reporter: Aslak Knutsen > Assignee: Marius Bogoevici > Fix For: 1.1 (Confirmed) > > > The Interceptor example in section 9.5.1 use a illegal method signature for Around-Invoke interceptors: > @AroundInvoke > public void aroundInvoke() throws Exception { ... } > (void and no InvocationContex argument) > Around-invoke methods have the following signature: > Object <METHOD>(InvocationContext) throws Exception -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-5) 9.5.1 Around-Invoke Interceptor example have wrong signature

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-5?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-5: ------------------------ Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) > 9.5.1 Around-Invoke Interceptor example have wrong signature > ------------------------------------------------------------ > > Key: CDI-5 > URL: https://issues.jboss.org/browse/CDI-5 > Project: CDI Specification Issues > Issue Type: Bug > Components: Interceptors > Affects Versions: 1.0 > Reporter: Aslak Knutsen > Assignee: Marius Bogoevici > Fix For: 1.1 (Confirmed) > > > The Interceptor example in section 9.5.1 use a illegal method signature for Around-Invoke interceptors: > @AroundInvoke > public void aroundInvoke() throws Exception { ... } > (void and no InvocationContex argument) > Around-invoke methods have the following signature: > Object <METHOD>(InvocationContext) throws Exception -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (CDI-5) 9.5.1 Around-Invoke Interceptor example have wrong signature

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-5?page=com.atlassian.jira.plugin.syst... ] Marius Bogoevici resolved CDI-5. -------------------------------- Resolution: Done https://github.com/jboss/cdi/pull/22 > 9.5.1 Around-Invoke Interceptor example have wrong signature > ------------------------------------------------------------ > > Key: CDI-5 > URL: https://issues.jboss.org/browse/CDI-5 > Project: CDI Specification Issues > Issue Type: Bug > Components: Interceptors > Affects Versions: 1.0 > Reporter: Aslak Knutsen > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > The Interceptor example in section 9.5.1 use a illegal method signature for Around-Invoke interceptors: > @AroundInvoke > public void aroundInvoke() throws Exception { ... } > (void and no InvocationContex argument) > Around-invoke methods have the following signature: > Object <METHOD>(InvocationContext) throws Exception -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2011