November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDX-190) Provide a utility to transparently wrap primitive types

by Dan Allen (JIRA)

Provide a utility to transparently wrap primitive types -------------------------------------------------------- Key: WELDX-190 URL: https://jira.jboss.org/browse/WELDX-190 Project: Weld Extensions Issue Type: Feature Request Affects Versions: 1.0.0.Beta1 Reporter: Dan Allen Fix For: 1.0.0.Beta2 When dealing at the level of a Type, it would be helpful to have a method that would automatically convert the Type to a primitive wrapper if the original Type represents a primitive. This functionality is provided by the Primitives class in Guava. Type type = Primitives.wrap(ip.getType()); At this point, we know that "type" does not represent a primitive. http://guava-libraries.googlecode.com/svn/trunk/javadoc/com/google/common... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-188) ContextTest and ContextDestroysBeansTest must be excluded from tests

by Gurkan Erdogdu (JIRA)

ContextTest and ContextDestroysBeansTest must be excluded from tests -------------------------------------------------------------------- Key: CDITCK-188 URL: https://jira.jboss.org/browse/CDITCK-188 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Gurkan Erdogdu org.jboss.jsr299.tck.tests.context.ContextTest and org.jboss.jsr299.tck.tests.context.ContextDestroysBeansTest "Class MyContextual implements Bean<MySessionBean>" is a session scoped bean and must be passivation capable. To do this, it must implement "PassivationCapable" interface. But it does not implement it. Actually, this issue has been reported and resolved in CR2 Those tests must be excluded from tests. But currently, they are not excluded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
5
0 / 0

[JBoss JIRA] Created: (WELDX-189) Provide utility to extract type parameter from Instance

by Dan Allen (JIRA)

Provide utility to extract type parameter from Instance ------------------------------------------------------- Key: WELDX-189 URL: https://jira.jboss.org/browse/WELDX-189 Project: Weld Extensions Issue Type: Feature Request Affects Versions: 1.0.0.Beta1 Reporter: Dan Allen Priority: Minor Fix For: 1.0.0.Beta2 When discovering injection points, a type of Instance<T> is effectively the same as discovering a type T. You don't want to create a producer method for an Instance, for instance, hence why you want to figure out what T is. Thus, it's common to want to extract the type parameter from Instance. Having a utility would be convenient. Here's an example that collects the actual bean types (extracting from the Instance type parameter if necessary) Set<Type> types = new HashSet<Type>(); for (InjectionPoint ip : event.getInjectionTarget().getInjectionPoints()) { types.add(Reflections.getActualType(ip.Type())); } Here's the utility: private static Type getActualType(Type t) { if (t instanceof ParameterizedType && ((ParameterizedType) t).getRawType().equals(Instance.class)) { return ((ParameterizedType) t).getActualTypeArguments()[0]; } return t; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (WELD-749) resteasy BDA throws NPE for EJB annotation when two applications are deployed

by Nicklas Karlsson (JIRA)

resteasy BDA throws NPE for EJB annotation when two applications are deployed ----------------------------------------------------------------------------- Key: WELD-749 URL: https://jira.jboss.org/browse/WELD-749 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.0.Beta2 Environment: 6.0.0-SNAPSHOT Reporter: Nicklas Karlsson First application deploys fine Second application fails for the resteasy BDA when trying to instantiate the @EJB class(?) 15:25:10,132 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Create: name=vfs:///C:/Java/AS/jboss-6.0.0-SNAPSHOT/server/default/deploy/LTK.war_WeldBootstrapBean state=Configured: java.lang.NullPointerException at org.jboss.weld.integration.deployer.env.bda.ClassLoaderResourceLoader.classForName(ClassLoaderResourceLoader.java:30) [:6.0.0-SNAPSHOT] at org.jboss.weld.util.ApiAbstraction.annotationTypeForName(ApiAbstraction.java:87) [:6.0.0-SNAPSHOT] at org.jboss.weld.ejb.EJBApiAbstraction.<init>(EJBApiAbstraction.java:36) [:6.0.0-SNAPSHOT] at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:100) [:6.0.0-SNAPSHOT] at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:181) [:6.0.0-SNAPSHOT] at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:192) [:6.0.0-SNAPSHOT] at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:152) [:6.0.0-SNAPSHOT] at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:283) [:6.0.0-SNAPSHOT] at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.initialize(BootstrapBean.java:106) [:6.0.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_20] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (WELD-732) Weld ignores observer methods declared in superclasses

by Igor Vaynberg (JIRA)

