Did you try setting your minDate to '07/01/2005'? I don't have time
to check, but I'm not sure if MM/DD/YYYY requires the padding zero or not.
Pat
Message
From: Todd [mailto:torr0101 (AT) gmail (DOT) com]
Sent: Thursday, November 17, 2005 4:34 PM
To: Tapestry users
Subject: JBoss/Tomcat Validation Error Inconsistency
We are evaluating Tapestry 4 at the company I'm working for and we've run
into a strange error. Upon navigating to the page in question we receive
an
error when the page attempts to load its validators. Perhaps we've missed
something, or this is a true bug. I hope its the former since this may
impact our decision making. Any ideas would be greatly appreciated.
JDK5
Tapestry4-beta13
JBoss4.03SP1
Tomcat5
From the Exception page:
Error initializing validator 'minDate' (class
): Unable to convert '7/1/2005'
to
type java.util.Date (for property minDate of object
@67ec05): Unparseable date:
"7/1/2005"; - nested throwable: (java.text.ParseException: Unparseable
date:
"7/1/2005")
61</component62
63<component id="shippingDate" type="DatePicker"64 <binding name="value"
value="shippingDate"/65 <binding name="translator"
value="translator:date,pattern=MM/dd/yyyy"/66 <binding name="validators"
value="validators:required,minDate=7/1/2005,maxDate=12/31/2005"/>
67<binding name="displayName" value="literal:Shipping Date"/>
68</component69
70<component id="desc" type="TextArea"71 <binding name="value"
value="desc"/>
To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org

I totally forgot to mention the weirdest part, it works on Tomcat. I don't
know what that means.

11/17/05, Konstantin Ignatyev <kgignatyev (AT) yahoo (DOT) comwrote:

That was my thought too but
SimpleDateFormat("MM/dd/yyyy") happily accepts
7/1/2001 at least in 1.5.0_05

Patrick Casey <patcasey (AT) adelphia (DOT) netwrote:
--
Did you try setting your minDate to '07/01/2005'? I
don't have time
to check, but I'm not sure if MM/DD/YYYY requires
the padding zero or not.

Pat

Message
From: Todd [mailto:torr0101 (AT) gmail (DOT) com]
Sent: Thursday, November 17, 2005 4:34 PM
To: Tapestry users
Subject: JBoss/Tomcat Validation Error
Inconsistency

We are evaluating Tapestry 4 at the company I'm
working for and we've run
into a strange error. Upon navigating to the page
in question we receive
an
error when the page attempts to load its
validators. Perhaps we've missed
something, or this is a true bug. I hope its the
former since this may
impact our decision making. Any ideas would be
greatly appreciated.

JDK5
Tapestry4-beta13
JBoss4.03SP1
Tomcat5

From the Exception page:

Error initializing validator 'minDate' (class
):
Unable to convert '7/1/2005'
to
type java.util.Date (for property minDate of
object

@67ec05):
Unparseable date:
"7/1/2005"; - nested throwable:
(java.text.ParseException: Unparseable
date:
"7/1/2005")

61</component62
63<component id="shippingDate" type="DatePicker">
64 <binding name="value"
value="shippingDate"/65 <binding
name="translator"
value="translator:date,pattern=MM/dd/yyyy"/66
<binding name="validators"
--
value="validators:required,minDate=7/1/2005,maxDate=12/31/2005"/>
67<binding name="displayName"
value="literal:Shipping Date"/>
68</component69
70<component id="desc" type="TextArea"71
<binding name="value"
value="desc"/>
>
>
>
>

To unsubscribe, e-mail:
tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail:
tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
--

However, JBoss is our production server, so we really need to address
this. The code I originally provided is out of the tutorial from Enjoying
Web Development With Tapestry. I'm not the actual developer that did it, but
I'll bet we can provide a war if anyone is interested.

11/17/05, Todd <torr0101 (AT) gmail (DOT) comwrote:

I totally forgot to mention the weirdest part, it works on Tomcat. I don't
know what that means.

11/17/05, Konstantin Ignatyev < kgignatyev (AT) yahoo (DOT) comwrote:

That was my thought too but
SimpleDateFormat("MM/dd/yyyy") happily accepts
7/1/2001 at least in 1.5.0_05

Patrick Casey <patcasey (AT) adelphia (DOT) netwrote:
--
Did you try setting your minDate to '07/01/2005'? I
don't have time
to check, but I'm not sure if MM/DD/YYYY requires
the padding zero or not.

Pat

Message
From: Todd [mailto: torr0101 (AT) gmail (DOT) com]
Sent: Thursday, November 17, 2005 4:34 PM
To: Tapestry users
Subject: JBoss/Tomcat Validation Error
Inconsistency

We are evaluating Tapestry 4 at the company I'm
working for and we've run
into a strange error. Upon navigating to the page
in question we receive
an
error when the page attempts to load its
validators. Perhaps we've missed
something, or this is a true bug. I hope its the
former since this may
impact our decision making. Any ideas would be
greatly appreciated.

JDK5
Tapestry4-beta13
JBoss4.03SP1
Tomcat5

From the Exception page:

Error initializing validator 'minDate' (class
):
Unable to convert '7/1/2005'
to
type java.util.Date (for property minDate of
object

@67ec05 ):
Unparseable date:
"7/1/2005"; - nested throwable:
(java.text.ParseException: Unparseable
date:
"7/1/2005")

61</component62
63<component id="shippingDate" type="DatePicker">
64 <binding name="value"
value="shippingDate"/65 <binding
name="translator"
value="translator:date,pattern=MM/dd/yyyy"/66
<binding name="validators"
--
value="validators:required,minDate=7/1/2005,maxDate=12/31/2005"/>
67<binding name="displayName"
value="literal:Shipping Date"/>
68</component69
70<component id="desc" type="TextArea"71
<binding name="value"
value="desc"/>
>
>
>
>

To unsubscribe, e-mail:
tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail:
tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>

one developer ran into this on JBoss on his machine. He passed it
on to another that dropped the war into Tomcat, it worked for him. So, then
I dropped it into my JBoss and I received the error. My JBoss install used
the all option. So, I thought maybe JBoss-AP was interfering, but that's a
shot in the dark.

11/17/05, Patrick Casey <patcasey (AT) adelphia (DOT) netwrote:
--
Is JBoss using the same JVM as your vanilla Tomcat system? I'm still
hung up on the potential red herring of that date format.

Pat

Message
From: Todd [mailto:torr0101 (AT) gmail (DOT) com]
Sent: Thursday, November 17, 2005 9:53 PM
To: Tapestry users
Subject: Re: JBoss/Tomcat Validation Error Inconsistency

I totally forgot to mention the weirdest part, it works on Tomcat. I
don't
know what that means.

11/17/05, Konstantin Ignatyev <kgignatyev (AT) yahoo (DOT) comwrote:

That was my thought too but
SimpleDateFormat("MM/dd/yyyy") happily accepts
7/1/2001 at least in 1.5.0_05

Patrick Casey <patcasey (AT) adelphia (DOT) netwrote:
--
Did you try setting your minDate to '07/01/2005'? I
don't have time
to check, but I'm not sure if MM/DD/YYYY requires
the padding zero or not.

Pat

Message
From: Todd [mailto:torr0101 (AT) gmail (DOT) com]
Sent: Thursday, November 17, 2005 4:34 PM
To: Tapestry users
Subject: JBoss/Tomcat Validation Error
Inconsistency

We are evaluating Tapestry 4 at the company I'm
working for and we've run
into a strange error. Upon navigating to the page
in question we receive
an
error when the page attempts to load its
validators. Perhaps we've missed
something, or this is a true bug. I hope its the
former since this may
impact our decision making. Any ideas would be
greatly appreciated.

JDK5
Tapestry4-beta13
JBoss4.03SP1
Tomcat5

From the Exception page:

Error initializing validator 'minDate' (class
):
Unable to convert '7/1/2005'
to
type java.util.Date (for property minDate of
object

@67ec05):
Unparseable date:
"7/1/2005"; - nested throwable:
(java.text.ParseException: Unparseable
date:
"7/1/2005")

61</component62
63<component id="shippingDate" type="DatePicker">
64 <binding name="value"
value="shippingDate"/65 <binding
name="translator"
value="translator:date,pattern=MM/dd/yyyy"/66
<binding name="validators"
--
value="validators:required,minDate=7/1/2005,maxDate=12/31/2005"/>
67<binding name="displayName"
value="literal:Shipping Date"/>
68</component69
70<component id="desc" type="TextArea"71
<binding name="value"
value="desc"/>
>
>
>
>

To unsubscribe, e-mail:
tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail:
tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
--

Well, we have not been able to determine what's happening. Apparently, no
one else can either. Unfortunately, this may mean that the powers that be at
my co will mandate that we consolidate our developer skills in Struts. I
fought hard on this one. To be taken down by a silly JBoss bugMaybe I can
steer us off JBoss ;). Wishful thinking.

