Created a new ECMA2 for a web service. In the code, I set the Microsoft.MetadirectoryServices.SchemaType to "Person" (with uppercase P) to match the Web Service's object type. As a result, the connector space object would not join to the metaverse object "person".
Symptoms: When generating a preview, the "Provisioning Summary" and Connector Updates" items did not appear in the Contents menu of the Preview dialog for any object in the Connector Space. Even when manually joined, the object would not try to execute an import flow rule (direct or extended). After hours scratching my head, I finally noticed the case difference of the object, recompiled the ECMA2, reloaded the interfaces, and that sorted it out. Sigh.
Yet another item to support my thesis, "The only thing case-sensitivity does is cause stuff to break".