This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Comment

Thanks for the reply.
But on the Web Flow References on cap. "Handling Ajax Requests" there is:

Spring Web Flow handles the optional rendering of fragments directly in the flow definition language through use of the render element. The benefit of this approach is that the selection of fragments is completely decoupled from client-side code, such that no special parameters need to be passed with the request the way they currently must be with the pure Spring MVC controller approach.

Comment

* The "modifica" transition takes you to a new view-state, which would mean a new screen and a different JSP right? So really the render fragment is probably irrelevant.

* You say that the request starts but stays on the same page. So did the request hit the server and the transition occur? The server side debug statements from Web Flow should give you a hint as to whether the transition has fired at all, succeeded or failed. Typically, if the transtion was fired and failed, then the flow would remain in the same view-state.

* If the transition did not fire at all, I would suspect a spring javascript setup issue. If you are using FireFox, turn on the Add-On and see what that tells you.

Comment

Agree with Ranjan..i think at this point best thing is to inspect the request/response using firebug or something else..if the AJAX call was successful you should be able to see the tiles html returning in the response of that POST call.

* The "modifica" transition takes you to a new view-state, which would mean a new screen and a different JSP right? So really the render fragment is probably irrelevant.

* You say that the request starts but stays on the same page. So did the request hit the server and the transition occur? The server side debug statements from Web Flow should give you a hint as to whether the transition has fired at all, succeeded or failed. Typically, if the transtion was fired and failed, then the flow would remain in the same view-state.

* If the transition did not fire at all, I would suspect a spring javascript setup issue. If you are using FireFox, turn on the Add-On and see what that tells you.

Agree with Ranjan..i think at this point best thing is to inspect the request/response using firebug or something else..if the AJAX call was successful you should be able to see the tiles html returning in the response of that POST call.

Comment

The 'body' fragment..how is it included in the JSP? Can you post the code? Make sure that the fragment is inside a html container (div or something) with a proper id assigned to it. The Ajax tiles resolver uses the html ids to figure out what needs to be replaced.

The 'body' fragment..how is it included in the JSP? Can you post the code? Make sure that the fragment is inside a html container (div or something) with a proper id assigned to it. The Ajax tiles resolver uses the html ids to figure out what needs to be replaced.

Comment

Please post the versions you are using for Spring Web Flow, Spring MVC and Tiles. If you are using Spring Web Flow 2.0.9 which in turn depends on Spring 2.5.6 how did you get around the TileConfigurer exception "Class org.apache.tiles.web.util.ServletContextAdapter not recognized a TilesApplicationContext"?

Please post the versions you are using for Spring Web Flow, Spring MVC and Tiles. If you are using Spring Web Flow 2.0.9 which in turn depends on Spring 2.5.6 how did you get around the TileConfigurer exception "Class org.apache.tiles.web.util.ServletContextAdapter not recognized a TilesApplicationContext"?