Hi, I am also facing the problem of invalid field value. I didnt give any validation for the datetimepicker but it validate itself and give this field error. Pls help asap.
With Regards, Ashok Torsten Römer wrote: > > Great, that was quickly fixed :-) > > I'm looking forward to 2.1.0! > > Thanks! > > Torsten > > Musachy Barroso wrote: >> I found several problem with the datetimepicker, first (and the worst) is >> that the names of the input fields (visible and hidden) were switched. >> Second, the hidden field was storing just the date section of the RFC >> 3339 >> format. In short, in the few cases that it worked it was because Xwork >> tries >> as a hard as possible to parse dates, using different formats. >> >> thanks >> musachy >> >> On 5/8/07, Torsten Römer <[EMAIL PROTECTED]> wrote: >>> >>> Done! (WW-1917) >>> >>> Hope this is useful, if I can help out in any other way please let me >>> know! >>> >>> BTW there is no such locale en_UK, it should be en_GB, but unfortunately >>> that wasn't the problem. >>> >>> Torsten >>> >>> Musachy Barroso schrieb: >>> > Can you log a jira ticket with the details on how to reproduce the >>> problem? >>> > >>> > https://issues.apache.org/struts/ >>> > >>> > thanks >>> > musachy >>> > >>> > On 5/8/07, Torsten Römer <[EMAIL PROTECTED]> wrote: >>> >> >>> >> Yes I did, and I also get that far; the datepicker shows up fine, and >>> it >>> >> inserts the picked date in the field in the format I specified using >>> >> displayFormat - but when I submit the form I get that validation >>> error. >>> >> >>> >> So I am still using String instead of Date and I'm currently trying >>> to >>> >> get the entered date validated. When this works I am already quite >>> happy. >>> >> >>> >> The problem that occurs in case the user has JavaScript disabled I am >>> >> BTW working around by placing an additional textfield with the same >>> name >>> >> in a <noscript> tag. Like this the user can at least enter a date >>> >> manually. >>> >> >>> >> Torsten >>> >> >>> >> Musachy Barroso schrieb: >>> >> > Did you look at the examples in showcase? I know the timepicker was >>> >> really >>> >> > broken on 2.0.6, but the datepicker was working. >>> >> > >>> >> > musachy >>> >> > >>> >> > On 5/8/07, Torsten Römer <[EMAIL PROTECTED]> wrote: >>> >> >> >>> >> >> I didn't have any struts.date.format set in my .properties files, >>> but >>> >> >> for testing I set it to yyyy-MM-dd in all of them but that doesn't >>> >> seem >>> >> >> to have any effect. The date is still shown in dd.MM.yy format, >>> and >>> I >>> >> >> get that validation error when request_locale=en_UK. >>> >> >> >>> >> >> Then I also set displayFormat to yyyy-MM-dd but like this I always >>> get >>> >> a >>> >> >> validation error. >>> >> >> >>> >> >> If I try to set saveFormat I get an exception: >>> >> >> SCHWERWIEGEND: Servlet.service() for servlet jsp threw exception >>> >> >> org.apache.jasper.JasperException: /page/reservation.jsp(15,1) >>> >> Attribute >>> >> >> saveFormat invalid for tag datetimepicker according to TLD >>> >> >> >>> >> >> The only way how I can get it to work is to use strings and parse >>> the >>> >> >> date myself in the action class. But like this, no validation is >>> done >>> >> at >>> >> >> all. >>> >> >> >>> >> >> It's a pity because the datetimepicker would be extremely easy to >>> >> use & >>> >> >> it looks really nice but it doesn't seem to like me ;-) >>> >> >> >>> >> >> Torsten >>> >> >> >>> >> >> Martin Gainty schrieb: >>> >> >> > please display contents of struts.date.format >>> >> >> > for both *en_UK.properties and >>> >> >> > *de_DE.properties files >>> >> >> > >>> >> >> > Martin-- >>> >> >> > This email message and any files transmitted with it contain >>> >> >> confidential >>> >> >> > information intended only for the person(s) to whom this email >>> >> message >>> >> >> is >>> >> >> > addressed. If you have received this email message in error, >>> please >>> >> >> notify >>> >> >> > the sender immediately by telephone or email and destroy the >>> >> original >>> >> >> > message without making a copy. Thank you. >>> >> >> > >>> >> >> > ----- Original Message ----- From: "Musachy Barroso" >>> >> >> <[EMAIL PROTECTED]> >>> >> >> > To: "Struts Users Mailing List" <user@struts.apache.org> >>> >> >> > Sent: Monday, May 07, 2007 8:05 PM >>> >> >> > Subject: Re: Correct usage of datetimepicker? >>> >> >> > >>> >> >> > >>> >> >> > Using Date for the action field is the way to go. The selected >>> value >>> >> is >>> >> >> > submited in RFC 3339 format (that can me modified using the >>> >> saveFormat >>> >> >> > attribute, which shouldn't have been public on the first place). >>> I'm >>> >> >> not >>> >> >> > really sure how it would work if the client has javascript >>> disabled. >>> >> >> > >>> >> >> > musachy >>> >> >> > >>> >> >> > On 5/7/07, Torsten Römer <[EMAIL PROTECTED]> wrote: >>> >> >> >> >>> >> >> >> I'm a bit unsure about a few things around datetimepicker. >>> >> >> >> >>> >> >> >> What type should the fields in my action class be? I am >>> currently >>> >> >> using >>> >> >> >> java.util.Date, it works fine for request_locale=de_DE but I >>> get >>> a >>> >> >> >> "Invalid field value for field ..." error for >>> request_locale=en_UK >>> >> and >>> >> >> >> the date redisplayed is "NaN.NaN.aN". I don't quite understand >>> >> this, >>> >> >> >> because the API doc says: "The value sent to the server is >>> >> typically >>> >> a >>> >> >> >> locale-independent value in a hidden field as defined by the >>> name >>> >> >> >> attribute" - but it seems the locale matters anyway? >>> >> >> >> >>> >> >> >> What also confuses me, is the displayFormat attribute. If I set >>> it >>> >> to >>> >> >> >> e.g. "yyyy-MM-dd", I always get the "Invalid field value for >>> field >>> >> >> ..." >>> >> >> >> error, regardless of the request_locale. >>> >> >> >> I am also a bit unsure about the format and saveFormat >>> >> attributes. I >>> >> >> >> played with them, but they did not seem to make any difference. >>> >> >> >> >>> >> >> >> I also wonder how to handle the situation where a user has >>> >> Javascript >>> >> >> >> disabled, in which case the date field + icon are not shown at >>> all. >>> >> >> >> >>> >> >> >> I am using Struts2 2.0.6. >>> >> >> >> >>> >> >> >> Torsten >>> >> >> >> >>> >> >> >> >>> >> --------------------------------------------------------------------- >>> >> >> >> 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] >>> >> >> >>> >> >> >>> >> > >>> >> > >>> >> >>> >> --------------------------------------------------------------------- >>> >> 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] >>> >>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Correct-usage-of-datetimepicker--tp10367578p19636905.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
