In my service composite that uses a File Adapter (write), I'm specifying a Logical Directory only at design time and then I'm populating the Physical directory to write to by editing the reference's properties post composite deployment. This is a very effective and logical use of SCA reference properties.
My problem is that when I deploy an update of the composite (say v1.2, v1.3, ...) it is blowing away the property value that I had previously set on that reference. Of course -- with Administrator hat on -- I forget to redefine that Physical location property EVERY TIME and thus my first instances always Fault after deploying a new version.
Is this expected behavior for configured values to not survive. Is there a recommended process/pattern here?