A couple of things you should be aware of is: - You cannot use result types that require full control of the response object (e.g. rendering PDFs, images, charts etc). To do that, you must dispatch a request to a servlet instead. - You should be aware of the lifecycle and the phases of a portlet, and how they apply to links and forms in a Struts 2 portlet to avoid weird state behaviour. - You should be aware of portlet modes, and how they are mapped to namespaces in the Struts 2 framework. - You can't create your own links. You should only create links using the form and url tags. - Ajax have some limitations. - You can't generate a complete HTML document, only what's between the <body> tags of what would have been a regular web app.
Otherwise, you should be able to build it as a normal Struts 2 app. Nils-H On 3/14/07, tom tom <[EMAIL PROTECTED]> wrote:
We were alble to successfully deploy the struts 2.06 portlet sample on our portal container which is uPortal. What we want to know is Can we write the portlet applications simillar to the Struts 2.0.6 web applications(not portlets). Does Struts 2.0.6 portlets got limitations compared to the normal struts 2.0.6 application. Are there any DOs and DONT'S Please us know before we beging the work. Thanks ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
