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.MINIFICATION_ENABLED, "false");
It couldn't handle a custom js file I created to abstract some prototype
methods

2. I annotated my login page event methods instead of depending on
annotation on the validate method and method-name convention on the success
method !
Before:
    private Object onSuccess() {
        return Index.class;
    }

    @OnEvent(component = "loginForm", value = "validateForm")
    private void validate() {

After:
@OnEvent(component = "loginForm", value = EventConstants.SUCCESS)
    private Object onSuccess() {
        return Index.class;
    }

    @OnEvent(component = "loginForm", value = EventConstants.VALIDATE)
    private void validate() {/*...*/}

3. I made my web.xml the exact as the the one generated by the maven
archetype. Before, I had some context parameters in it related to the app
version, gzip-compression, white space removal...etc. I removed all that.

I believe the main reason for this mess is that we migrated to 5.3 by just
changing the class-path or something. I think we need to download the
archetype for the new version and then move our files "carefully" trying to
care as much as possible for what is set as defaults in the new archetype.

I don't know if I used the term "archetype" correctly but I just mean the
template project downloaded by maven !
I hope this works for someone.

On Wed, Dec 14, 2011 at 4:18 PM, Michael Gentry <mgen...@masslight.net>wrote:

> 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
> <mart.schnei...@gmail.com> 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.
> >
> > --
> > View this message in context:
> http://tapestry.1045711.n5.nabble.com/5-3-JSONArray-Error-while-submitting-forms-tp5011831p5069614.html
> > Sent from the Tapestry - User mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>


-- 
*Regards,*
*Muhammad Gelbana
Java Developer*

Reply via email to