datetimepicker and dates 2007-02-05 - By Musachy Barroso
Back
The patch was already committed to xwork by Phil. You just need to
update and recompile.
thanks
musachy
Dariusz Wojtas wrote:
> ok, I surely will try this patch - somewhen later this week.
> I will inform you about the results.
>
> Thanks for quick response.
>
> Best regards
> Dariusz Wojtas
>
> On 2/5/07, Musachy Barroso <mbarroso@(protected)> wrote:
>> Hi Dariousz
>>
>> I recently sent a patch for XWork to parse dates on RFC 3339 format
>> (which the datepicker uses):
>>
>> https://issues.apache.org/struts/browse/WW-1643
>>
>> Can you recompile xwork and try?
>>
>> musachy
>>
>>
>> Dariusz Wojtas wrote:
>> > Hi,
>> >
>> > I have been reporting some problems with conversion at the beginning
>> > of the year.
>> > There were problems with conversion when some actions/pages were
>> > invoked from the Opera browser. A bit strange but that's how it was.
>> >
>> > Now I tried Opera again and I found a case in which some code fails
>> > under Opera (9.0.2) but works perfectly under FF and IE.
>> >
>> > <s:datetimepicker name="myDateProperty" displayFormat="yyyy-MM-dd"
>> > label="My Date Label"/>
>> >
>> > My action defines a property of type java.util.Date 
>> > I select some date in my form, submit it (2007-02-05) and the date is
>> > set in the action when called from IE or FF, but it is still null when
>> > invoked from Opera.
>> > I only can see some log:
>> >
>> > 20:31:15,718 ERROR - ParametersInterceptor -
>> > ParametersInterceptor - [setParameters]: Unexpected Exception catched:
>> > Error setting expression 'myDateProperty with value
>> > '[Ljava.lang.String;@(protected)'
>> >
>> >
>> > I defined a custom date converter (I already have to use converters
>> > for float and double, doesn't work without them - commas vs dots) and
>> > it started to work.
>> >
>> > Is there any way to have a better, out of the box solution?
>> > I believe this may be something with the locale, but cant be sure.
>> > I do not play with locale in my app.
>> >
>> > I use a standard widget (which works nicely) but it fails in some
>> > environments.
>> > Now I found the reason, I found some solution - works for me - but
>> > this shows some general problem.
>> >
>> > This email is rather not a question for help, but info about some
>> > problem.
>> >
>> > Best regards
>> > Dariusz Wojtas
>
> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
> 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)
|
|
