This works:

<on-entry>
  <set name="viewScope.commandName" value="'credentials'" />
  <set name="credentials.username" value="flowScope.credentials ==
null ? '' : flowScope.credentials.username" />
</on-entry>

I added the second "set" tag for view-state id="viewLoginForm".

Regards,
Yuriy


On Sun, Jun 13, 2010 at 8:31 PM, Scott Battaglia
<scott.battag...@gmail.com> wrote:
> Its mostly because the credentials variable is defined within the view
> state, so it gets recreated each time.  You can instantiate it outside of
> the view state.  The Web Flow 2 Schema should say how.
> Note, I'm just guessing.  I haven't tried it :-)
> Cheers,
> Scott
>
> On Thu, Jun 10, 2010 at 2:55 PM, Yuriy Zubarev <yzuba...@boats.com> wrote:
>>
>> Greetings,
>>
>> After upgrading from version 3.3.* to 3.4.* we noticed a small
>> difference in a behavior of "login" flow and a form. Whenever user
>> provides an incorrect combination of username and password, CAS flow
>> goes back to log-in page with a correct error message but "username"
>> field is empty. It used to keep its value and I would like to have
>> that behavior back. I guess Spring upgrade might be the root cause and
>> there is a way to adjust the behavior through the maze of Spring XML
>> configuration.
>>
>> I shamelessly wanted to save myself couple of days digging through
>> Spring documentation and ask the community if it's already figured it
>> out.
>>
>> Thank you,
>> Yuriy
>>
>> --
>> You are currently subscribed to cas-user@lists.jasig.org as:
>> scott.battag...@gmail.com
>> To unsubscribe, change settings or access archives, see
>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
> --
> You are currently subscribed to cas-user@lists.jasig.org as:
> yzuba...@boats.com
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user

-- 
You are currently subscribed to cas-user@lists.jasig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to