Okay, so I want to use the default XML sitemap for a portion of a site, but I also want part of it generated dynamcially and data-driven. The complication? As far as I can tell, you can have a second SiteMap act as a starting point for a brand new node tree, but I want to have it generate multiple branches. E.g.
This is how I think the SiteMap system works.
______________
| XmlDrivenRoot |
/ \
/ \
_________ ______________
| XmlNode | | DataDrivenRoot |
/ \
/ \
_________ _________
| DataNode | | DataNode |
...but here's how I actually want it to work...
______________
| XmlDrivenRoot |
/ | \
/ | \
_________ _________ _________
| XmlNode | | DataNode | | DataNode |
...where I use the default XmlSiteMapProvider, but have a bunch of branches generated off the root node via my custom SiteMapProvider.
Is it possible to have this arrangement without a hack? I'm considering reverting to a third composite provider which manually combines the XML and my custom nodes, but I'm hoping I can accomplish what I want without resorting to such trickery.
Does anyone know if the above is possible?