March 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-869) Weld OSGi bundle reports version as ${parsedVersion.osgiVersion}

by Dan Allen (JIRA)

Weld OSGi bundle reports version as ${parsedVersion.osgiVersion} ---------------------------------------------------------------- Key: WELD-869 URL: https://issues.jboss.org/browse/WELD-869 Project: Weld Issue Type: Bug Components: OSGi support Affects Versions: 1.1.0.Final Reporter: Dan Allen Priority: Minor When Weld starts on GlassFish, it reports it's version as: WELD-000900 ${parsedVersion (osgiVersion}) The version is read from the MANIFEST.MF, which has this line: Specification-Version: ${parsedVersion.osgiVersion} The replacement doesn't seem to be working properly in the osgi build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (WELDX-51) Create a single jar file for Weld SE that includes all dependencies

by Pete Muir (JIRA)

Create a single jar file for Weld SE that includes all dependencies ------------------------------------------------------------------- Key: WELDX-51 URL: https://jira.jboss.org/jira/browse/WELDX-51 Project: Weld Extensions Issue Type: Feature Request Components: Java SE Reporter: Pete Muir Fix For: Java SE 1.0.0.CR3 To make using Weld SE easy, we should create a single jar (primarily for use at runtime, at compile time you would depend just on cdi-api of course) * cdi-api * weld-api * weld-spi * weld-core * weld-se -- 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

5
14
0 / 0

[JBoss JIRA] Created: (WELD-876) BeanXmlParser fails when woodstock is the underlying parser

by Stuart Douglas (JIRA)

BeanXmlParser fails when woodstock is the underlying parser ----------------------------------------------------------- Key: WELD-876 URL: https://issues.jboss.org/browse/WELD-876 Project: Weld Issue Type: Bug Reporter: Stuart Douglas Priority: Minor BeansXmlParser has the following code: try { parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema"); parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource", loadXsds()); } catch (IllegalArgumentException e) { // No op, we just don't validate the XML } However, the actual exception thrown (according to the javadoc) is a SAXNotRecognizedException or a SAXNotSupportedException, which means that if the underlying SAX impl does not support those properties then parsing will fail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-575) Definition/DeploymentExceptions thrown by an AnnotationModel are wrapped by a ComputationException

by Marius Bogoevici (JIRA)

Definition/DeploymentExceptions thrown by an AnnotationModel are wrapped by a ComputationException -------------------------------------------------------------------------------------------------- Key: WELD-575 URL: https://jira.jboss.org/browse/WELD-575 Project: Weld Issue Type: Feature Request Components: Reflection layer Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Assignee: Pete Muir Fix For: 1.1.0.BETA1 If an exception is thrown while evaluating a Function, the exception is wrapped by a ComputationException. As a result, the exceptions thrown by the AnnotationModel subclasses (Stereotype, InterceptionBinding) - which indicate a definition error detected while parsing the annotation are thrown as ComputationExceptions by the framework. An illustration for this can be found in MetaAnnotationStore.getInterceptionBindingModel, although this needs to be done in a more general fashion. -- 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

4
5
0 / 0

[JBoss JIRA] Created: (WELD-799) Weld throws java.lang.IllegalStateException: Context is not active during stress testing at higher number of clients

by Martin Gencur (JIRA)

Weld throws java.lang.IllegalStateException: Context is not active during stress testing at higher number of clients -------------------------------------------------------------------------------------------------------------------- Key: WELD-799 URL: https://issues.jboss.org/browse/WELD-799 Project: Weld Issue Type: Bug Components: Performance and Scalability Affects Versions: 1.1.0.CR1 Environment: JBossAS 6 CR1, Weld/trunk Reporter: Martin Gencur Fix For: 1.1.0.Final I executed performance stress test using Wicket for view layer and Weld-trunk. Everything goes well up to 2100 sessions. Then the following exception is thrown. I tried it twice and it failed at the same amount of sessions. Whole stack trace: 2010-12-17 03:03:57,840 WARN [org.apache.wicket.protocol.http.pagestore.FileChannelPool] (http-10.16.89.196-8080-304) Unable to reduce enough channels, no idle channels left to remove. 2010-12-17 03:03:57,842 WARN [org.apache.wicket.protocol.http.pagestore.FileChannelPool] (PageSavingThread-Wicket Filter) Unable to reduce enough channels, no idle channels left to remove. 2010-12-17 03:03:57,842 WARN [org.apache.wicket.protocol.http.pagestore.FileChannelPool] (PageSavingThread-Wicket Filter) Unable to reduce enough channels, no idle channels left to remove. 2010-12-17 03:03:58,499 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/seam-wicket-examples-numberguess-3.0.0-SNAPSHOT]] (http-10.16.89.196-8080-6) Exception sending request destroyed lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.IllegalStateException: Context is not active at org.jboss.weld.context.AbstractConversationContext.deactivate(AbstractConversationContext.java:263) [:2010-12-17 02:45] at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:125) [:2010-12-17 02:45] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:204) [:6.0.0.20101110-CR1] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.20101110-CR1] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.20101110-CR1] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.20101110-CR1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.20101110-CR1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.20101110-CR1] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.20101110-CR1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.20101110-CR1] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.20101110-CR1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.20101110-CR1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.20101110-CR1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [:6.0.0.20101110-CR1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.20101110-CR1] at java.lang.Thread.run(Thread.java:619) [:1.6.0_20] There is a new hudson job which tests this at http://hudson.qa.jboss.com/hudson/view/Weld/job/perf-seam-wicket-numbergu... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (WELD-809) NPE in ForwardingContextual.toString during session failover

