JDeveloper 10.1.2.0(build 1811): DataAction problem in struts-config

Question

I've created several data pages (with JHeadstart). With data of one of those pages I must do some calculation and then display the results in another page. I create an DataAction in which I dropped the method that does the calculation. JDeveloper created an UIModel.xml for the DataAction but I had to set the values of the parameters in struts (property inspector). No java file involved. Then I created the Forwards to and from my DataAction. Everything worked nice. So I saved the struts-config.xml and checked it in into PVCS Version Manager. The next day I took all the files of my project from VM and run JHS again. Strut-config is not overwritten, but updated; it looked OK. However when I tested the flow from the first page to the other, the method is not executed but the second page is displayed.
If I drop the method again in the data action (and set all parameters and the resultlocation to the proper values) everything is working again. It can't be that this again dropping of a method is the way we should work with struts containing data actions!
The[b] problem is not that the data action has changed into an icon of a datapage with a yellow exclamation mark icon (Re: 10.1.2 Struts Bug? in fact nothing is changed at all. The problem is that the method is not executed.
The dataAction in the struts_config source - as it was before I checked it in into VM and after checking out:
<action path="/invokeCalcDownTree" className="oracle.adf.controller.struts.actions.DataActionMapping" type="oracle.adf.controller.struts.actions.DataAction" name="DataForm">
<set-property property="modelReference" value="invokeCalcDownTreeUIModel"/>
<set-property property="methodName" value="invokeCalcDownTreeUIModel.calculateDownstreamTree"/>
<set-property property="resultLocation" value="${sessionScope.currentDownTraceId}"/>
<set-property property="numParams" value="6"/>
<set-property property="paramNames[0]" value="${data.TT_DownstreamUIModel.TT_DownstreamId}"/>
<set-property property="paramNames[1]" value="${data.TT_DownstreamUIModel.TT_DownstreamProductiepartij}"/>
<set-property property="paramNames[2]" value="J"/>
<set-property property="paramNames[3]" value="1"/>
<set-property property="paramNames[4]" value="RO"/>
<set-property property="paramNames[5]" value="-1"/>
<forward name="success" path="/StartTT_DownTree.do"/>
</action>
Kind regards,
Josée Vervaart
ICT Solutions, Deventer

Answer 1

The problem was not Version Manager itself but working with Version Manager:
our policy is only check-in those which are not generate by JHS and those which are customized in JDeveloper (not anymore generated) i.e. check-in the business components, view objects, application structure and a few UNIX's and UIModel-files etc.
I had to do the first modification in the struts-config: adding a DataAction.
I checked in the UIX's and UIModel-files of the calling and called page, the UIModel of the DataAction, the struts-config.xml, and later on also the StrutsPageFlow.oxd_struts and modelers.map. Today we saw that the databindings.cpx file must be checked in too.