[
https://issues.apache.org/jira/browse/WOOKIE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197012#comment-13197012
]
Paul Sharples edited comment on WOOKIE-306 at 1/31/12 4:49 PM:
---------------------------------------------------------------
Just a heads up. I have been looking at this and...
The test expects "test1" to be null (but its actually our friend "undefined"
again.)
If you fix that in the test we start to get inconsistent results.
Sometimes the test passes, most times it doesn't. It would appear that the
updates are being persisted back to the DB ok when you open the widget the
first time. (running against mysql I can check what the db looks like after
opening the widget for the first time)
However, if you open the widget again (subsequent calls are made back to the
WidgetAPIImpl class to retrieve the preferences) the results usually have
either test3 as not set or test1 still being in the recordset.(it shouldn't be
and no tuple exists for it in the db).
It looks as though the WidgetAPIImpl::preferences call has a stale read state
somehow. Note, this happens with both queues switched on and switched off.
was (Author: psharples):
Just a heads up. I have been looking at this and...
The test expects "test1" to be null (but its actually our friend "undefined"
again.)
If you fix that in the test we start to get inconsistent results.
Sometimes the test passes, most times it doesn't. It would appear that the
updates are being persisted back to the DB ok when you open the widget the
first time. (running against mysql I can check what the db looks like after
opening the widget for the first time)
However, if you open the widget again (subsequent calls are made back to the
WidgetImpl class to retrieve the preferences) the results usually have either
test3 as not set or test1 still being in the recordset.(it shouldn't be and no
tuple exists for it in the db).
It looks as though the WidgetImpl::preferences call has a stale read state
somehow. Note, this happens with both queues switched and switched off.
> Widget Interface: Conflicts when using Clear() and SetItem()
> ------------------------------------------------------------
>
> Key: WOOKIE-306
> URL: https://issues.apache.org/jira/browse/WOOKIE-306
> Project: Wookie
> Issue Type: Bug
> Reporter: Scott Wilson
>
> When running the W3C Test Case "au", Wookie fails to correctly set a value
> after calling clear() first and then reloading the page.
> This is likely caused by the clear() process executing and overriding the
> subsequent (in script order terms) setItem() call, either on the client side
> or server side.
> To replicate, use this widget:
> http://dev.w3.org/2006/waf/widgets-api/test-suite/test-cases/ta-aa/au/au.wgt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
