anonymous wrote : Your portlet would have to be packaged along with a servlet that handles the AJAX requests. Presumably your rendered JSPs would have to have some sort of refresh mechanism that users can click on to trigger an AJAX request.
Doesn't the portal render out a whole page at a time? How would I construct a servlet to give me just a single portlet's response (including decorators)? I wouldn't want to to strip out the extra content in a servlet because I can do that with javascript just as well, and thus I could theoretically achieve some kind of AJAX-style behavior without writing a servlet. So how would you implement such a servlet? BTW - with regards to the separate inter-portlet-communication thread that is arising here - keep in mind that you aren't necessarily going to end up with JSR168 portlets if you use an API designed specifically to allow you to communicate with portlets in JBoss - what you will end up with is JBoss Portlets that happen to use the JSR168 API's too. If you would like to be able to deploy any portlets you develop to under JSR 168 portal platforms (say Jetspeed 2, BEA Portal, etc...), then using the PortletSession and possibly the PortletContext are your 'portable' solutions to inter-portlet-communication. Regards. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907259#3907259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3907259 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
