Darn - email problems. I accidently deleted the message I wanted to reply to.
Anyway, saveUserCopletInstance is the method I really care about. I don't think anything was ever actually calling the other save methods. When I added support for storing JSR-168 Portlet preferences I added code to cause just the coplet instance data to be saved, as that is where the portlet preferences reside. I don't want to save the layout as well since, in a lot of cases, the user may not even be able to change his layout and it will end up creating a slew of duplicated files.
Ah, ok - this way makes sense of course. Ok, so I think we should go with the two methods: saveUserLayout and saveUserCopletInstances and implement them accordingly.
If you're ok with it, I can fix it tomorrow.
Carsten
As for the other two methods, I tried to leave saveUserProfiles as I found it in terms of functionality - it did the same thing saveUserLayout is doing now, but accomplished it by calling saveUserLayout and saveUserCopletInstance.
Ralph
