Preventing reflection misuse
----------------------------
Key: WELD-361
URL: https://jira.jboss.org/jira/browse/WELD-361
Project: Weld
Issue Type: Bug
Components: Reflection layer
Affects Versions: 1.0.0.GA
Reporter: Nicklas Karlsson
Assignee: Nicklas Karlsson
Fix For: 1.0.1.CR1
Prevent misuse of Weld reflection privilege elevation (either through using reflection util classes directly or through other API/SPI)
--
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
IllegalStateException not thrown when a delegate method is invoked outside of business method invocation
--------------------------------------------------------------------------------------------------------
Key: WELD-430
URL: https://jira.jboss.org/jira/browse/WELD-430
Project: Weld
Issue Type: Bug
Components: Interceptors and Decorators
Affects Versions: 1.0.1.CR2
Reporter: Jozef Hartinger
Fix For: 1.0.1.GA
org.jboss.jsr299.tck.tests.decorators.invocation.DecoratorInvocationTest.testDecoratorInvokesDelegateMethodOutsideOfBusinessMethodInterception()
--
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 serialization of the metamodel
--------------------------------------
Key: WELD-210
URL: https://jira.jboss.org/jira/browse/WELD-210
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Reporter: Pete Muir
This would allow us to do stuff like build the metamodel at compile time (time saver?) or work in environments like GWT where the reflection support is limited
--
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
Create clustering (functional) tests from Seam examples
-------------------------------------------------------
Key: WELD-266
URL: https://jira.jboss.org/jira/browse/WELD-266
Project: Weld
Issue Type: Feature Request
Reporter: Pete Muir
Assignee: Ondrej Skutka
Create functional tests from examples such as Weld numberguess and Seam 3 booking which verify that Weld performs correctly in a cluster.
--
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
Interceptor for lifecycle callback with binding type @Target({TYPE, METHOD}) not detected as definition error
-------------------------------------------------------------------------------------------------------------
Key: WELD-458
URL: https://jira.jboss.org/jira/browse/WELD-458
Project: Weld
Issue Type: Bug
Components: Interceptors and Decorators
Affects Versions: 1.0.1.Final
Reporter: Ondrej Skutka
Spec says:
An interceptor for lifecycle callbacks may only declare interceptor binding types that are defined as @Target(TYPE). If an
interceptor for lifecycle callbacks declares an interceptor binding type that is defined @Target({TYPE, METHOD}), the con-
tainer automatically detects the problem and treats it as a definition error.
org.jboss.jsr299.tck.tests.interceptors.definition.broken.interceptorForLifecycleTargetMethod.InterceptorForLifecycleTargetMethodTest
In the TCK trunk
--
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 EEJB environment in harness
-----------------------------------
Key: CDITCK-51
URL: https://jira.jboss.org/jira/browse/CDITCK-51
Project: CDI TCK
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Infrastructure
Affects Versions: 1.0.0.GA
Reporter: Pete Muir
Fix For: 1.1.0.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
Investigate using dependency:copy-dependencies rather than dependency:copy as it looks in the reactor
-----------------------------------------------------------------------------------------------------
Key: CDITCK-42
URL: https://jira.jboss.org/jira/browse/CDITCK-42
Project: CDI TCK
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Infrastructure
Reporter: Pete Muir
Fix For: 1.0.0.CR3
--
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
It is not possible to add identical beans through BeforeBeanDiscovery.addAnnotatedType
--------------------------------------------------------------------------------------
Key: WELD-413
URL: https://jira.jboss.org/jira/browse/WELD-413
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.1.CR1
Reporter: Stuart Douglas
Priority: Minor
Adding a bean that is exactly the same as an existing bean results in the added bean being ignored.
I can't think of a use case for having two beans exactly the same, however it still should work, and may be a symptom of a larger problem.
--
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