|
berserk.properties
BERSERK configuration file is called berserk.properties and it must
be in the application’s classpath to be successfully read.
BERSERK offers runtime configuration capabilities using
BerserkConfiguration class. By using the BerserkConfiguration class, developers
can specify all options available on the configuration file.
configuration options
The following table shows the available options when using berserk.
Some options can reflect user developed solutions, as explained in the How To
section.
|
Property
|
Mandatory
|
Allowed Values
|
Default Value
|
|
storageBroker
|
always
|
class name
|
StorageBrokerDigester
|
|
berserk.databaseName
|
using OJB
|
string
|
BERSERK_OJB
|
|
berserk.filterDefinitions
|
using Digester
|
file path
|
/fd.xml
|
|
berserk.serviceDefinitions
|
using Digester
|
file path
|
/sd.xml
|
|
berserk.filterChainsDefinitions
|
using Digester
|
file path
|
/fcd.xml
|
|
berserk.transactionManager
|
always
|
class name
|
TransactionBrokerEmpty
|
|
application.transactionManager
|
always
|
class name
|
TransactionBrokerEmpty
|
In order to improve table readability, only the class name is written. When
configuring BERSERK, full qualified classes’ name must be used.
pt.ist.utl.berserk.storage.ojb must precede table values to allow BERSERK to
work properly.
options
To better understand the significance of each configuration possibility, a
brief description follows:
-
storageBroker - the class specified in this field
will handle filters, services and filter chains definitions readings.
-
berserk.databaseName - when using OJB this field must
have the name specified in the database descriptor (parameter jcd-alias).
-
berserk.filterDefinitions
- when using Digester this field must be a string representing the file
unix-like path pointing to the file containing filter configurations. A heading
slash (‘/’) must be provided, representing the root of the class path location.
The file is search in application’s class path-
-
berserk.serviceDefinitions
- when using Digester this filed must be a string representing the file
unix-like path pointing to the file containing services configurations. A
heading slash (‘/’) must be provided, representing the root of the class path
location. The file is search in application’s class path.
-
berserk.filterChainsDefinitions - when using Digester
this field must be a string representing the unix-like file path pointing to
the file containing filter chains configurations. A heading slash (‘/’) must be
provided, representing the root of the class path location. The file is search
in application’s class path.
-
berserk.transactionManager
- the class specified in this field will be responsible to assure a
transactional environment to BERSERK storage operations.
-
application.transactionManager - the class specified in this
field will be responsible to assure a transactional environment to application
storage operations.
|
