1.0.2 sanity testing - feedback requested

[Keith Donald]

Msauer,

That is right, the set element has not been enhanced for 1.0.2 and will not be as we decided it was too significant of an enhancement for a point release (will consider it again for 1.1).

Regardless in your case you should use flow variables with the 'var' element. See sellitem-jsf for an example.

Keith

[jeremyg484]

I am assuming that if I use the new DelegatingFlowVariableResolver I will not be able to expect that my bean will be created from the spring context as it was before. My understanding is that with this recommended variable resolver I will have to use the set element to create the flow scope bean. Is that correct?

You will indeed need some other way to populate your flow variables if you opt not to also use the original FlowVariableResolver and FlowPropertyResolver. But keep in mind that you can configure as many variable and property resolvers as you want, so you could potentially continue to use ${flowScope.xxx} and let the old resolver delegate to the application context for bean creation on demand.

Jeremy

[jamesclinton]

Build 51 has resolved my component binding errors present in 39-42.

Thank you.