|Home > Guides > Core Developers Guide > ObjectFactory|
All objects created by the framework are instantiated by the ObjectFactory. The ObjectFactory provides the means of integrating the framework with IoC containers like Spring, Pico, Plexus, and so forth.
Customized ObjectFactory must extend ObjectFactory or any of its descendants and have a default, no-argument constructor.
To register a customized ObjectFactory, add or edit an entry in
where foo.bar.MyCustomObjectFactory is the custom object factory.
If you want to just extend one part of ObjectFactory, ie. to change how Result Types are build, you can implement
ResultFactory interface and register it with dedicated name, see Extension Points for more details. Original ObjectFactory will use these dedicated factories to do the work. It's already done this way - the original functionality of ObjectFactory was extracted to separated classes which implements the interfaces below. Check the source of ObjectFactory to see more details. All these factories are available as from version 2.3.16.
List of Factory interfaces:
ResultFactory- dedicated interfaces used by ObjectFactory to create Result Types
StrutsResultFactoryit's internal implementation which checks if Result implements
ParamNameAwareResultinterface to restrict names of parameters set on the instance of Result, see Result Types for more info.
ActionFactory- dedicated interface used by ObjectFactory to actions
InterceptorFactory- dedicated interface used by ObjectFactory to create interceptors
ValidatorFactory- dedicated interface used by ObjectFactory to create validators
ConverterFactory- dedicated interface used by ObjectFactory to create instances of TypeConverter
UnknownHandlerFactory- dedicated interfaces used by ObjectFactory to create instances of Unknown Handlers (as from version 2.3.18)