|
We have noticed that backbase seems to have a lot of trouble with removing/replacing elements which are being used by concurrent threads. This often manifests as the error
CRITICAL: Javascript error: 'TypeError, h_ has no properties'
upon which Backbase crashes and the interface no longer responds to events.
We have noticed this problem with several unrelated parts of our UI. We are not doing anything at all unusual like using Javascript to control backbase, it's all straight BXML. The only common theme we can discern is that the element being removed has a long-running constructor (which fires of an HTTP request for example) and it crashes if it is replaced while the constructor is still running.
Has anyone else encountered this? Are there plans to address this in Backbase? Is there a recommended workaround, or coding practice which is guaranteed to avoid this problem?
So far we have worked around it as much as possible by extensive use of locking. However this is a hassle, it makes the interface seem less responsive, and it is hard to tell if we have locked everything which might trigger this error.
thread locking
14 April, 2008 - 16:28 — arkanticeInside the panelset, i have a panel with filter(forms) and a panel with links. When the user changes the filter values it submits the form (which writes the values in the session). There are some mandatory fields inside the form. Now if the user clicks the link very quickly after setting the filter value, the calling of the file executes first before submitting the form(with filters), which offcourse leeds to an error(will tell the user that he hasnt selected any filter value).
Thread locking//restricting user activities.....
16 April, 2008 - 17:01 — arkanticeHello BB
No Update Regarding this issue??This is a bug in our application. We are using 3.3.1(community version).
Looking forward to hear from BB.
Ar Kantice