[WICKET-6279] AttributeModifier.VALUELESS_ATTRIBUTE_REMOVE does not work after deserialisation - ASF JIRA

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 7.2.0
Fix Version/s: 7.6.0, 8.0.0-M3
Component/s: wicket
Labels:
- attribute
- behavior
Environment:
Tomcat 7.0
Windows 7

Description

The magic values AttributeModifier.VALUELESS_ATTRIBUTE_REMOVE and AttributeModifier.VALUELESS_ATTRIBUTE_ADD do not work correctly after they have been deserialized.

Imagine you have a page with a component that has sth. added like this:

component.add(AttributeModifier.replace("myattribute", AttributeModifier.VALUELESS_ATTRIBUTE_ADD));

component.add(AttributeModifier.replace("anotherattribute", Model.of(AttributeModifier.VALUELESS_ATTRIBUTE_ADD)));

component.add(AttributeModifier.replace("thirdattribute", new StringResourceModel("myresourcekey").setDefaultValue(AttributeModifier.VALUELESS_ATTRIBUTE_ADD)));

Once we navigate away from the page, it gets serialized including the String value "VA_ADD" for AttributeModifier.VALUELESS_ATTRIBUTE_ADD. When we go back (e.g. with browser back button), it is deserialized. But then the deserialized String "VA_ADD" is not anymore the same as AttributeModifier.VALUELESS_ATTRIBUTE_ADD, so we have an attribute added to our component with value "VA_ADD".

I'm not sure how this can be resolved or if it can be resolved at all. My workaround is to use an AbstractReadOnlyModel that always returns AttributeModifier.VALUELESS_ATTRIBUTE_ADD, so that special value is not serialized at all.

If it's not possible to manage the deserialisation, then there should be at least some documentation about this problem and maybe convenience code using my workaround with AbstractReadOnlyModel could be provided.

Thanks,
Sven