]
Lin Gao moved JBEAP-12512 to WFLY-9168:
---------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9168 (was: JBEAP-12512)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
Security
(was: EJB)
(was: Security)
Affects Version/s: (was: 7.1.0.ER3)
Log error org.jboss.security.annotation.SecurityDomain annotation is
used in EJB
--------------------------------------------------------------------------------
Key: WFLY-9168
URL:
https://issues.jboss.org/browse/WFLY-9168
Project: WildFly
Issue Type: Bug
Components: EJB, Security
Reporter: Lin Gao
Assignee: Lin Gao
Priority: Critical
Original Estimate: 2 days
Remaining Estimate: 2 days
The annotation *{{org.jboss.security.annotation.SecurityDomain}}* is present in the
legacy security packages and documented in 7.1
[
Javadoc|https://access.redhat.com/webassets/avalon/d/red-hat-jboss-enterp...]:
{quote}
Annotation for specifying the JBoss security domain for EJBs.
{quote}
Nevertheless this annotation doesn't work and the one from another package has to be
used instead - {{org.jboss.ejb3.annotation.SecurityDomain}}.
Server doesn't log an error or warning when the legacy one is used.
*Suggested fix:*
Add a deployment processor which will log error when the legacy annotation is used in the
deployment.
Another possibility how to fix this would be to add support for the legacy annotation
too.
I'll create a separate JIRA for JavaDoc update in the legacy annotation class.