[
https://issues.jboss.org/browse/AS7-2887?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-2887:
---------------------------------------
Re: "MDB - Give a "feature unsupported" error, refuse to deploy"
@Clustered on an MDB has never been a feature and AFAIK never will be a feature. I'm
not sure what it would mean. We've never failed a deployment on it though, any more
than we fail a deployment due to the presence of some other annotation that isn't
understood.
I don't feel strongly about this (at all), as I can see the benefits of consistency in
how we treat this annotation.
Disallow deployment of @Clustered EJBs if the type is not valid
---------------------------------------------------------------
Key: AS7-2887
URL:
https://issues.jboss.org/browse/AS7-2887
Project: Application Server 7
Issue Type: Task
Components: Clustering, EJB
Reporter: David Lloyd
Priority: Blocker
Fix For: 7.1.0.CR1
@Clustered can be applied as follows:
* Entity EJB - Give a "feature unsupported" error, refuse to deploy
* Stateful Session EJB - Allow
* Stateless Session EJB - Allow (has no effect though)
* Singleton EJB - Give a "feature unsupported" error, refuse to deploy
* MDB - Give a "feature unsupported" error, refuse to deploy
Note that "feature unsupported" should be worded such that the feature may
become available in future releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira