Sent
Should anyone else want to try as well, please let me know...
Best regards,
Jacob
-Original Message-
From: Muhammad Gelbana [mailto:m.gelb...@gmail.com]
Sent: Wednesday, June 13, 2012 4:15 PM
To: Tapestry users
Subject: Re: [5.3] JSONArray Error while submitting forms
This is
: Thursday, June 14, 2012 1:26 AM
To: Tapestry users
Subject: Re: [5.3] JSONArray Error while submitting forms
A shot in the dark... another thing to try would be to increment the value of
the SymbolConstants.APPLICATION_VERSION symbol in your app module class
(normally AppModule.java
; Best regards,
>> Jacob
>>
>>
>> From: Muhammad Gelbana [mailto:m.gelb...@gmail.com]
>> Sent: Tuesday, June 12, 2012 5:06 PM
>> To: Poder, Jacob
>> Subject: Re: [5.3] JSONArray Error while submitting forms
>>
>> The only I did beat this was to use
ards,
> Jacob
>
>
> From: Muhammad Gelbana [mailto:m.gelb...@gmail.com]
> Sent: Tuesday, June 12, 2012 5:06 PM
> To: Poder, Jacob
> Subject: Re: [5.3] JSONArray Error while submitting forms
>
> The only I did beat this was to use maven (as i'm used to) to create the
> skele
description to
reproduce and see if it could be a Tapestry bug???
Best regards,
Jacob
From: Muhammad Gelbana [mailto:m.gelb...@gmail.com]
Sent: Tuesday, June 12, 2012 5:06 PM
To: Poder, Jacob
Subject: Re: [5.3] JSONArray Error while submitting forms
The only I did beat this was to use maven (as
Are you packaging your application using maven ? Try to make a clean build
(mvn clean)
On Tue, Jun 12, 2012 at 11:02 AM, Poder, Jacob wrote:
> Aha, the error ONLY occurs when the form is submitted by pressing return!
>
> So, 3 conditions to make this happen:
> 1) IE8/9 browser
> 2) Submit form u
Aha, the error ONLY occurs when the form is submitted by pressing return!
So, 3 conditions to make this happen:
1) IE8/9 browser
2) Submit form using return button
3) A validator (e.g. required/min/max) must have failed immediately before
Best regards,
Jacob
T5.3.3
-
hear the result?
Best regards,
Jacob
-Original Message-
From: Muhammad Gelbana [mailto:m.gelb...@gmail.com]
Sent: Monday, June 11, 2012 5:22 PM
To: Tapestry users
Subject: Re: [5.3] JSONArray Error while submitting forms
How did this start happening ? Did you just modify the class pat
How did this start happening ? Did you just modify the class path from
pointing to an older tapestry version to a newer one ?
Please state your app configuration. Things like:
*SymbolConstants.MINIFICATION_ENABLED*
On Mon, Jun 11, 2012 at 9:43 AM, Poder, Jacob
wrote:
> Hi,
>
> I'm having the pr
Thanks Michael, much appreciated, as I would never have guessed that! I will
give it a try.
Peter
- Original Message -
From: "Michael Gentry"
To: "Tapestry users"
Sent: Friday, 3 February, 2012 6:31:49 PM
Subject: Re: [5.3] JSONArray Error while submitting forms
gt; From: "Muhammad Gelbana"
> To: "Tapestry users"
> Sent: Tuesday, 10 January, 2012 9:11:23 PM
> Subject: Re: [5.3] JSONArray Error while submitting forms
>
> When I had this problem, clearing the cache didn't solve it. I had move all
> my classes\tml\reso
Re: [5.3] JSONArray Error while submitting forms
When I had this problem, clearing the cache didn't solve it. I had move all
my classes\tml\resources manually from my old tapestry project to a new
tapestry 5.3.1 skeleton project.
On Tue, Jan 10, 2012 at 5:32 PM, Lenny Primak wrote:
> I
When I had this problem, clearing the cache didn't solve it. I had move all
my classes\tml\resources manually from my old tapestry project to a new
tapestry 5.3.1 skeleton project.
On Tue, Jan 10, 2012 at 5:32 PM, Lenny Primak wrote:
> I think clearing the cache is not the full answer to this pro
I think clearing the cache is not the full answer to this problem.
There aught to be a better answer. Perhaps versioning the formdata element?
On Jan 10, 2012, at 10:13 AM, Gunnar Eketrapp wrote:
> I have already answered to this.
>
> The clearing of the cache seems to have solved my problem a
I have already answered to this.
The clearing of the cache seems to have solved my problem as well.
2012/1/10 Muhammad Gelbana
> Shouldn't Gunnar decide first if the issue should be closed or not ?
>
> On Tue, Jan 10, 2012 at 12:08 AM, Bob Harner wrote:
>
> > Is anyone still seeing this proble
Shouldn't Gunnar decide first if the issue should be closed or not ?
On Tue, Jan 10, 2012 at 12:08 AM, Bob Harner wrote:
> Is anyone still seeing this problem after clearing the browser cache?
> If not, we'll be able to close TAP5-1777.
>
> On Mon, Jan 9, 2012 at 9:52 AM, Michael Gentry
> wrote
Is anyone still seeing this problem after clearing the browser cache?
If not, we'll be able to close TAP5-1777.
On Mon, Jan 9, 2012 at 9:52 AM, Michael Gentry wrote:
> Hi Josh (and others),
>
> I was using Chrome and then tried my app in Safari and it worked in
> Safari. I then cleared my Chrome
Hi Josh (and others),
I was using Chrome and then tried my app in Safari and it worked in
Safari. I then cleared my Chrome cache and it started working in
Chrome, too. I suspect some JS was being cached somewhere that was
making things incompatible. Hope that helps others, too.
Thanks,
mrg
Hi Josh,
Better late than never? :-)
Here is with 5.3.1, which still didn't help:
t:formdata:H4sIAJ2RvUsDMRjG3x4ofkAHncTFoWO5q6IguggiKpRSPCe39C6eKbkkJu
1dw5OgrOj/4OTH DUwbH/i4vOgrlWKOU61E5JHt43z4/nefqEua4L1UsVEO
Is4i1GGeY7eVCl90QHXKSyQTddhIrlIpE1Gg4kDpyiSLBFXWRKGpQZztuIDXlrGXPWElBBRr3hI
I know this may sound useless but I'm just trying to help. I have tried to
do 3 things but I'm not quite sure which actually made this work for me:
1. I noticed an exception thrown by the javascript compressor whenever I
access the login page so I disabled it
configuration.add(SymbolConstants.MINI
Hello,
We also had the error appear in Jetty. Didn't try Tomcat/etc.
Unfortunately, we've been under a multiple-deploy crunch and didn't
really have time to explore the issue and went back to 5.2.6 for now.
Thanks,
mrg
On Mon, Dec 12, 2011 at 4:21 PM, mart.schneider
wrote:
> I have the same
On Mon, Dec 12, 2011 at 10:21 PM, mart.schneider
wrote:
> I have the same problem with Tapestry 5.3. Strangely, everything works fine
> while running my application in Jetty. I only get the error when running
> inside Tomcat. It occurs on all of my forms.
If you really want this issue to be solv
I have the same problem with Tapestry 5.3. Strangely, everything works fine
while running my application in Jetty. I only get the error when running
inside Tomcat. It occurs on all of my forms.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/5-3-JSONArray-Error-while-submit
A copy of the request would be helpful. It seems like in the first
report the "t:submit" parameter was coming back as a quoted string,
but later reports seem to have it fixed by checking if it's empty.
On Wed, Dec 7, 2011 at 1:58 PM, Gunnar Eketrapp
wrote:
> I have no idea! For sure there must be
I too am using chrome... My form is simple, 5 radio buttons and a submit button.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
I have no idea! For sure there must be something special with your case, my
case and Seamus case.
Or perhaps we are the only one using form's :-)
My browser is Chrome ...
I have coded around the problem for now by using my own 5.3.1 as reported
above.
2011/12/7 Muhammad Gelbana
> But how com
But how come this issue isn't causing enough noise !!! We must have
something common in our code that is very unique !!!
I can't figure out what could be unique in my login page !!..2 fields
form...1 submit button...1 event handling method !
On Wed, Dec 7, 2011 at 9:24 PM, Gunnar Eketrapp
wrote:
I just created an issue for this
https://issues.apache.org/jira/browse/TAP5-1777
I would love to see a fix for this otherwise I must go into production with
my own brewed 5.3.1
or revert to 5.2.6.
Thanks in advance,
Gunnar Eketrapp
2011/12/7 Muhammad Gelbana
> Facing the same issue !! I didn't
Facing the same issue !! I didn't expect that to happen and it will take
sometime to revert back to 5.2.6 :(
I cleared my browser's cache and made sure I'm using tapestry's latest
css\js...still having the same problem with a form that has nothing to do
ajax !
On Wed, Dec 7, 2011 at 8:36 AM, Gunn
if (raw != null && *!raw.isEmpty() &&*
new *JSONArray(raw)*.getString(1).equals
This seems to have solved the problem.
I made this fix in *Form.java, Submit.java* and *LinkSubmit.java*. Built
and installed my own 5.3.1 in my local maven repo.
Rebuilt my project and now I can logi
A possible solution would be to make a code around in the method
isFormCancelled() in Form.java.
/Gunnar
if (raw != null &&
new *JSONArray(raw)*
.getString(1).equals(InternalConstants.CANCEL_NAME))
{
return true;
}
if
Anyone have a solution to this. I have a form which I dont believe is making
use of any ajax (unless tapestry is and I dont know about it I am using the
current T5.3 release) and I get this error. When inspecting my page in
chrome and looking at the resources I see prototype 1.7 and scriptaculous
1
Yes, there was a conflict with an older version of prototype / scrupulous.
After removing these, things started to work.
HTH,
/Serge
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/5-3-JSONArray-Error-while-submitting-forms-tp7018161p7065209.html
Sent from the Tapestr
For some reason my form submission crashes in the the method
isFormCancelled in Form.java.
The call to JSONArray(raw) crashes since raw is an empty string which is
not allowed.
I must have missed something with 5.3 and form handling that is
incompatible with 5.2.6.
Does anyone have a clue what h
Did you solve this? I am getting the same right now.
I just started my second attempt with 5.3 after Taha pointed out a
solution for my user type translators.
But now I am looking at these JSONArray stack traces ...
Perhaps there is a snapshot release of 5.3 that I can try with !?
2011/11/21 S
35 matches
Mail list logo