I have been using displaytag < 1.0rc1 in a portlet application for some time. I am testing 1.0rc1 to see if it will be a smooth upgrade. I have had numerous issues with params being forwarded in the past and I am real happy that an option has been added to the 1.0rc2 code in CVS so I don't have to maintain my own version which does the same.

That said the change to the requestURI in 1.0rc1 is really going to mess things up for me. Since I don't rely on params being forwarded, I need to add them to the url by passing a custom requestURI in the table tag attribute. I use a portlet actionURL tag to create the url for the requestURI. It always starts with a "/", but I cannot have it prepending the URL with the Context. The context where the portlet is installed is not the same as the portal's.

Would it be possible to make this behavior configurable via a tag attribute? Normally I would recommend it be changeable via a property file instead, but I have to deploy in a WebLogic portal where all the portlets run in one big webapp (really screwed up if you ask me) and other portlets might require the behavior to work as default.

Can you help me out?


- James



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel

Reply via email to