Problems with Associations between entities (jdev903production)

Question

Hi,
every now and then, I feel a strong urge to pick up my pc and throw it out the window, when I'm working in jdeveloper.
But usually just in time I realise the power that bc4j still has, and the fact that people walking under my window might not be too pleased with my pc landing on their head convinces me to just count to 10, and just retry what I was trying to do.
I will explain the problems below:
1. Wrongly numbered and magically renumbered members
I have an entity with about 13 attributes. The underlying schema object is a view (simple view
on a table, nothing fancy).
I have a few associations between this entity and several other entities, one of which is an association with itself (parent/child relation). Some of these associations have accessors, and the parent/child association has accessors both ways (getParent() and getChildren()).
When I compile, I get an error like this:
Error(399,12): duplicate case label.
This problem occurs because near the top of the file, the attributes have been defined as follows:
protected static final int ASSET = 0;
protected static final int PARENT = 1;
protected static final int PRICELINES = 2;
protected static final int CHILDREN = 3;
protected static final int ID = 0;
protected static final int CODE = 1;
protected static final int ENDDATE = 2;
protected static final int STARTDATE = 3;
protected static final int TYPE = 4;
The first 4 are from the association accessors, the rest (starting with ID) are attributes. Why do these get the same numbers?
I edited the first 4 lines and gave them increasing numbers that didn't conflict with any of the attributes. But each time I edit one of the associations, all of these lines get renumbered again and start counting at 0! (even if I move the lines down so they are in the correct order).
So even if I just edit the parent/child association, even the PRICELINES (which is an accessor NOT from the association I'm editing) thing gets renumbered wrongly.
Why?!
2. Internal XML parser error
Every now and then, after playing around with associations and viewlinks, I suddenly get an error message like this:
"Expected Name instead of '<'."
from the XML parser, when I try to open a ViewObject from the navigator. The XML files look fine, but even a restart of jdeveloper doesn't help. In this case I usually delete my files, get the last known working versions from CVS and redo what I did before it went wrong. Because of the randomness (though quite frequent) of this problem, I can't provide you with good 'steps to reproduce' yet, but do you have any clue as to what might cause this? It's quite a nuisance.
Greetings,
Ivo

Answer 1

[list]
[*]Wrongly numbered and magically renumbered members
We just found and fixed a problem for 9.0.4 yesterday where in some cases
the constants for the accessors got inadvertently renumbered.
I hope it's the same issue you're hitting, but I cannot
be 100% sure unless you could send me a testcase project
for me to try and reproduce with 9.0.3 and with the
fixed 9.0.4 release.
[*]Internal XML parser error
An error like "Expected Name instead of '<'." can mean some kind of corruption in the XML file. When you say they "look" fine, are you able to verify by trying to parse them externally to make sure it's not some subtle error your eye is not seeing?
If you can give me a testcase project and tell me what steps to try and repeat, I can have our QA team try and exercise your steps to hopefully reproduce the problem.
[*]View Accessors are not being created
You mentioned a source control system in the mix. Is there any possibility that the YourViewImpl.java file is read-only on the file system? This would cause BC4J to not be able to write the accessor into the file.
[*]Magically disappearing ViewLink source/destination attributes
Obviously, this is not intentional. I'll ask the developer to see if
there's anything obvious that could be the cause of this
"short-circuit" of correct functionality.
[*]Dependencies not checked correctly when using entitylevel inheritance
"(no inheritance is possible on the view level)"
The above statement confused me. We do support View objects extending
other view objects, however I was able to reproduce the problem
and I filed Bug#2678090 to get it fixed.
[*]EVERY question/problem on the forum needs to be analyzed by a team member with 1 exclusive question: [How] Could have better documentation / help file elimenated this problem?
Excellent point. And we are doing this!
[*]Don't get me wrong; if this weren't a super product; I would not be here.
Neither would we. ;->
Let's identify every remaining technical issue for you, ideally get a testcase to reproduce the problem, and then we'll fix it.
[*]And truly; thank you for taking this time with us. Not every company affords so many resources with their customers; let alone free downloads.
We believe it's a great 21st-century way to be in direct contact with our customers. The feedback we get here is awesome for the product!
[*](Hey! I Want to pay. Help me finish and sell my app!)
We want you help you finish faster, too. Keep the questions and issues coming and we're doing our best to address them.
[list]