March 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-416) Consider whether we should hold destroying the session context until all requests using it have ended

by Pete Muir (JIRA)

Consider whether we should hold destroying the session context until all requests using it have ended ----------------------------------------------------------------------------------------------------- Key: WELD-416 URL: https://jira.jboss.org/jira/browse/WELD-416 Project: Weld Issue Type: Feature Request Components: Scopes & Contexts Reporter: Pete Muir Assignee: David Allen Priority: Minor Fix For: 1.0.2.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

13 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-311) Producer field behavior differs from producer method

by alberto Gori (JIRA)

Producer field behavior differs from producer method ---------------------------------------------------- Key: WELD-311 URL: https://jira.jboss.org/jira/browse/WELD-311 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.0.0.CR1 Environment: Ubuntu 9.10, Java 6. Reporter: alberto Gori This producer field inject a Temp object into the request scope, corretly. @Named @SessionScoped public class HelloWorld implements Serializable { @Produces @RequestScoped @TenTemp public Temp getTemp() { return new Temp(10); } } The same producer written as a field create a session scoped object (note that the main bean is session scoped too) instead of request scoped. @Named @SessionScoped public class HelloWorld implements Serializable { @Produces @RequestScoped @TenTemp Temp t = new Temp(10); } -- 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

13 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (WELDX-81) Add support for onejar-maven-plugin

by Pieter Martin (JIRA)

Add support for onejar-maven-plugin ----------------------------------- Key: WELDX-81 URL: https://jira.jboss.org/jira/browse/WELDX-81 Project: Weld Extensions Issue Type: Feature Request Components: Weld Extensions Reporter: Pieter Martin The onejar-maven-plugin http://code.google.com/p/onejar-maven-plugin packages a project with all its dependencies into a single jar. The dependencies being nested jars inside the one jar. This is a nice way to make an executable jar for a java-se standalone project. However the current org.jboss.weld.environment.se.discovery.URLScanner does not support this as the classes are not in the expected place. Attached is a first attempt at modifying the URLScanner to support the onejar-maven-plugin -- 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

13 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-379) Use beans.xsd for validation of beans.xml

by Nicklas Karlsson (JIRA)

Use beans.xsd for validation of beans.xml ----------------------------------------- Key: WELD-379 URL: https://jira.jboss.org/jira/browse/WELD-379 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Priority: Minor 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-408) weld-servlet-javadoc.jar missing

by Wolfgang Frech (JIRA)

weld-servlet-javadoc.jar missing --------------------------------- Key: WELD-408 URL: https://jira.jboss.org/jira/browse/WELD-408 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Environment: n/a Reporter: Wolfgang Frech Priority: Trivial weld-servlet-javadoc.jar missing in distribution package weld-1.0.0.SP1.zip. All other JARs in folder artifacts have companion JARs with source and javadoc. Sorry for setting the priority to trivial. Saw note too late. Hope that committers agree. -- 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

13 years, 8 months

2
11
0 / 0

[JBoss JIRA] Created: (WELD-466) Injected dependent Instance<?> aren't registered as dependents

by Nicklas Karlsson (JIRA)

Injected dependent Instance<?> aren't registered as dependents -------------------------------------------------------------- Key: WELD-466 URL: https://jira.jboss.org/jira/browse/WELD-466 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson If we have @RequestScoped public class Foo { @Inject Instance<Bar> bar; } and bar has a dependent scoped producer/disposer pair, the disposer method is never called when Foo is destroyed since the Instance is not considered a dependent to Foo -- 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

13 years, 8 months

2
14
0 / 0

[JBoss JIRA] Created: (WELD-230) EL Literals not working in numberguess on Jetty or Tomcat.

by Steven Boscarine (JIRA)

