JDev 9.0.3 LOV-Binding Bug?

Question

Hi!
I've got a little problem with JDev 9.0.3 when migrating my project from JDev 9.0.2. All known Bugs from JDev 9.0.2 seem to be fixed but therefore other bugs appeared.
My Problem in detail:
I have 2 views (simplified):
ORDERVIEW
-- OrderId (DBSequence)
-- OrderTypeIdFK (Number)
ORDERTYPEVIEW
-- OrderTypeId (Number)
-- OrderTypeDescription (String)
On a panel I display a textfield with OrderId and a ComboBox which should display the according OrderTypeDescription.
So I created a LOVBinding on this ComboBox:
LOV-ViewObject
OrderTypeView
-- OrderTypeId
TargetViewObject
OrderView
-- OrderTypeIdFk
LOV attributes to display
-- OrderTypeDescription
In JDev 9.0.2 this works perfectly, besides the missing search-function.
When migrating to 9.0.3 without performing any changes I got the following exception when changing a OrderView-Row by selecting another OrderTypeDescription from the ComboBox:
oracle.jbo.domain.DataCreationException: JBO-25009: Cannot create an object of type:oracle.jbo.domain.Number with value: Buy
("Buy" is one OrderTypeDescription)
It seems that JDev wants to write OrderTypeDescription into the OrderTypeFK-Field. Of course, that can't work...
If I change "LOV attributes to display" to "OrderTypeId" it works fine, but that's not what I want....
Any suggestions? Thanks a lot
Bernhard

Answer 1

I have a problem very much like the one Bernhard described but in 9.0.2. A combobox with LOV-binding first worked fine but then I decided to make the control non-editable to force the user select one of the list items, not modifying the combobox contents by keyboard. After all, it makes no sense to let the user write something that has no counterpart in the LOV list. So I added 'myCombo.setEditable(false)' in my code. The result was that the combobox still shows Ok a description corresponding to an id value found in database but if I pick another value in the combobox list and try to update it to database then I get the same error Bernhard did. Is this the same bug? Should I upgrade to 9.0.3 (we are planning to do it) and get the patch to it or is there any other remedy?
- Risto