FBean.Register(classname) only succeeds the first time classname is used?!

Question

This is not a question, it is a futile cry of helplessness, such as a 9 month old might make when they strike their head on a rock.
Consider:
'BLOCKA'.WHEN-NEW-BLOCK-INSTANCE:
FBean.Register_Bean('ITEMA', ALL_ROWS, 'my.TestBean');'BLOCKB'.WHEN-NEW-BLOCK-INSTANCE:
FBean.Register_Bean('ITEMB', ALL_ROWS, 'my.TestBean');And what happens? If BLOCKA is 'first', ITEMA is populated with the TestBean, but BLOCKB's ITEMB is not. Conversely, if BLOCKB is first, ITEMB is populated with the TestBean, but BLOCKA's ITEMA is not.
Happily, it doesn't matter to me today. But it would be fair to say that Forms and I are becoming estranged on a fairly brief aquiantance.

Answer 1

Thanks Francois,
I am certainly feeling a bit alone in the Oracle Forms enhanced JavaBeans world, trying to get a PROPERTY_CHANGED_EVENT to bubble up from my bean into my form. [This Google Query|http://www.google.com.au/search?q=FBEAN+PROPERTY_CHANGED_EVENT&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-GB:official&client=firefox-a] for "FBEAN PROPERTY_CHANGED_EVENT" (both of which would appear on the FBEAN.ENABLE_EVENTS line) finds only my poor posts from yesterday.
I really, really dislike the legacy Forms JavaBeans approach. A JavaBean is all about properties and state. Something simple like 'background-color' is a good example. You should be able to simply:
FBEAN.SET_PROPERTY('My_Bean_Area', 'background-color', '#FFFFF');
which is equivalent to:
bean.backgroundColor = "#FFFFFF";
... and the same bean class is usable in both Java and Oracle Forms.
With the legacy Forms JavaBeans appraoch, you've got to write a wrapper class, AND you'd be forced to write something semantically nonsensical like:
:success = GET_CUSTOM_PROPERTY('My_Bean_Area', 'SETBACKGROUNDCOLOR', '#FFFFFF');
and the hapless monkey who's come to fix your broken code can't wrap his mind around why your'e using a getter to mutate the bean (or why you're returning a value from your setter, for that mattter).
(PS. I do not accuse YOU of such crimes, but i have inherited a codebase which would shock you. and the legacy Forms JavaBeans approach is largely to blame).
Anyhow. I guess I had better try to extract some sense from GET_CUSTOM_PROPERTY and friends instead of whining ...
cheers,
David.