Re: [S2] datetimepicker and dates

[Musachy Barroso]

Can you find out what is the value that is being submitted? FF plugin 
"Tamper Data" is handy for this. The other thing is that the datepicker 
is the only one working right now, the timepicker is broken (doesn't use 
RFC 3339). I think you are using datepicker, but I just wanted to make 
sure :)

thanks
musachy
Dariusz Wojtas wrote:
Hi Musachy,

I compiled the latest xwork 2.0.1  snapshot.
I used S2.0.5 snapshot (last weekend) and today's xwork 2.0.1 snapshot.
I have double checked if I use correct JAR files.
The problem is still there.
Exactly the same symptoms.
Date is not set, property is null:

   <s:datetimepicker name="myDateProperty" displayFormat="yyyy-MM-dd"
       label="My Date Label"/>

And I get the same error on the console:
19:55:00,984 ERROR - ParametersInterceptor      -
ParametersInterceptor - [setParameters]: Unexpected Exception catched:
Error setting expression 'myDateProperty' with value
'[Ljava.lang.String;@6d4f30'

If I uncomment my custom Date converter in xwork-conversion.properties
then it works.

One extra question.
Can the interceptor be modified to check if the parameter is an array
(We both know it is at this point), and print at least the 1st element
from the array?
Dummy toString from array is almost useless.

Something like
  Error setting expression 'myDateProperty' with value ['<1st val>', 
....]


Best regards
Dariusz Wojtas

On 2/6/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
I got the same error on 1.6, but it works on 1.5.

thanks
musachy

Dariusz Wojtas wrote:
> Hi Musachy,
>
> I have problems with compiling xwork from SVN. A fresh copy.
> I am using JDK 1.6, maybe this is the reason.
>
> mvn clean install
>
> produces after some time
>
> [ERROR] BUILD FAILURE
> [INFO]
> 
------------------------------------------------------------------------
> [INFO] Compilation failure
>
> 
c:\projects\xwork\src\java\com\opensymphony\xwork2\inject\ContainerImpl.java:[334,50] 

>
> incompatible types
> found   : java.lang.reflect.Constructor<?>
> required: java.lang.reflect.Constructor<T>
>
> Can you share a copy of xwork or point to some nightly build?
>
> Regards
> Dariusz Wojtas
>
> On 2/5/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
>> 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 <[EMAIL 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;@1bd06a0'
>> >> >
>> >> >
>> >> > 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]