[
https://issues.jboss.org/browse/WFLY-1995?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-1995:
----------------------------------------
Why is this for "some" EJB annotations?
We went through a lot of pain around this with the server config, with expressions
supported on "some" elements but not others. It was a mess as there was no clear
logic for why it was supported. We ended up supporting them everywhere unless there was a
clear reason why doing so was wrong/
IMO this should only be supported if it can supported consistently for all annotations,
with an understandable rationale for why it's not supported for any cases where it
isn't.
The configuration should be consistent with whatever we do to enable/disable expression
support in the deployment descriptor parsers.
Allow property substitution in EJB Annotations
@ActivationConfigProperty and @ResourceAdapter with configurable option
----------------------------------------------------------------------------------------------------------------------
Key: WFLY-1995
URL:
https://issues.jboss.org/browse/WFLY-1995
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: EJB
Reporter: Carlo de Wolf
Assignee: Chao Wang
Create a configuration option which enables property substitution in EJB annotations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira