On Apr 9, 2010, at 12:26 PM, Ramesh Reddy wrote:
No, I am not saying to include this. If we can export CF, that is
one
way to share. Or user1 can go the deploy directory of the container to
grab the -ds.xml files.
Then I'm confused about the motivation behind the attempt to make VDBs more portable.
I thought the idea was to make it easy to move a VDB from one environment to another,
specifically thinking about promotion, like from dev to test to prod. If the CF names
generally match the model names, how would, say, a prod admin ever know the appropriate
connector to assign the CF to? If this info still has to be passed around verbally or via
some other exported entity, then why are we taking it out of the VDB in the first place?
Thanks,
JPAV