We’re looking to extend Tridion’s content storage layer with a new storage type to allow us to write some of our component presentations into a RavenDB repository. As part of this, we also want to continue storing all of those component presentations in our Broker Database.
Is it possible to configure Tridion’s deployer to send one ItemType to multiple storage types? The documentation and posts I have found on extending the storage layer (such as Julian Wrath’s post 'HowTo: Extending Content Broker Storage') do not seem to address this situation.
For instance, assuming valid definitions of defaultdb and defaultFile would the following result in published component presentations being sent to both storage types?
<Item typeMapping="ComponentPresentation" cached="false" storageId="defaultdb"/> <Item typeMapping="ComponentPresentation" cached="false" storageId="defaultFile"/>