When we decide to include DiF's default stages in our project several features are available.
A list of these follows:
These are fully implemented and functional and can be used in conjunction with our own application stages.
Many times we may want to customize some of the default stages DiF provides.
We may want to change them a bit, either by extending the original class and adding what we need, or complexly replacing the default stage by our own.
This is accomplished by defining a new stage with the same ID that the default one. And adding the parameter "overrideDefault" to the @StageDefinition annotation.
Bellow is an example of such replacement.
TODO: Add code sample here
This can be done for any of the previous listed default stages and thus allow us to completely customized DiF's default features.
Some special stages deserves special attention.
The default DiF Template stage, the "diftemplate".\
All DiF default pages use this default template. If we want to use all default DiF stages and their functionality, but still wan't them to comply to our specific customized page style, or template, all we need to do is override only this template stage, and all default stages will reflect the new template.
This is the most common use of stage overriding.
The default Home stage, is a DiF administration dashboard. As such we will normally not want it has the default home stage and instead have a customized user oriented home page.
Nevertheless this default stage is handy for administration purposes, and has such stage overriding is not what we want to do (since it would make it impossible to access the default stage.
For this, DiF allows that we state with is the stage we should consider our home stage. This can be any existing stage, we need only to provide it's ID. This will force all DiF interfaces to use the new stage ID and the default home stage, but maintain this stage available for we to link it wherever we wish to.
You can see how to do this in the Configuration section.