[
https://issues.apache.org/jira/browse/WOOKIE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197776#comment-13197776
]
Scott Wilson commented on WOOKIE-306:
-------------------------------------
Yes, I'd noticed that warning crop up. The only thing I came across as a
possible explanation was a discussion on the "leakiness" of the enhanced
Collection object (aka the Smart Proxy) that JPA creates for child Collections;
as we subclass Collection with the specialized InverseRelationshipCollection
class this may well be the problem:
http://grep.elasticpath.com/community/techblog/blog/2010/09/21/openjpa-and-collection-smart-proxies;jsessionid=995420CAB9020A69299283D2E26D5A30
However, when I tried to change WidgetInstanceImpl.preferences to a regular
Collection type it broke a load of other things so I reverted it.
At least with this fix we do get better consistency, even if its not perfect,
so I'm happy to close this one.
> 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
> Fix For: 0.9.2
>
>
> 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
