Problem with method action after migrating from TP2 to TP4

Question

Hi,
we are migrating our application (ADF Faces, ADF BC) from TP2 to TP4. We have encountered several problems.
The biggest that we could not solve is as following:
In our View Object's RowImpl.java classes we have method void refreshLOVAccessorQueries(). In a number of View Objects that method is placed in client interface. In pageDefs of jspx pages that are bound to that View Objects we have method action like
<methodAction IterBinding="TeeCronTtVOIterator"
id="refreshLOVAccessorQueriesCron"
InstanceName="bindings.TeeCronTtVOIterator.currentRow"
DataControl="TradingAppModuleDataControl"
RequiresUpdateModel="true" Action="invokeMethod"
MethodName="refreshLOVAccessorQueries"
IsViewObjectMethod="false" IsLocalObjectReference="true"/>
and invoke action like
<invokeAction id="refreshCronLOVs" Binds="refreshLOVAccessorQueriesCron"
Refresh="prepareModel"
RefreshCondition="#{!requestContext.postback and empty bindings.exceptionList}"/>
When we are accessing such a jspx page the application rases error:
"Method bindings.TeeCronTtVOIterator.currentRow.refreshLOVAccessorQueries() not supported "
In TP2 everything worked fine. Now in TP4 for some VO that refresh is OK and for others just mentioned error is thrown. Confusing is that all View Objects and their java classes are created in the same manner and they are almost identical, and this counts for pageDefs too.
What could be the reason of all this?
Second thing is that in adfc-config.xml in backing bean defs we have managed-property like:
<managed-bean>
<managed-bean-name>regionBacking</managed-bean-name>
<managed-bean-class>app.view.backing.RegionBacking</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>bindings</property-name>
<value>#{bindings}</value>
</managed-property>
</managed-bean>
JDeveloper warn us about that with: ' EL token bindings" is unknown '. Why is that? It looks that everything connected with that managed property works fine.
Another problem is not severe but unpleasant
After migration to TP4 nothing (not one element) is visible (shown) in the design view.
The structure of the pages is similar as in the StoreFrontDemo and it shows just fine in TP2.
Thanks!!!

Answer 1

Thanks Frank,
but working from beginning is to much work so, we have solved it in another way.
Regard to first problem we discovered that it is happening only when there is no Rows in iterator for which we are invoking action. In invoke action we have changed refresh property to default value and the problem is solved.
Second thing is warning that has no other effect so we will ignore it.
About third problem, when we create new working copy of application in JDeveloper without system11.1..... directory, JDev works fine and all jspx pages are shown in design view. After some work, due to undiscovered reason design view is lost... What could cause this?
Maxa