By default MOSS directs browser enabled InfoPath forms to the /_layouts/formserver.aspx page, with the query string parameters that define the form to display or edit. We have defined our own page (for a number of reasons) and would like to direct the forms in the form library there. The page can be hosted in that same _layouts folder, in a document library, it doesn't really matter.
There is a built-in IPFSSiteFeatures SharePoint Feature that contains the EcbEntry.xml file that contains custom actions to construct InfoPath form urls that use the /_layouts/formserver.aspx page. One idea we had was to create our own SharePoint Feature based on IPFSSiteFeatures that we can then associate with our own custom Form library (defined as a list definition). The problem is in identifying where that association occurs. There must be a link between the XML Form Library (maybe the content type?) and the IPFSSiteFeatures Feature that causes the Form Library to use the custom actions defined in IPFSSiteFeatures.
Alternative approaches are welcomed...
Thanks!