A few ADF BC state passivation/activation problems

Question

Our development team has encountered and researched a few ADF BC passivation/activation related bugs that are very annoying. Some of them have been fixed in the new JDeveloper 11gR1 (11.1.1.1.0) but other ones are still active in the last production release. As we consider some of these bugs as very important we decided to report them in this forum:
*1) New (modified) values of read-only SQL-derived or transient attributes are not activated if they have been modified in ViewObject's cache and the corresponding changes have not been posted to DB yet*
The attribute values are included into the passivated state but the activation process does not try to activate a modified value if the method <tt>ViewRowImpl.isAttributeUpdateable(int)</tt> returns <tt>false</tt> for the corresponding row attribute. There are many business cases when some ViewObject attributes have to be modified despite the fact they are read-only (or conditionally read-only depending on the values of another attributes).
*2) Transient values (values of SQL-derived or transient attributes) that have been modified in ViewObject's cache to <tt>null</tt> are not cleared on state activation*
This is true even for updateable attributes. The problem exists because the passivation process does not write into the passivated state anything about attributes having <tt>null</tt> values. As a consequence the activation process does not try to modify values of the corresponding attributes during the activation and they keep the value fetched from the ViewObject's query.
*3) State activation process does not restore ViewCriteria row names*
As a result the query components (<af:query>, <af:quickQuery> and table filters) do not work correctly after state passivation/activation because they do not clear eventual previously applied filter condition as they do that by searching ViewCriteria rows having particular names. In this way the new condition is appended instead of overriding eventual previous one.

Answer 1

Hi Maxa,
I am the thread owner. Sorry for the delay, but my forum account was destroyed during the transition to the new Oracle's SSO, so I had to create a new account and I have missed your posting.
The table filter problem was resolved in the new JDev 11.1.1.2. The bug number is "Bug 8650239 - FILTERING CRITERIA ARE APPENDED WHEN AM POOLING IS DISABLED".
If you have to use previous JDev 11g version then the you have to patch the class oracle.jbo.ViewCriteria in the archives adfm.jar and oracle.adf.model_11.1.1.ear as follows (look at the bold lines):
{font:Courier}
public void passivate(XMLDocument doc, XMLElement node) {
ViewCriteriaRow r = (ViewCriteriaRow)row;
for(int j = 0; j < r.getAttributeCount(); j++) {
if(rowNode == null) {
rowNode = doc.createElement("Row");
((XMLElement)rowNode).setAttribute("uc", r.isUpperColumns() ? "1" : "0");
((XMLElement)rowNode).setAttribute("cj", (new StringBuilder()).append("").append(r.getConjunction()).toString());
*((XMLElement)rowNode).setAttribute("n", r.getName() == null ? "" : r.getName());*
public void activate(XMLElement node) {
for(Node rowNode = node.getFirstChild(); rowNode != null;) {
ViewCriteriaRow vcr = createViewCriteriaRow();
s = ((XMLElement)rowNode).getAttribute("uc");
if(s != null && s.length() > 0)
vcr.setUpperColumns(Integer.valueOf(s).intValue() == 1);
s = ((XMLElement)rowNode).getAttribute("cj");
if(s != null && s.length() > 0)
vcr.setConjunction(Integer.valueOf(s).intValue());
String name = ((XMLElement)rowNode).getAttribute("n");
if(name != null && name.length() > 0)
vcr.setName(name);
{font}
You have to decompile the class, add the bold lines, compile the class and repack it into the specified archives. I am affraid it is not quite legal to patch Oracle's classes but I do not have other solution.