by Sivakumar Thyagarajan (JIRA)

NPE in ForwardingContextual.toString during session failover ------------------------------------------------------------ Key: WELD-809 URL: https://issues.jboss.org/browse/WELD-809 Project: Weld Issue Type: Bug Reporter: Sivakumar Thyagarajan Please see the corresponding GlassFish issue for more information http://java.net/jira/browse/GLASSFISH-15277 GlassFish SQE has a multi-machine HA cluster setup, where during session failover of a shopping cart sample application, the following NPE is thrown is ForwardingContextual.toString java.lang.NullPointerException at org.jboss.weld.context.ForwardingContextual.toString(ForwardingContextual.java:53) at java.lang.String.valueOf(String.java:2826) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.jboss.weld.context.SerializableContextualInstanceImpl.toString(SerializableContextualInstanceImpl.java:66) at java.lang.String.valueOf(String.java:2826) at java.lang.StringBuilder.append(StringBuilder.java:115) at org.jboss.weld.context.beanstore.AttributeBeanStore.attach(AttributeBeanStore.java:120) at org.jboss.weld.context.AbstractBoundContext.activate(AbstractBoundContext.java:75) at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:138) at org.apache.catalina.core.StandardContext.fireRequestInitializedEvent(StandardContext.java:4544) at org.apache.catalina.core.StandardHostValve.preInvoke(StandardHostValve.java:626) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:323) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
5
0 / 0

[JBoss JIRA] Created: (WELD-851) Upgrade to findbugs-maven-plugin 2.3.2 when available

by Jozef Hartinger (JIRA)

Upgrade to findbugs-maven-plugin 2.3.2 when available ----------------------------------------------------- Key: WELD-851 URL: https://issues.jboss.org/browse/WELD-851 Project: Weld Issue Type: Task Components: Testing Infrastructure (Mocks and Harness Integration) Affects Versions: 1.1.0.Final Reporter: Jozef Hartinger Priority: Minor Upgrade to findbugs-maven-plugin 2.3.2 when available. Due to MFINDBUGS-122 it is not currently possible to run findbugs analysis. http://jira.codehaus.org/browse/MFINDBUGS-122 https://hudson.qa.jboss.com/hudson/view/Weld/job/Weld-trunk-findbugs/399/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (WELD-764) Instance appears to leak memory

by Pete Muir (JIRA)

Instance appears to leak memory ------------------------------- Key: WELD-764 URL: https://jira.jboss.org/browse/WELD-764 Project: Weld Issue Type: Bug Reporter: Pete Muir Fix For: 1.1.0.CR1 Nothing formal to confirm this, just a feeling from looking at a few problems -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-415) testApplicationScopeActiveDuringCallToEjbTimeoutMethod TCK test method is failing in Hudson

by Martin Gencur (JIRA)

testApplicationScopeActiveDuringCallToEjbTimeoutMethod TCK test method is failing in Hudson ------------------------------------------------------------------------------------------- Key: WELD-415 URL: https://jira.jboss.org/jira/browse/WELD-415 Project: Weld Issue Type: Bug Components: Testing Infrastructure (Mocks and Harness Integration) Affects Versions: 1.0.1.CR1 Reporter: Martin Gencur Assignee: Pete Muir Fix For: 1.0.1.CR2 Stack trace: java.lang.AssertionError at org.jboss.jsr299.tck.tests.context.application.ejb.EJBApplicationContextTest.testApplicationScopeActiveDuringCallToEjbTimeoutMethod(EJBApplicationContextTest.java:31) -- 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
5
0 / 0

[JBoss JIRA] Created: (WELD-823) Injection into Servlet not working in Jetty 6.x

by Dan Allen (JIRA)

Injection into Servlet not working in Jetty 6.x ----------------------------------------------- Key: WELD-823 URL: https://issues.jboss.org/browse/WELD-823 Project: Weld Issue Type: Bug Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.1.0.CR4 Reporter: Dan Allen Fix For: 1.1.0.Final Apparently the test suite does not test injection into Servlets for Jetty 6.x because users are reporting that it doesn't work. I added a Servlet injection into the numberguess example and was able to verify that the injection is not taking place, despite receiving the startup message: INFO: Jetty detected, JSR-299 injection will be available in Servlets and Filters. Injection into Listeners is not supported. If this turns out to be a user error, then we need to turn to a documentation improvement, because a guy like Antonio should not be having difficulty getting this to work. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2011