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