Jdeveloper 11g + decode syntax exception

Question

Hello,
I am using Build JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536.
When I add decode sql function in order by clause,following exception throws in Jdeveloper IDE. it looks like pattern issue,any clue??
SEVERE: exception visiting oracle.xml.parser.v2.XMLAttr@6e80b2
DeptView.xml [1047:1063) [45,4:45,20)
44: <ViewLinkAccessor
45: Name="EmpEOView"
46: ViewLink="model.WorksInDeptLink"
47: Type="oracle.jbo.RowIterator"
java.util.regex.PatternSyntaxException: Unclosed group near index 16
\bDECODE(DNAME\b
^
     at java.util.regex.Pattern.error(Pattern.java:1713)
     at java.util.regex.Pattern.accept(Pattern.java:1571)
     at java.util.regex.Pattern.group0(Pattern.java:2533)
     at java.util.regex.Pattern.sequence(Pattern.java:1806)
     at java.util.regex.Pattern.expr(Pattern.java:1752)
     at java.util.regex.Pattern.compile(Pattern.java:1460)
     at java.util.regex.Pattern.<init>(Pattern.java:1133)
     at java.util.regex.Pattern.compile(Pattern.java:823)
     at oracle.jbo.dt.dependency.xdf.SQLReferenceFactory.getStartIndex(SQLReferenceFactory.java:286)
Thanks
RB

Answer 1

To anyone else encountering this:
I would just like to report, that Oracle Development has managed to reproduce this problem from scratch by following a similar upgrade path 10.1.3.0->10.1.3.4->11.1.1.0. The problem is NOT OS-related, but related to migrating the user settings from 10.1.3.3. So Jan you were right about that. Credits go to you :)
The only workaround for me has so far been to take a backup of my old SYSTEM directory causing the problem, and I have been forced to carefully recreate all my settings to get around this problem, since I already removed my old 10.1.3.3 installation, assuming the migration went OK - which it didn't... So, I will keep my old backup, in the hope that Development finds a fix to this issue, so I can go back to the settings I used to have, even though I THINK I have recreated them all for 11g - not completely sure though... time will tell.
Until then, I will track the bug, that Didier has logged for me, which he mentioned in his post.
Regards,
Jacob