Re: [jboss-as7-dev] EJB Remote client design
On Thursday 15 September 2011 09:20 AM, David M. Lloyd wrote:
Client API
----------
...
Each EJB receiver has an obligation to keep the EJB client context
updated with the list of module identities that it can access. When a
proxy is invoked upon, the EJB client context uses this table to select
the destination. This means that for the Remoting protocol for example,
the server sends back messages informing the client of changes in
deployment status (which should be relatively infrequent) as well as
sending an initial summary of what modules are available.
I'm not too sure the EJB app repository is going to be very useful. A
server might host numerous EJBs across different applications (1000s
maybe) and the client(s) might just be interested in just 1 or a few of
those EJBs. Furthermore, the clients are interested only in the remote
views exposed by the EJB. Beans that do not expose any remote view are
of no use in the EJB app repository. Sending down the repository of a
large number of EJBs (even though it's just identifiers) to each client,
when the client isn't really interested in most of those, looks like an
overhead.
-Jaikiran