One of the problems I found with JSR 168 portlets running in weblogic is that after a call to sendRedirect() in the processAction() method, the render method is still invoked, which doesn't make sense. I am using Spring Portlet MVC in BEA Weblogic Server 8.1.5.
I was thinking only to allow the render service to execute in the case that no redirect was issued by introducing following dispatcher servlet for extending from Spring Framework's dispatcher portlet implementation.
But it causes a side-effect to me. Whenever I use sendRedirect, for example from a JSP page, it invokes my next page's (SimpleFormController's) onSubmitAction(). I dont understand why onSubmitAction is being called when I use this new dispatcher and why not when I use Spring framework's dispatcher. Aparently it seems to me that as long as I am using Weblogic server for deploying my portal there should be no side-effect for the above mentioned code other than saving the extra render request.
May be I am with the portlet's work flow and hence need some thaughts from you.
Thanks in advance.
Ashik Uzzaman Lead Member of Technical Staff, Salesforce.com, San Francisco, CA, USA.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Spring portlets running in weblogic server