January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-222) Coordinate with Mojarra to get Weld JSF app working from Maven central

by Dan Allen (JIRA)

Coordinate with Mojarra to get Weld JSF app working from Maven central ---------------------------------------------------------------------- Key: WELD-222 URL: https://jira.jboss.org/jira/browse/WELD-222 Project: Weld Issue Type: Feature Request Components: Infrastructure Reporter: Dan Allen Fix For: 1.0.0.CR2 Although the Weld artifacts are published to the Maven central repository, it's still not possible to get a JSF app built without relying on the JBoss Maven repository. The problem is JSF. See output below. We have sent a request to the Mojarra team to publish their artifacts in the central repository. When they do, we need to align with that version. Missing: ---------- 1) javax.faces:jsf-api:jar:2.0.0-RC Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.example:helloworld:war:0.0.1-SNAPSHOT 2) javax.faces:jsf-api:jar:2.0.0-RC ---------- 1 required artifact is missing. for artifact: org.example:helloworld:war:0.0.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) However, if you add java.net repository and override the JSF versions to use the 2.0 release, you get errors on startup INFO: Weld 1.0.0-CR1 2009-10-21 21:58:22.119::WARN: Failed startup of context org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@66f4652{/jsf2,/home/lily/workspace/jsf2/0_helloworld/src/main/webapp} java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:401) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363) at org.mortbay.jetty.handler.ContextHandler.loadClass(ContextHandler.java:1101) at org.mortbay.jetty.plugin.Jetty6MavenConfiguration.parseAnnotations(Jetty6MavenConfiguration.java:135) at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configure(AbstractConfiguration.java:119) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureWebApp(WebXmlConfiguration.java:180) at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configureWebApp(AbstractConfiguration.java:96) at org.mortbay.jetty.plus.webapp.Configuration.configureWebApp(Configuration.java:149) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1247) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) -- 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, 3 months

2
18
0 / 0

[JBoss JIRA] Created: (WELDINT-19) Bind BeanManager to java:comp/BeanManager not java:app/BeanManager

by Pete Muir (JIRA)

Bind BeanManager to java:comp/BeanManager not java:app/BeanManager ------------------------------------------------------------------ Key: WELDINT-19 URL: https://jira.jboss.org/jira/browse/WELDINT-19 Project: Weld Integration Issue Type: Bug Components: Deployer Reporter: Pete Muir Assignee: Pete Muir Fix For: 5.2.0.Beta4 -- 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, 3 months

3
11
0 / 0

[JBoss JIRA] Created: (WELDINT-23) ProcessAnnotatedType not fired for Filter, Tag Library Listener, Servlet Listener and JSF Managed Bean

by Jozef Hartinger (JIRA)

ProcessAnnotatedType not fired for Filter, Tag Library Listener, Servlet Listener and JSF Managed Bean ------------------------------------------------------------------------------------------------------ Key: WELDINT-23 URL: https://jira.jboss.org/jira/browse/WELDINT-23 Project: Weld Integration Issue Type: Bug Reporter: Jozef Hartinger Assignee: Pete Muir Fix For: 5.2.0.Beta5 org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForFilter() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForJsfManagedBean() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForTagLibraryListener() org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessAnnotatedTypeEventFiredForServletListener() -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-269) Registration of a custom implementation of the Decorator interface fails

by Jozef Hartinger (JIRA)

Registration of a custom implementation of the Decorator interface fails ------------------------------------------------------------------------ Key: WELD-269 URL: https://jira.jboss.org/jira/browse/WELD-269 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Assignee: Marius Bogoevici Fix For: 1.0.0.CR2 org.jboss.jsr299.tck.tests.decorators.custom.CustomDecoratorTest.testCustomImplementationOfDecoratorInterface() -- 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, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (WELD-328) Do nightly build of distribution

by Pete Muir (JIRA)

Do nightly build of distribution -------------------------------- Key: WELD-328 URL: https://jira.jboss.org/jira/browse/WELD-328 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.1.CR1 -- 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (WELD-248) Manifest should use osgi version, not maven version

by Pete Muir (JIRA)

Manifest should use osgi version, not maven version --------------------------------------------------- Key: WELD-248 URL: https://jira.jboss.org/jira/browse/WELD-248 Project: Weld Issue Type: Feature Request Components: Infrastructure Reporter: Pete Muir Priority: Blocker Fix For: 1.0.0.CR2 -- 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, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-399) Conversation should work on AppEngine

by Paul Bakker (JIRA)

Conversation should work on AppEngine ------------------------------------- Key: WELD-399 URL: https://jira.jboss.org/jira/browse/WELD-399 Project: Weld Issue Type: Feature Request Components: Conversations Affects Versions: 1.0.0.GA Environment: Google AppEngine 1.3 Reporter: Paul Bakker Priority: Optional Weld works pretty well on GAE, which is of course great in combination with JSF 2. The only problem I've ran into so far is that conversations don't work. GAE doesn't allow threading, and the cleanup scheduler in Weld brakes this rule. The problem is in org.jboss.weld.conversation.AbstractConversationManager.scheduleForTermination(AbstractConversationManager.java:204) This is obviously not a bug, it's just a GAE problem. I'm not sure how this should be solved in a clean way, disabling the cleanup task when running on GAE seems like a bad idea (memory leaks). It might be an idea to create a GAE task queue for cleanup, but this would require GAE specific code. -- 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, 7 months

3
8
0 / 0

[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, 7 months

2
1
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, 7 months

3
8
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, 7 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010