DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29502>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29502 Extend the Struts framework to allow Struts application to be executed within a JSR168 portlet. ------- Additional Comments From [EMAIL PROTECTED] 2004-06-10 20:52 ------- I'm not up to speed on Jetspeed, but I want to point out something that I think Pradeep should check out in light of his original proposal. Ate, perhaps you can comment on whether you've been tracking this for your current implementation. Even before Struts 2.0, we could make progress on decreasing Struts' dependencies on the Servlet API. (This is tricky, to be sure, but we shouldn't give up yet!) Specifically, the struts-chain project is designed so that one could probably put in a few chain commands that adapted the portlet context into a Struts "environment," possibly diminishing the need for a ServletObjectsFactory. It would definitely change the part of the proposal discussing RequestProcessors. It would be fair to say that it may be a little time before a Struts 1.3 release based on the struts-chain processor is ready, so if you wanted this to have more wide adoption sooner, you might need to tolerate some things about Struts 1.2. But do note that after 1.2.1 is cut, I'm hoping to join in on making the struts-chain processor the default request processor. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
