A developer on my team is trying to use both full html and xml views
in his application.  He is running into a problem after the first
transition from a full html view into a full xml view.

The transition to to the first xml view displays correctly.  The form
on this page is displays a postback to the /app/foo.xml view id.
However, when the form is submitted it seems the restoreView of clay's
viewHandler gets confused.  It logs that it is restoring the
/app/bar.html view id which had previously transitioned to
/app/foo.xml instead of restoring /app/foo.xml.  The result is a page
not found error.

Although I haven't seen the combination used in the clay usecase app I
am assuming that the combination is possible from the documentation.
Does anyone know why transitioning from one full xml view to another
would be a problem given that the first came from a full html view?

Thanks,
Ryan

Reply via email to