Weld ignores observer methods declared in superclasses ------------------------------------------------------ Key: WELD-732 URL: https://jira.jboss.org/browse/WELD-732 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Beta1 Reporter: Igor Vaynberg Currently when discovering observers weld only checks declared methods of the class, which ignores any observers declared in superclasses that should be inherited. {code} AbstractBeanDeployer: protected <X> void createObserverMethods(RIBean<X> declaringBean, WeldClass<X> annotatedClass) { for (WeldMethod<?, ? super X> method : annotatedClass.getDeclaredWeldMethodsWithAnnotatedParameters(Observes.class)) { createObserverMethod(declaringBean, method); } } {code} Notice the use of get*Declared*WeldMethodsWithAnnotatedParameters(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] Created: (WELD-741) AbstractConversationContext calls conversaiton.end() without checking if its transient

by Igor Vaynberg (JIRA)

AbstractConversationContext calls conversaiton.end() without checking if its transient -------------------------------------------------------------------------------------- Key: WELD-741 URL: https://jira.jboss.org/browse/WELD-741 Project: Weld Issue Type: Bug Reporter: Igor Vaynberg {code} org.jboss.weld.exceptions.IllegalStateException: WELD-000215 Attempt to call end() on a transient conversation org.jboss.weld.context.conversation.ConversationImpl.end(ConversationImpl.java:124) org.jboss.weld.context.AbstractConversationContext.invalidate(AbstractConversationContext.java:307) org.jboss.weld.wicket.WeldRequestCycle.detach(WeldRequestCycle.java:121) {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (WELD-742) Fix the set of decorated types of a decorator

by Marius Bogoevici (JIRA)

Fix the set of decorated types of a decorator --------------------------------------------- Key: WELD-742 URL: https://jira.jboss.org/browse/WELD-742 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.1.0.Beta2 a) The set of decorated types of a decorator must include the interfaces of its superclasses b) The set of decorated types of a decorator must take @Typed into account -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (WELD-699) CDI API regression: Observes.notifyObserver has been changed to Observes.receive

by Sivakumar Thyagarajan (JIRA)

CDI API regression: Observes.notifyObserver has been changed to Observes.receive -------------------------------------------------------------------------------- Key: WELD-699 URL: https://jira.jboss.org/browse/WELD-699 Project: Weld Issue Type: Bug Components: CDI API Affects Versions: 1.1.0.Beta1 Reporter: Sivakumar Thyagarajan In the Weld 1.1 Beta 1 release, the @Observes API has an annotation element changed. This is an incompatible API change and would break existing clients. -- The original API for @Observes -- public interface javax.enterprise.event.Observes extends java.lang.annotation.Annotation{ public abstract javax.enterprise.event.Reception notifyObserver(); public abstract javax.enterprise.event.TransactionPhase during(); } -- The original API for @Observes -- and now it is: -- The new API for @Observes -- public interface javax.enterprise.event.Observes extends java.lang.annotation.Annotation{ public abstract javax.enterprise.event.Reception receive(); public abstract javax.enterprise.event.TransactionPhase during(); } -- The new API for @Observes -- Notice the renaming of "notifyObserver" to "receive". The original name for the annotation element "notifyObserver" has been published earlier as part of Java EE 6 javadoc [1]. However in the JSR 299 specification, the annotation element is referred to as "receives" (See Section 10.4.3) and hence I think this have been renamed as part of WELD-455 [2]. Please revert this change in API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
4
0 / 0

[JBoss JIRA] Created: (WELD-727) Remove partial export of javassist from weld osgi bundle

by Sivakumar Thyagarajan (JIRA)

Remove partial export of javassist from weld osgi bundle -------------------------------------------------------- Key: WELD-727 URL: https://jira.jboss.org/browse/WELD-727 Project: Weld Issue Type: Bug Components: OSGi support Affects Versions: 1.1.0.Beta1 Reporter: Sivakumar Thyagarajan Fix For: 1.1.0.Beta2 The current weld osgi bundle exports javassist.util.proxy. This was earlier done in Weld 1.0 for handling references to util.proxy classes during proxy class loading in the context of an application classloader. With the new proxy SPI changes, it is possible for a Weld SPI implementation to provide a classloader to handle Proxy class loading. This make the current export of javassist.util.proxy unnecessary and also has been known to cause other issues [see GlassFish issue 12368 and WELD-570] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] Created: (WELD-662) weld-servlet-jboss5 can't scan jars nested in jars

by Pete Muir (JIRA)

weld-servlet-jboss5 can't scan jars nested in jars -------------------------------------------------- Key: WELD-662 URL: https://jira.jboss.org/browse/WELD-662 Project: Weld Issue Type: Bug Components: Servlet Container Support Reporter: Pete Muir Fix For: 1.1.0.Beta2 If you try deploying a non-exploded war to EAP 5.1 with weld-servlet-jboss5 with jars to scan in WEB-INF/lib, the scanner fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2010