FAQ

This page tries to compile the most asked questions and to answer as directly as possible.

If your question is not listed please fill a bug report / feature request here.

As any good answer, this one starts with "it depends" :)

Each storage options targets its own applications with specific (and different) requirements and characteristics. Thus, using either OJB or XML has impact on how BERSERK fulfills application's requisits.

OJB is a much more complete storage mechanism. It has great extensibility and time complexity is way smaller than XML's. This means that for many filters, services and filter chains OJB has a smaller configuration reading overhead that XML.

On the other hand XML is easier to use and has better portability, since it needs no DBMS to store BERSERK's components configurations. It's time-to-run is way smaller, because the filters, services and filter chains configurations are stored on regular files on the OS native file system.

When running BERSERK on a managed environment (as Tomcat, JBoss, etc...), it may be easier to use OJB if you want to make runtime changes to service, filters and filter chain configurations, since manipulating files in a managed evironment can introduce aditional complexity (for example with file paths).

The conclusion is:

Use XML for quick developing (and portability) and OJB for wider possibilities and better scalability.