Suggestion on usage of Struts Portlet Bridge for jboss portl

[chetan_aggarwal_in]

Hi,

Following is the scenario:

I have a web application built using Struts 1.3. Now we want to convert it to a portal like application.

Following are choices:

1. Write portlet classes and copy code from Action Classes and add to portlet classes.
- Advantage : Complete life cycle is portal based.
- Disadvantage : Struts application is no longer needed.

2. Use a struts portlet bridge
- Advantages - Still will be able to use Action classes with portal like look and feel.
- Disadvantage - I am not getting very comfort feeling with bridge as i am not sure full set features, industry practises. I have also read about certain limitations regarding (not able to user request.getParameter() style in JSP pages...)


Please share your thoughts/suggestions/experiences of using bridges.

Thanks and Regards,
Chetan

[vegastyl]

We are running a number of Struts apps in Portal and do not have any significant problems. We stick to using the Struts tag libraries however and do not use code directly in the JSPs. If you are under time constraints, converting this app to a portlet shouldn't be too difficult. If you have the time for a rewrite, however, using something like Seam might be a better choice.