Unable to add Surf to an existing Spring MVC web application

[chrislack]

Just saw your post - looks like we posted about the same time with roughly the same ideas except yours is more complete and works!

Are you thinking of forwarding the Spring MVC request to a Surf webscript to populate a portion of the page or a rss feed or something? I think you'd probably want to just go via a URL that Surf services so that you get all of the Surf processing. If you tried to just have a Spring MVC View Resolver go to Surf's view layer direct it would miss out things like the Surf interceptors. One of these populates the context object on which lots of the webscript stuff depends.

My View Resolver suggestion was for going the other way - from Surf to a Spring JSP but I'm not sure it would work... especially given the other thread about using JSP.

[BillyBacon]

Nice! What are the odds!

Correct, I was thinking that after a SpringMVC controller did it's processing we could maybe forward the request to Surf to populate a portion (what we are calling a standard component) of the page. I'm not entirely sure we want to do this or if it even makes sense to.

Thanks again for the ideas Chris, you were a tremendous help!

[chrislack]

No problem, I'm a bit of a Spring Surf fan. Talking of Struts which you mentioned earlier my current customer isn't using Surf but instead Struts 1 with the best bits removed, combined with things like EJB 2

[manikantha11]

Hi All,

Could you please provide me source code which uses spring surf and spring MVC together. As its very helpful to learn.
Thank you all,

[bodydesign]

I was using website stage May MVC remote controls with some of my Search websites (which also had Search Webscript remote controls for some of the elements on the page). I can think of a number of guidelines you could go:
1. Create a personalized made PageViewResolver training (check the Search resource for the normal one) which ahead to your JSPs. This obviously still has your May MVC sessions being prepared by Search. The training has two techniques - one to choose if it will manage the particular URL and one to come back a Search PageView item. The PageView could then somehow provide the JSPs without too much Search engagement....my understanding all gets a bit imprecise here... so not 100% sure and this would need some testing and might not be the best way etc.
2. Individual servlet dispatchers for May MVC and Search if its possible to keep the perspective xml separate which is where I think you began. I don't know why that wasn't functioning but it seems like it should.
3. Erm.... there may be a another way of using JSP making which bypasses much of the Search products. I'll have a think when I'm more awaken.