public interface PropertyContainerUpdater
initFinder(AppContext, PropertyFinder, String) method should always be called before any other methods from this interface.
While it would be cleaner to initialise the object within the constructor this process may need information about
the higher stages of the call chain.| Modifier and Type | Method and Description |
|---|---|
java.lang.String |
endParse()
End a batch parse this de-allocates any temporary storage and
and perform any final operations.
|
PropExpressionMap |
getDerivedProperties(PropExpressionMap previous)
return a set of derived property definitions.
|
PropertyFinder |
initFinder(uk.ac.ed.epcc.webapp.AppContext ctx,
PropertyFinder prev,
java.lang.String table)
Generate a PropertyFinder that will find any PropertyTag generated by this class.
|
uk.ac.ed.epcc.webapp.jdbc.table.TableSpecification |
modifyDefaultTableSpecification(uk.ac.ed.epcc.webapp.AppContext conn,
uk.ac.ed.epcc.webapp.jdbc.table.TableSpecification t,
java.lang.String table_name)
Modify the default table specification if appropriate
A null specification denotes that a table should not be auto-created.
|
void |
startParse(PropertyContainer static_props)
Start a batch parse.
|
PropertyFinder initFinder(uk.ac.ed.epcc.webapp.AppContext ctx, PropertyFinder prev, java.lang.String table)
All properties defined at run-time should have their PropertyTag objects constructed by the time the first call to this method returns. As some parsers properties will generate different things depending on the other properties already in scope this method is passed a PropertyFinder for any properties that may already be in scope. This will include any default parameters specified when the data was uploaded and any properties generated from the database meta-data. Though it is perfectly legal to return a PropertyFinder that returns a superset of the generated properties the only requirement is that the returned finder can find any property that this classes parse method may actually generate values for. So Normally the contents of the super-finder are not included in the result unless these values are actually generated by the parse. If values are generated then a MultiFinder can be populated with the PropertyRegistrys from the generated properties
ctx - prev - PropertyFinder for the higher levels in the call chain.table - String name of the destination table in case per-table customisation is neededPropExpressionMap getDerivedProperties(PropExpressionMap previous)
Definitions are allowed for properties that are also generated directly in the parse phase. In this case the parse value should always be used by preference and the derived definition only provides a fall-back implementation if the parse value is unavailable. For example if not persisted in the database layer. This allows one parser/policy to specify a default implementation as a derived property definition which is then overridden by having the same property generated in a parse method of a different policy/parser
previous - Previous definitionsvoid startParse(PropertyContainer static_props) throws java.lang.Exception
java.lang.Exceptionstatic_props - properties constant for this accounting run.java.lang.String endParse()
uk.ac.ed.epcc.webapp.jdbc.table.TableSpecification modifyDefaultTableSpecification(uk.ac.ed.epcc.webapp.AppContext conn,
uk.ac.ed.epcc.webapp.jdbc.table.TableSpecification t,
java.lang.String table_name)
conn - AppContextt - TableSpecification or nulltable_name -