April 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-240) Incorrect detection of Tomcat

by Daniel Munzinger (JIRA)

Incorrect detection of Tomcat ----------------------------- Key: WELD-240 URL: https://jira.jboss.org/jira/browse/WELD-240 Project: Weld Issue Type: Bug Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.0.CR1 Environment: Windows, Tomcat 7.0.0 from trunk, Weld Servlet 1.0.0.CR1 Reporter: Daniel Munzinger Priority: Minor I've been playing around with the Tomcat 7 development stream from SVN trunk when I came across this litte message: "JSR-299 injection will not be available in Servlets, Filters etc. This facility is only available in Tomcat" I managed to locate the source of this message at org.jboss.weld.environment.servlet.Listener:114 when calling Reflections.classForName("org.apache.AnnotationProcessor"); This class is not present in the current code base which makes "tomcat = false" and Weld thinks that there is no tomcat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] Created: (WELDX-84) Merge tomcat-support and jetty-support into weld-servlet

by Pete Muir (JIRA)

Merge tomcat-support and jetty-support into weld-servlet -------------------------------------------------------- Key: WELDX-84 URL: https://jira.jboss.org/jira/browse/WELDX-84 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Reporter: Pete Muir Currently we package these as separate jars, due to classloading restrictions. Would be more convenient for the user to package these in the same jar. If we can find a better way to add the injection support to Tomcat and Jetty, then perhaps we can do away with this altogether. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
8
0 / 0

[JBoss JIRA] Created: (WELD-487) When validating serializability of Decorators, delegate injection points should be ignored

by Marius Bogoevici (JIRA)

When validating serializability of Decorators, delegate injection points should be ignored ------------------------------------------------------------------------------------------ Key: WELD-487 URL: https://jira.jboss.org/jira/browse/WELD-487 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.0.2.CR1 Decorators of a passivation capable bean must be passivation capable as well. This includes a check as to whether their injection points are passivation capable. In the current implementation, an @Inject @Delegate @Any delegation point will be reported as an ambiguous dependency, although this does not happen elsewhere. Solution: @Inject @Delegate injection points must not be checked for passivation capability. The decorator being validated has already been selected *because* it decorates a passivation capable bean, so we know that the delegate is passivation capable (even if we deal with a chain of decorators, all decorators must be passivation capable). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (WELDX-90) weld-extensions-bom 1.0.0-CR2, undefined ${testng.version} reference

by Adam Warski (JIRA)

weld-extensions-bom 1.0.0-CR2, undefined ${testng.version} reference -------------------------------------------------------------------- Key: WELDX-90 URL: https://jira.jboss.org/jira/browse/WELDX-90 Project: Weld Extensions Issue Type: Bug Components: Weld Extensions Affects Versions: Archetypes 1.0.0.Beta1 Reporter: Adam Warski The bom contains a reference to ${testng.version}, which isn't then specified in the properties. This causes mvn:site to fail in projects using the bom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] Commented: (WELDX-23) Support servlet injection on Jetty

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELDX-23?page=com.atlassian.jira.plugi... ] Pete Muir commented on WELDX-23: -------------------------------- Patch looks good. > Support servlet injection on Jetty > ---------------------------------- > > Key: WELDX-23 > URL: https://jira.jboss.org/jira/browse/WELDX-23 > Project: Weld Extensions > Issue Type: Feature Request > Components: Servlet Containers > Reporter: Pete Muir > Assignee: Matija Mazi > Attachments: jetty-injection.patch, jetty-injection.patch, jetty-injection.patch, jetty-injection.patch, jetty-web.xml, myapp-context.xml > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (WELD-56) Supporting proxies with no no-arg constructors