EL Literals not working in numberguess on Jetty or Tomcat. ---------------------------------------------------------- Key: WELD-230 URL: https://jira.jboss.org/jira/browse/WELD-230 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.CR1 Environment: Ubuntu Jaunty Jackalope AMD64 Tomcat 6.0.20 mvn -version Apache Maven 2.2.0 (r788681; 2009-06-26 09:04:01-0400) Java version: 1.6.0_16 Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.28-16-generic" arch: "amd64" Family: "unix" Reporter: Steven Boscarine Is the examples POM in Weld 1 CR1 may be importing the wrong EL lib version? I am having a hard time getting EL Literals working in Jetty or Tomcat. I first tried in my own app and couldn't get them working, so I tried modifying the numberguess example home.xhtml file to: <div> I'm thinking of a number between #{game.getSmallest()} and #{game.biggest}. You have #{game.remainingGuesses} guesses. </div> ...and got: 2009-10-21 23:22:22.697::WARN: /weld-numberguess/home.jsf java.lang.NoSuchMethodError: javax.el.ELResolver.invoke(Ljavax/el/ELContext;Ljava/lang/Object;Ljava/lang/Object;[Ljava/lang/Class;[Ljava/lang/Object;)Ljava/lang/Object; at com.sun.el.parser.AstValue.getValue(AstValue.java:111) at com.sun.el.parser.AstValue.getValue(AstValue.java:163) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:219) at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:71) at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:71) at com.sun.faces.facelets.el.ELText$ELTextVariable.writeText(ELText.java:217) at com.sun.faces.facelets.el.ELText$ELTextComposite.writeText(ELText.java:141) at com.sun.faces.facelets.compiler.TextInstruction.write(TextInstruction.java:78) at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:74) at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:178) at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:848) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1610) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1613) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:340) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:273) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:915) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) If it helps, according to mvn site, the versions are: javax.el el-api 2.1.2-b04 org.glassfish.web el-impl 2.1.2-b04 -- 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

13 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (WELD-459) A final class interceptor or an interceptor class with a final method not detected as a definition error

by Ondrej Skutka (JIRA)

A final class interceptor or an interceptor class with a final method not detected as a definition error -------------------------------------------------------------------------------------------------------- Key: WELD-459 URL: https://jira.jboss.org/jira/browse/WELD-459 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Ondrej Skutka Spec says: If the bean class of a managed bean declares or inherits a class level interceptor binding or a stereotype with interceptor bindings, it must not be declared final, or have any non-static, non-private, final methods. If a managed bean has a class- level interceptor binding and is declared final or has a non-static, non-private, final method, the container automatically detects the problem and treats it as a definition error. If a non-static, non-private method of a bean class of a managed bean declares a method level interceptor binding, neither the method nor the bean class may be declared final. If a non-static, non-private, final method of a managed bean has a method level interceptor binding, the container automatically detects the problem and treats it as a definition error. org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalClassClassLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalClassMethodLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalMethodClassLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalMethodMethodLevelInterceptorTest In the TCK trunk -- 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

13 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (WELDX-48) Revisit the way we bind BeanManager to JNDI in Tomcat.

by Pete Muir (JIRA)

Revisit the way we bind BeanManager to JNDI in Tomcat. ------------------------------------------------------ Key: WELDX-48 URL: https://jira.jboss.org/jira/browse/WELDX-48 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Reporter: Pete Muir Currently we rely on the deprecated ManagerObjectFactory in core. Also talk to Remy, see if there is way to bind to the correct place in 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

13 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (WELDX-49) error during shutdown on Jetty: no class org.apache.AnnotationProcessor

by Dan Allen (JIRA)

error during shutdown on Jetty: no class org.apache.AnnotationProcessor ----------------------------------------------------------------------- Key: WELDX-49 URL: https://jira.jboss.org/jira/browse/WELDX-49 Project: Weld Extensions Issue Type: Bug Components: Servlet Containers Affects Versions: Servlet Containers 1.0.0.CR2 Reporter: Dan Allen Assignee: Dan Allen Fix For: Servlet Containers 1.0.0.CR3 Exception in thread "Shutdown" java.lang.NoClassDefFoundError: org/apache/AnnotationProcessor ... at org.jboss.weld.environment.servlet.Listener.contextDestroyed(Listener.java:81) Because of this line: sce.getServletContext().removeAttribute(WeldAnnotationProcessor.class.getName()); Need to check for class being available. -- 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

13 years, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2010