[
https://issues.jboss.org/browse/WFLY-6197?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated WFLY-6197:
-------------------------------
Description: The default singleton policy happens to be named "default" in
our default configuration. However, the EJB subsystem should not rely on this - as a user
can change this. Part of the problem is, there is no registered capability that
specifically refers to the default singleton policy. (was: The default singleton policy
happens to be named "default" in our default configuration. However, the EJB
subsystem should not rely on this. Part of the problem is, there is no registered
capability that specifically refers to the default singleton policy.)
@ClusteredSingleton is hardcoded to use a specific singleton policy
name
------------------------------------------------------------------------
Key: WFLY-6197
URL:
https://issues.jboss.org/browse/WFLY-6197
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 10.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 10.1.0.Final
The default singleton policy happens to be named "default" in our default
configuration. However, the EJB subsystem should not rely on this - as a user can change
this. Part of the problem is, there is no registered capability that specifically refers
to the default singleton policy.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)