Hello All,

I've attempted to make the switch to 5.3 and am facing an issue that
currently eludes me.  My attempts to use linksubmit leads to a javascript
error somewhere within the depths of the framework, with an error suggesting
that Tapestry is creating an incorrectly formated client redirect request.


Internally, the events are firing and all is well.  That is until Tapestry
attempts to perform the redirect behind my return value of <PageName>.class. 
(Or string literal "PageName", same result).

I've dug into the underlying javascript error as far as I can, and it comes
down to these types of initial errors:



The first is the result of trying to return <PageName>.class and the other
was a later attempt to do the same through a multizone return - just for
comparison, not the desired behavior.


The "offending code" is simply:




This return value is working for other buttons on the very same page, just
not working at the end of the line.  The "buttons" that work are
actionlinks, the one that is still failing is linksubmit.  I've tried some
variations on the submit theme and they all lead to the exact same error,
when attempting to return Index.class.


The application structure is as follows:
  An Index page that displays a grid of reports with edit actionlinks that
lead to a wizard.
  A wizard parent page with one default zone and three blocks to anchor the
three-page configuration process
  Three pages with Continue/Back/Cancel actionlinks & linksubmits.
  The wizard child pages advance forward using linksubmit. *The leading
pages return a reference to the next page(embedded component references),
the last (which fails) tries to return the index page class.*

*So in summary, linksubmit works fine when returning embedded components but
not a page class reference.  Actionlinks on the same pages CAN return page
class references with no trouble.*

The error is client-side and is present under both IE 8 and FireFox. 
Nothing but success is ever logged on the server.  Can anyone suggest where
I might start to sort this out?  What further information can I share that
would be helpful?

Thank you,
Ryan


--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/Badly-formed-JSON-string-error-generated-on-linksubmit-under-5-3-tp5033566p5033566.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

Reply via email to