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

Yes I read the guide - not the latest one, but on 3.0.7 since we are working on that one.
Would the AbstractWizardFormController the proper approach? I see this is deprecated and there is only the @Controller annotation. So if there is now other possibilities I will give this a try.

Unfortunately for my use case this doesn't help since in one of my view it returns a ModelAndView with an AbstractPdfView added.
Once the PdfView (open/save dialog) appears it does not return back to the workflow allowing to show my next view .

It seems there is no solution for that and the user has no manually go to the next page? Or in my case to refresh the current page?

Comment

Ok. I moved away from using AbstractView and AbstractWizardFormController since I can put the PDF download logic also in the Controller.

Though some things needs to be considered:
- it is only allowed to use the writer. Because later WebSphere complains an "OutputStream already obtained" because it uses the writer and my controller uses the outputstream. And both are not allowed to be used in the same request and response.
- in the meanwhile I use the writer (which of course doesn't make sense since I have to write bytes/PDF) to check whether the application can deal with my normal ModelAndView (for refreshing current page) while the PDF dialog appears.