I forgot to mention the postfix was "_selected" before, from the Dojo
widget, I changed it to "Key" to make it less cryptic, and it won't
change anymore.

musachy

Musachy Barroso wrote:
> Hi Dariusz
>
> I need to update the documentation with this info, the thing is that
> for each autocompleter, struts will create 2 fields, one for the text
> entered, with the name "${name}" and another for the key, with the
> name "${name}Key", we need both to "remember" the values if there is a
> validation error or you return INPUT from your page, so if you have:
>
> ["ACURA","351"]
>
> and
>
> <s:autocompleter name="car"....>
>
> when you click submit, it will submit:
>
> car=ACURA&carKey=351
>
> you need to add the property "car" and "carKey" in your action. About
> the opera problem, I haven't test it on opera, but I will check it out.
>
> regards
> musachy
>
> Dariusz Wojtas wrote:
>> Hello,
>>
>> I am very happy with the changes being made.
>> They really seem to help - on Firefox 2 :)
>> I can see much better propagation of events in cascaded
>> autocompleters, predefining seems to work on the simple test case that
>> I made.
>>
>> But there are still problems, some of them seem to be very new.
>> I have made a fresh build today (trunk of S2, revision 490697) and the
>> problems that I can now see [on Windows XP SP2] are:
>>
>> a) problems on MsExplorer (latest 6.xx) - problems with propagating
>> events
>>   even if I try to type characters in the 1st autocompleter in the
>> chain I get javascript error.
>>   I cannot say much about the error [poor console in ie] but it
>> makes it unusable.
>>   If I try to click on the dropdown first - usually it opens as it
>> should.
>>   But events are still not propagated.
>>
>> b) problems on Opera (9.0.2) - propagating events does not seem to
>> work.
>>
>> There is also one big problem that is browser independent.
>> I have a property in my action:
>>  private Integer carMakerId;
>> with getter and setter.
>> And I have autocompleter attached to it that.
>> The list it is loaded with is like this (part of real output) -
>> [name, id]:
>>
>>  [ ["ACURA","351"], ["ALFA ROMEO","353"], ["AUDI","354"],....]
>>
>> After I select AUDI and submit the form I get URL like this
>> /myApp/myAction.action?carMakerId=AUDI&carMakerIdKey=354
>> And that creates a long stacktrace because the carMakerId property is
>> of type Integer, which makes the action fail completely - stacktrace.
>> I created a separate JIRA ticket for the exception problem: WW-1577
>> [improve property handling].
>>
>> But the question here is - How should I handle such properties in my
>> actions?
>> Create property
>> private Integer carMakerIdKey;
>> instead? Will it be understood when preloading the value?
>> What if the property postfix changes? [I think it did recently].
>> Any hints on that?
>>
>> Thanks a lot,
>> I am really trying not to complain, I really see improvements but
>> there is still a lot to be done ;(
>>
>> Best regards
>> Dariusz Wojtas
>>
>>
>> On 12/27/06, Musachy Barroso <mbarroso@(protected):
>>> I attached a patch to WW-1562 to fix some of the things you requested.
>>>
>>> regards
>>> musachy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@(protected)
>> For additional commands, e-mail: user-help@(protected)
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)