>
Initialization Options Reference

This refers to the properties which are made available to the spine framework at initialization. The properties defined in the spine-init.xml file contain all the initialization properties required by the framework as well as user defined properties.A brief explanation of some of these properties are give below:

logFile The path to the log4j configuration file which will determine the format for error messages.This can either be a java properties file or an xml file.
watchTime The refresh time in milliseconds to check the log4j file for changes.
configFile The path to the spine configuration file, usually spine.xml.
roleConfigFile The path to the default roles file. This may be replaced by a database or ldap backed plugin which loads all the registered Groups and Applications in the system.
DataSources
DataSource This must specify an attribute called [key] and an optional attribute called [default] which can be set to true or false. There should be only one default dataSource in the configuration, otherwise the last read default value is set for all the dataSources in configuration
DataSourceBuilder THe full class name of the DataSourceBuilder implementation which will be used to create and initialize this Datasource.
sourceClass The full class name of the DataSource class which will be initialized by the framework.
property This has 2 attributes called [name] and [value], you specify a property name and value which is then read by the system. You can specify as many property tags as needed.
plugins
plugin This must specify a single attribute called [key] which represents a unique name by which the plugin will be known throughout the application.
pluginName The full class name of the plugin to be used by this configuration.
property This has 2 attributes called [name] and [value], you specify a property name and value which is then read by the system. You can specify as many property tags as needed.

 
>
Configuration Options Reference

This is sometimes referred to as process flow configuration within spine. The configuration file spine.xml hosts this configuration and this file is read at initialization.A sample file is available  here with the various nodes and node details given below:

dataProxies

dataProxy The node which contains the attributes for the DataProxy i.e the full [className] and the [index]. You can define as many dataProxy tags as you need.
processor Has a single attribute called [name] which is the name by which this processor's configuration is known to the system
processorClass The full class name of the object which represents the processor to use.
delegate
The business delegate used by the business tier and its associated objects(this tag has no attributes). You may specify 1 to many Delegates.
subClass The full class name of the AbstractBusinessDelegate sub class in use by the process flow.
dataAccessObject The tag showing the DataAccessObjects and dependencies.
className The full class name of the DataAccessObject in use.
proxyIndex The index of the proxy subclass we are using for this process flow.
multiDelegate
The delegate used by the business tier and its associated objects(this tag has no attributes), use a multiDelegate tag when defining a MultiViewProcessor. You may specify 1 to many multiDelegates
subClass The full class name of the AbstractBusinessDelegate sub class in use by the process flow.
managedObject The tag indicating which object is used by this process flow, we advise using a SpineBean.
objectClass The full class name of the managed object in use by this process flow.
dataAccessObject The tag showing the DataAccessObjects and dependencies.
className The full class name of the DataAccessObject in use.
proxyIndex The index of the proxy subclass we are using for this process flow.
pageIndex An index used to specify this particular managed object configuration.
builder The full class name of a builder which can be used to invoke additional properties and/or functions for the various managed objects



<< Back    |     Home    |     Index    |     Forward >>

Copyright © 2008 Zphinx Software Solutions , all rights reserved