I think you can define the object that you need to make
available to all connected clients as a BlazeDS destination with
the application scope. Here is an example:
<destination id="SampleEmployeeRO">
<properties>
<source>samples.explorer.EmployeeManager</source>
<scope>application</scope>
</properties>
</destination>
Here is a link to the doc:
http://livedocs.adobe.com/blazeds/1/blazeds_devguide/help.html?content=rpc_config_2.html#260036The scope ... "Indicates whether the object is available in
the request scope, the application scope, or the session scope.
Objects in the request scope are stateless. Objects in the
application scope are available to the web application that
contains the object. Objects in the session scope are available to
the entire client session."
- Mykola
The valid values are request, application, and session. The
default value is request.