by Nicklas Karlsson (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-56?page=com.atlassian.jira.plugin... ] Nicklas Karlsson closed WELD-56. -------------------------------- Resolution: Done > Supporting proxies with no no-arg constructors > ---------------------------------------------- > > Key: WELD-56 > URL: https://jira.jboss.org/jira/browse/WELD-56 > Project: Weld > Issue Type: Feature Request > Components: Scopes & Contexts > Reporter: Pete Muir > Assignee: Nicklas Karlsson > Fix For: 1.1.0.BETA1 > > > On Tue, May 12, 2009 at 1:11 AM, Jason T. Greene > <jason.greene(a)redhat.com> wrote: > Hi Everyone, > As a non-standard extension, I was thinking that we could support generation > proxies of classes not containing no-arg constructors by using various > techniques that are supported by most JDKs. > This would involve generating a proxy with a constructor call passing bogus > parameters. Then a JDK specific approach would be used to instantiate the > proxy class: > Sun, IcedTea, Mac: Unsafe.allocateInstance() - The most efficient > Above + IBM, JRockit: ReflectionFactory.newConstructorForSerialization() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Reopened: (WELD-56) Supporting proxies with no no-arg constructors

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-56?page=com.atlassian.jira.plugin... ] Pete Muir reopened WELD-56: --------------------------- After discussion on IRC, we should change this to have the presence of a classpath resource e.g. META-INF/org.jboss.weld.enableUnsafeProxies (not in services as Stuart said) be what switches on the code. > Supporting proxies with no no-arg constructors > ---------------------------------------------- > > Key: WELD-56 > URL: https://jira.jboss.org/jira/browse/WELD-56 > Project: Weld > Issue Type: Feature Request > Components: Scopes & Contexts > Reporter: Pete Muir > Assignee: Nicklas Karlsson > Fix For: 1.1.0.BETA1 > > > On Tue, May 12, 2009 at 1:11 AM, Jason T. Greene > <jason.greene(a)redhat.com> wrote: > Hi Everyone, > As a non-standard extension, I was thinking that we could support generation > proxies of classes not containing no-arg constructors by using various > techniques that are supported by most JDKs. > This would involve generating a proxy with a constructor call passing bogus > parameters. Then a JDK specific approach would be used to instantiate the > proxy class: > Sun, IcedTea, Mac: Unsafe.allocateInstance() - The most efficient > Above + IBM, JRockit: ReflectionFactory.newConstructorForSerialization() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (WELD-381) Proxied EJBs as Injection point, wrong interface chosen

by John Ament (JIRA)

Proxied EJBs as Injection point, wrong interface chosen ------------------------------------------------------- Key: WELD-381 URL: https://jira.jboss.org/jira/browse/WELD-381 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.0.GA Environment: GF v3, JDK 1.6, Windows Reporter: John Ament Based on the forum post, The following EJB cannot be injected into clients: @DAO @Local(ResultDAOBean.class) @Stateless public ResultDAO extends AbstractDAO<Result> implements ResultDAOBean Happens the same with/without @Local The problem comes in when AbstractDAO implements something (e.g. AbstractDAOBean<E>) or ResultDAOBean extends an interfacet (e.g.AbstractDAOBean<E>). The interface AbstractDAOBean isn't marked as an EJB itnerface, and only one of these two would implement/extend it (ideally, ResultDAOBean). The injection point results in the following exception: Caused by: java.lang.IllegalStateException: Unable to convert ejbRef for ejb ResultDAO to a business object of type interface AbstractDAOBean at com.sun.ejb.containers.EjbContainerServicesImpl.getBusinessObject(EjbContainerServicesImpl.java:104) at org.glassfish.weld.ejb.SessionObjectReferenceImpl.getBusinessObject(SessionObjectReferenceImpl.java:60) at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:121) at jpa.dao.EvaluationDAOBean_$$_javassist_110.getEM(EvaluationDAOBean_$$_javassist_110.java) at NewSessionBean.init(NewSessionBean.java:30) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.ejb.containers.interceptors.BeanCallbackInterceptor.intercept(InterceptorManager.java:1006) at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:61) at com.sun.ejb.containers.interceptors.CallbackInvocationContext.proceed(CallbackInvocationContext.java:109) at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doCallback(SystemInterceptorProxy.java:133) at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.init(SystemInterceptorProxy.java:115) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.ejb.containers.interceptors.CallbackInterceptor.intercept(InterceptorManager.java:961) at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:61) at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:390) at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:373) at com.sun.ejb.containers.AbstractSingletonContainer.createSingletonEJB(AbstractSingletonContainer.java:518) ... 38 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (WELD-470) Log debug and trace streamlining, separation of error and log messages

by Nicklas Karlsson (JIRA)

Log debug and trace streamlining, separation of error and log messages ---------------------------------------------------------------------- Key: WELD-470 URL: https://jira.jboss.org/jira/browse/WELD-470 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Fix For: 1.0.2.CR1 Some components do a lot of debug/trace log, some little and some not at all. Best practices need to be worked out and applied Also, splitting out the messages into log and errors might be a good idea so we don't have @MessageId("000008") CALL_PROXIED_METHOD -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (WELD-397) Warn if a scope annotation is put at an injection point

by Pete Muir (JIRA)

Warn if a scope annotation is put at an injection point ------------------------------------------------------- Key: WELD-397 URL: https://jira.jboss.org/jira/browse/WELD-397 Project: Weld Issue Type: Feature Request Components: Scopes & Contexts Reporter: Pete Muir Priority: Minor Fix For: 1.0.1.CR1 Users are getting confused :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2010