June 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-261) Tidy up OSGi exports

by Pete Muir (JIRA)

Tidy up OSGi exports -------------------- Key: WELD-261 URL: https://jira.jboss.org/jira/browse/WELD-261 Project: Weld Issue Type: Task Components: OSGi support Reporter: Pete Muir Priority: Critical 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (CDITCK-62) The Weld Porting Package Impls provided by the TCK should support OSGI

by Kyle Grucci (JIRA)

The Weld Porting Package Impls provided by the TCK should support OSGI ---------------------------------------------------------------------- Key: CDITCK-62 URL: https://jira.jboss.org/jira/browse/CDITCK-62 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: All Reporter: Kyle Grucci Fix For: 1.0.1.CR1 The current porting package impl classes provided with the TCK work with Weld in a non-OSGI environment. It would be great in the future if the impls can also work out of the box with Weld in an OSGI environment. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-497) Check for null in BeanManager.getReference()

by Jozef Hartinger (JIRA)

Check for null in BeanManager.getReference() -------------------------------------------- Key: WELD-497 URL: https://jira.jboss.org/jira/browse/WELD-497 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.1.Final Reporter: Jozef Hartinger Assignee: Pete Muir Priority: Minor Fix For: 1.0.2.CR1 Weld currently throws the following exception if the "bean" parameter is null during getReference() invocation Caused by: java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:810) An exception with self-explanatory message should be thrown instead. Also, check the other parameters for null values. -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-273) Add GlassFish targets to example POMs

by Pete Muir (JIRA)

Add GlassFish targets to example POMs ------------------------------------- Key: WELD-273 URL: https://jira.jboss.org/jira/browse/WELD-273 Project: Weld Issue Type: Feature Request Components: Examples, GlassFish Integration 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

13 years, 5 months

1
7
0 / 0

[JBoss JIRA] Created: (WELD-554) org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml

by NIkola Nikolic (JIRA)

org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml --------------------------------------------------------------------------------------------- Key: WELD-554 URL: https://jira.jboss.org/browse/WELD-554 Project: Weld Issue Type: Bug Components: Conversations Environment: Microsoft Windows 7 Professional. Java 1.6.0_18-b07. Glassfish-3.0.1-b20. Reporter: NIkola Nikolic org.jboss.weld.context.NonexistentConversationException can't be catched by a rule in web.xml. Let's say that page http://localhost:8080/test6/faces/index.xhtml?cid=1 can be rendered. If conversation time out and user tries to access page again, error page occures with following message: XML Parsing Error: no element found Location: http://localhost:8080/test6/faces/index.xhtml?cid=3 Line Number 1, Column 1: even if rule for exception exists in web.xml <error-page> <exception-type>org.jboss.weld.context.NonexistentConversationException</exception-type> <location>/faces/error.xhtml</location> </error-page> Same error occures if user change url manualy by changing cid number to non existing. -- 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

13 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (WELDSE-23) Disable logging out of the box

by Peter Royle (JIRA)

Disable logging out of the box ------------------------------ Key: WELDSE-23 URL: https://jira.jboss.org/jira/browse/WELDSE-23 Project: Weld support for Java SE Issue Type: Feature Request Affects Versions: 1.0.1.Final Reporter: Peter Royle Assignee: Peter Royle Priority: Minor Fix For: 1.0.2.CR1 The presence of SLF4J-simple within the Weld SE jar causes problems for those wanting to use a different SLF4J provider (eg: jdk14). This comment from Ceki points to a good solution, using SLF4J 1.6: Ceki Gulcu - 23/Apr/10 04:17 AM As of SLF4J version 1.6.0, if no binding is found on the class path, then slf4j-api will default to a no-operation implementation discarding all log requests. Thus, instead of throwing an exception, SLF4J will emit a single warning message about the absence of a binding and proceed to discard all log requests without further protest. If Weld's distribution includes slf4j-api.jar but no binding, then even in the absence of any SLF4J binding on the class path, Weld's distribution will still work out-of-the-box, and without requiring the end-user to download a binding from SLF4J's web-site. Only when the end-user wishes to enable logging will she need to install a binding. The problem with this currently is that version 1.6 is still alpha, so resolution of this issue will have to wait until version 1.6 is released as stable, and becomes available in the JBoss maven repositories: -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-478) Tomcat dependencies are incomplete in documentation

by Hontvári József (JIRA)

Tomcat dependencies are incomplete in documentation --------------------------------------------------- Key: WELD-478 URL: https://jira.jboss.org/jira/browse/WELD-478 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.1.Final Reporter: Hontvári József In section 18.3. there is a list of dependencies for servlet containers. This is incomplete, it does not list all dependecies and it also does not specify their versions. After tracking some NoClassDefFoundError, here are some additional jars: -jsr299-api.jar is listed but this does not exist in Weld 1.0.1.Final distribution. Likely this is cdi-api.jar from the artifacts/cdi directory. -weld-logging.jar is listed, but I cannot find such jar. Likely this entry is obsolete. -cal10n-api-0.7.2.jar -javax.inject-1.jar -jboss-interceptor-1.0.0-CR11.jar -jboss-interceptor-api-1.1.jar -slf4j-ext-1.5.10.jar After adding these jars Weld starts with the web application but org.jboss.weld.environment.servlet.Listener throws a com.google.common.collect.ComputationException: java.lang.reflect.GenericSignatureFormatError. I tries to follow the maven configuration, but without success, I can only guess that I included the wrong version of one of the jars. -- 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, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (CDITCK-149) Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest

by Gurkan Erdogdu (JIRA)

Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest ----------------------------------------------------------- Key: CDITCK-149 URL: https://jira.jboss.org/jira/browse/CDITCK-149 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu org.jboss.jsr299.tck.tests.context.MyContextual is a SessionScoped bean.As spec section 6.6.4 it must be passivation capable, but it is not. therefore it throws Definition exception -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-475) Setup / teardown conversation in WeldListener and not in the PhaseListener

by Nicklas Karlsson (JIRA)

Setup / teardown conversation in WeldListener and not in the PhaseListener -------------------------------------------------------------------------- Key: WELD-475 URL: https://jira.jboss.org/jira/browse/WELD-475 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Assignee: Nicklas Karlsson Fix For: 1.0.2.CR1 "The conversation scope is active during all standard lifecycle phases of any JSF faces or non-faces request.". The conversation should be resumed at at that point, too? -- 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, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-286) jsf/permalink example fails with "identifier 'blog' resolved to null"

by Ondrej Skutka (JIRA)

jsf/permalink example fails with "identifier 'blog' resolved to null" --------------------------------------------------------------------- Key: WELD-286 URL: https://jira.jboss.org/jira/browse/WELD-286 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.GA Reporter: Ondrej Skutka jsf/permalink example deploys, but when accessing the application it fails with following exception: 13:56:27,628 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception javax.el.PropertyNotFoundException: /home.xhtml @30,78 listener="#{blog.loadLatestEntries}": Target Unreachable, identifier 'blog' resolved to null at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:100) at com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:112) at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2342) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:102) at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:1993) at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:1941) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:285) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:243) at org.jboss.weld.integration.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:336) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:114) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- 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, 6 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2010