I'll still use T4 as a hobby, but I think my company's apps would have
benefited from some of T4's performance minded features. We're bigger / much
more highly transactional than TSS. :(

Thanks for all your help!

11/17/05, Todd <torr0101 (AT) gmail (DOT) comwrote:

one developer ran into this on JBoss on his machine. He passed
it on to another that dropped the war into Tomcat, it worked for him. So,
then I dropped it into my JBoss and I received the error. My JBoss install
used the all option. So, I thought maybe JBoss-AP was interfering, but
that's a shot in the dark.

11/17/05, Patrick Casey <patcasey (AT) adelphia (DOT) netwrote:
--
Is JBoss using the same JVM as your vanilla Tomcat system? I'm still
hung up on the potential red herring of that date format.

Pat

Message
From: Todd [mailto: torr0101 (AT) gmail (DOT) com]
Sent: Thursday, November 17, 2005 9:53 PM
To: Tapestry users
Subject: Re: JBoss/Tomcat Validation Error Inconsistency

I totally forgot to mention the weirdest part, it works on Tomcat. I
don't
know what that means.

11/17/05, Konstantin Ignatyev <kgignatyev (AT) yahoo (DOT) comwrote:

That was my thought too but
SimpleDateFormat("MM/dd/yyyy") happily accepts
7/1/2001 at least in 1.5.0_05

Patrick Casey <patcasey (AT) adelphia (DOT) netwrote:
--
Did you try setting your minDate to '07/01/2005'? I
don't have time
to check, but I'm not sure if MM/DD/YYYY requires
the padding zero or not.

Pat

Message
From: Todd [mailto:torr0101 (AT) gmail (DOT) com]
Sent: Thursday, November 17, 2005 4:34 PM
To: Tapestry users
Subject: JBoss/Tomcat Validation Error
Inconsistency

We are evaluating Tapestry 4 at the company I'm
working for and we've run
into a strange error. Upon navigating to the page
in question we receive
an
error when the page attempts to load its
validators. Perhaps we've missed
something, or this is a true bug. I hope its the
former since this may
impact our decision making. Any ideas would be
greatly appreciated.

JDK5
Tapestry4-beta13
JBoss4.03SP1
Tomcat5

From the Exception page:

Error initializing validator 'minDate' (class
):
Unable to convert '7/1/2005'
to
type java.util.Date (for property minDate of
object

@67ec05):
Unparseable date:
"7/1/2005"; - nested throwable:
(java.text.ParseException : Unparseable
date:
"7/1/2005")

61</component62
63<component id="shippingDate" type="DatePicker">
64 <binding name="value"
value="shippingDate"/65 <binding
name="translator"
value="translator:date,pattern=MM/dd/yyyy"/66
<binding name="validators"
--
value="validators:required,minDate=7/1/2005,maxDate=12/31/2005"/>
67<binding name="displayName"
value="literal:Shipping Date"/>
68</component69
70<component id="desc" type="TextArea"71
<binding name="value"
value="desc"/>
>
>
>
>
>

To unsubscribe, e-mail:
tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail:
tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>
>
>
>

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org
>
>
>

Todd <torr0101 <atgmail.comwrites:

Well, we have not been able to determine what's happening. Apparently, no
one else can either. Unfortunately, this may mean that the powers that be at
my co will mandate that we consolidate our developer skills in Struts. I
fought hard on this one. To be taken down by a silly JBoss bugMaybe I can
steer us off JBoss ;). Wishful thinking.

I'll still use T4 as a hobby, but I think my company's apps would have
benefited from some of T4's performance minded features. We're bigger / much
more highly transactional than TSS. :(

Thanks for all your help!

Try running JBoss with this system property set:

eg.

Alternatively, create your own validator, which I think is what I will do.

The reason for the problem seems to be that HiveMind searches for
property editors and finds
DateEditor allows 3 formats, the first of which cpmes from the
system property if has been set.

Here's the JBoss code, from ,
where there's talk about its Locale issues.

String defaultFormat = System.getProperty(
"", "MMM d, yyyy");
formats = new DateFormat[] { new SimpleDateFormat(defaultFormat),
// Tue Jan 04 00:00:00 PST 2005
new SimpleDateFormat("EEE MMM d HH:mm:ss z yyyy"),
// Wed, 4 Jul 2001 12:08:56 -0700
new SimpleDateFormat("EEE, d MMM yyyy HH:mm:ss Z") };

Geoff

To unsubscribe, e-mail: tapestry-user-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: tapestry-user-help (AT) jakarta (DOT) apache.org