[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-3848:
-----------------------------------
{quote}
Could you please let us know how did you verify with some sample program..thanks
{quote}
You don't have to do anything. Just deploy the @Clustered beans on the server side and
invoke them from a client. Here's one example of the client invoking on remote beans
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+....
That example isn't specific to @Clustered beans though.
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL:
https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: eap6_LA, failover_testing
Fix For: 7.1.1.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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