Willow selections

Hi Tomaz,

First check that your selection component is not created in every render cycle, so it can hold its state between calls. Usually components holding state must be kept in instance variables in the containing component, initialized once and rendered many times.

Second, the selection state needs to be serialized so it's available in the server. Some affordances (like #determineBehaviorByEvaluating:) applied on the selection component automatically serializes the content but others not. You can check it by looking at the affordances you're using and locating the WebInteractionCommand being applied. Each command responds to #requiresSerialization indicating if it will automatically serialize the content of the triggered component or not. (This deserves a better explanation in the docs, I will create an issue to not forget).

In case you're using an affordance not doing automatic serialization or if you want the state to be synchronized  when another component is triggered, you need to use some of the serialization affordances (check WebInteractionInterpreter). Depending on the interactivity level you want is the serialization strategy you should use.

Now in your case it depends on what you are trying to accomplish. If you want the selection to be available as soon as possible, you need to use serializeIt or serializeWithHiddenInputs if no other affordance is doing the automatic serialization when triggering the selection. If you want to do fewer server calls (and for example just send everything on a single call when a button is clicked) you need to serialize the form containing the selection components when triggering the button.

Hope it helps.

Gabriel