July 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-538) Unsatisfied dependency in interceptor still checked for serialization, resulting in NPE

by Nicklas Karlsson (JIRA)

Unsatisfied dependency in interceptor still checked for serialization, resulting in NPE --------------------------------------------------------------------------------------- Key: WELD-538 URL: https://jira.jboss.org/browse/WELD-538 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Given a serializable interceptor with a @Inject Logger log but no producer for it you get a java.lang.NullPointerException at org.jboss.weld.util.Beans.isPassivationCapableDependency(Beans.java:175) at org.jboss.weld.bootstrap.Validator.validateInjectionPointPassivationCapable(Validator.java:335) at org.jboss.weld.bootstrap.Validator.validateCdiBoundInterceptors(Validator.java:224) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:170) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:363) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:349) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:402) at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.boot(BootstrapBean.java:121) [:6.0.0-SNAPSHOT] because it checks for passivation on a null-resolved bean -- 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

2
5
0 / 0

[JBoss JIRA] Created: (WELD-549) Conversation propagated by default with h:link

by David Beaumont (JIRA)

Conversation propagated by default with h:link ---------------------------------------------- Key: WELD-549 URL: https://jira.jboss.org/browse/WELD-549 Project: Weld Issue Type: Bug Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.1.Final Environment: GlassFish Server Open Source Edition 3.0.1 on Mac OS 10.6 and Windows 7. WELD-000900 1.0.1 (SP2) Reporter: David Beaumont Attachments: CdiConvoBug.war I created a long running conversation by running a method on a conversation scoped bean: private boolean initialized; public void init() { if(initialized) return; conversation.begin(); initialized = true; } >From a facelets page using the JSF2 event system: <f:metadata> <f:event type="preRenderView" listener="#{convoBean.init}" /> </f:metadata> If a conversation has been made long-running, the h:link tag will produce links with the conversation query parameter, thereby propagating the conversation whether that was what you wanted or not. I.e: <p>Link: <h:link outcome="page2.xhtml" value="a link" /></p> produces <p>Link: <a href="/CdiConvoBug/page2.jsf?cid=3">a link</a></p> -- 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
26
0 / 0

[JBoss JIRA] Created: (WELD-479) Detect circular dependencies in @Dependant scoped beans

by Stuart Douglas (JIRA)

Detect circular dependencies in @Dependant scoped beans ------------------------------------------------------- Key: WELD-479 URL: https://jira.jboss.org/jira/browse/WELD-479 Project: Weld Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas According to 5.4: "Beans with scope @Dependent never have circular dependencies", we should detect this at deployment time and throw an error. -- 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
12
0 / 0

[JBoss JIRA] Created: (WELD-364) Remote EJB methods should be able to observe

by Nicklas Karlsson (JIRA)

Remote EJB methods should be able to observe -------------------------------------------- Key: WELD-364 URL: https://jira.jboss.org/jira/browse/WELD-364 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Fix For: 1.0.1.CR1 Unneccessary restriction is currently present -- 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
9
0 / 0

[JBoss JIRA] Created: (WELD-469) Exception in normal mode for incompletly annotated custom scopes.

by Wolfgang Frech (JIRA)

Exception in normal mode for incompletly annotated custom scopes. ----------------------------------------------------------------- Key: WELD-469 URL: https://jira.jboss.org/jira/browse/WELD-469 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: n/a Reporter: Wolfgang Frech If a custom scope is incomplete, say without the target annotation for field and type, but without method, Weld now - logs a warning - uses the context for that scope - marks the scope as invalid - returns only Java, not ClientProxy refs for Beans. According to the spec,the container must detect the missing annotation. It should not complete the initialization. In addition to that behavior, it may treat it on a best-effort basis, but only in development mode. In normal mode, the container should throw an exception that cannot be missed. -- 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
11
0 / 0

[JBoss JIRA] Created: (WELD-558) Performance Problem while using ApplicationScoped and/or SessionScoped Component in RequestScoped Bean

by Markus Weiss (JIRA)

Performance Problem while using ApplicationScoped and/or SessionScoped Component in RequestScoped Bean ------------------------------------------------------------------------------------------------------ Key: WELD-558 URL: https://jira.jboss.org/browse/WELD-558 Project: Weld Issue Type: Bug Components: Scopes & Contexts Affects Versions: 1.0.1.Final Environment: Windows XP 32bit / Ubuntu 10.04 GlassFish Server Open Source Edition 3.0.1 (build 22) WELD-000900 1.0.1 (SP3) Reporter: Markus Weiss If I inject a SessionScoped or ApplicationScoped base class in a RequestScoped ManagedBean and make heave use of the injected resources the page load time increases every time I reload the page. I can provide an example project which reproduces this performance problem. -- 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
13
0 / 0

[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-206) Tests for OSGi bundle to ensure the correct bundle headers are generated

by Pete Muir (JIRA)

Tests for OSGi bundle to ensure the correct bundle headers are generated ------------------------------------------------------------------------ Key: WELD-206 URL: https://jira.jboss.org/jira/browse/WELD-206 Project: Weld Issue Type: Task Reporter: Pete Muir Assignee: Roger Kitain Priority: Critical 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

13 years, 5 months

1
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2010