JBoss.orgCommunity Documentation

Chapter 10. Bus Configuration

10.1. web.xml and appserver configuration
10.2. ErraiService.properties
10.2.1. errai.dispatcher.implementation
10.2.2. errai.async_thread_pool_size
10.2.3. errai.async.worker_timeout
10.2.4. errai.authentication_adapter
10.2.5. errai.require_authentication_for_all
10.2.6. errai.auto_discover_services
10.2.7. errai.auto_load_extensions
10.3. ErraiApp.properties

This section contains information on configuring the server-side bus.

Depending on what application server you are deploying on, you must provide an appropriate servlet implementation if you wish to use true, asynchronous I/O. See _section 6.5 _ for information on the available servlet implementations.

Here's a sample web.xml file:

he ErraiService.properties file contains basic configuration for the bus itself.

Example Configuration:

The ErraiApp.properties acts as a marker file. When it is detected inside a JAR or at the top of any classpath, the subdirectories are scanned for deployable components. As such, all Errai application modules in a project should contain an ErraiApp.properties at the root of all classpaths that you wish to be scanned.

The file can also include explicitly declared serializable types (such as those from third-party code) that cannot be annotated for serialization. (See the section on serialization for more details)

errai.bus.serializableTypesDefines a list of serializable types to expose to the bus.