I am curious to know, how beneficial are STRUTS for a portal architecture e.g, WebSphere Portal or any other vendor? How do they fit in together? I know about STRUTS Portlets but it is just develop and deploy STRUTS application as a portlet, which ofcourse can be done on a regular J2EE server. Is there a real advantage to using STRUTS in Portal tools, When and Why?
If John Carnell or any body can respond, I appraciate it.
I have some experience with Struts and Oracle's Portal Server. I had a great deal of difficulty intergating Struts in OPS because OPS did a great deal of manipulation of the URL when building out its page.
Everything that goes through Struts goes through the ActionServlet. However, when integrating into a portal, the redirect of the page to a Servlet is just one of usually many URL calls. So, I could never integrate a Struts app to stay in the "portal" window beyond the first screen of the applications.
John Carnell - Senior Engineer, Genesys PureCloud Division
Author of Spring Microservices in Action