Deployer Extensions with Eclipse - Step 8: Other considerations and tips
You completed the tutorial. Now you will be able to write your modules and start extending the deployer based on your needs.
Other deployer extension points
In this tutorial you learned how to add your custom module to your deployer. But every class in the cd_deployer_conf.xml can be extended or overwritten, meaning that you can modify or extend the behavior of the BinaryDeploy module for example, by replacing the default module with a module you wrote your self and that extends the com.tridion.deployer.BinaryDeploy class in this case.
In the same way you can overwrite the Processors, both for deployment and undeployment. You can also remove certain functionality by bypassing the process method or skipping certain actions within the default deployment process.
Considerations and tips
- Basically every class defined in the cd_deployer_conf.xml can be extended/replaced
- Once you are done with the implementation, generate a jar file with your code and add it to the deployer classpath
- Be aware that once the process method is called, the package is unavailable
- Note that the processors can be executed in pre/post transaction mode (hotfix available)
- If something goes wrong in your extension, throw a ProcessingException, so the deployer knows that the deployment must be considered as failed
- Read the deployer API documentation
Customizing the custom deployer
Developing a custom processor
Creating a custom module