Observer method resolution ignores type parameters
--------------------------------------------------
Key: WBRI-136
URL: https://jira.jboss.org/jira/browse/WBRI-136
Project: Web Beans RI
Issue Type: Bug
Affects Versions: 1.0.0.ALPHA2
Reporter: David Allen
Assignee: David Allen
Priority: Minor
Section 7.7 of the PRD2 specification states: When searching for observers for an event, the container searches for observers which satisfy the following rules:
• the event object must be assignable to the observed event type, taking type parameters into consideration, and ...
Currently resolution works only for the event type information, regardless of any specific type parameters.
The test for this assertion is in org.jboss.jsr299.tck.unit.event.EventTest.testResolvingChecksTypeParameters().
--
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
Support specializing producer methods on enterprise beans
---------------------------------------------------------
Key: WBRI-116
URL: https://jira.jboss.org/jira/browse/WBRI-116
Project: Web Beans RI
Issue Type: Feature Request
Reporter: Pete Muir
Assignee: Pete Muir
Fix For: 1.0.0.BETA1
Deferring for now, as really we need a "better" bean deployer to support this (one that order bean creation so that the specialized bean is created and available for the specializing bean to use).
This intersects with XML deployment.
--
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
isProxyable should be available on AnnotatedClass
-------------------------------------------------
Key: WBRI-108
URL: https://jira.jboss.org/jira/browse/WBRI-108
Project: Web Beans RI
Issue Type: Feature Request
Reporter: David Allen
There should be a method isProxyable for AnnotatedClass that returns whether or not the class is proxyable. Either the check can be moved to that location, or the result can at least be cached there. It would be more efficient if the checks were done there since the reflected metadata is already available in that class.
--
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
automatic conversation propagation for jsf postbacks broken in chrome
----------------------------------------------------------------------
Key: WBRI-138
URL: https://jira.jboss.org/jira/browse/WBRI-138
Project: Web Beans RI
Issue Type: Bug
Affects Versions: 1.0.0.ALPHA2
Reporter: Nicklas Karlsson
Assignee: Nicklas Karlsson
Priority: Minor
This page contains the following errors:
error on line 1 at column 28: Extra content at the end of the document
--
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