Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0 RC2
-
Fix Version/s: 1.0 RC2
-
Component/s: Configuration
-
Labels:None
-
Application server:Tomcat 5.0.28
Description
The problem for me is that a change was introduced with 1.0rc1 that made it
so that if the requestURI begins with a "/" the context will be prepended to
whatever is in the requestURI.
So I am using this in a portlet environment, the portlet is in it's own webapp called /ExamplePortlet and the portal itself is in another webapp called /portal. When a user is accessing the portal all requests go through the /portal webapp, a user would never directly goto the /ExamplePortlet webapp when accessing that portlet. I fill in the requestURI attribute with the output from the <portlet:actionURL/> tag which creates a long portal specific url which always starts with a "/". Displaytag seeing this long url beginning with a "/" prepends it with /ExmaplePortlet so I end up with http://localhost:8080/ExamplePortlet/portal/..... Instead of http://localhost:8080/portal/.....
This change is noted in the change notes for 1.0rc1.
I am sure this functionality helps folks out who are not doing portlet work, but it really causes problems ina portal environment. I can partially get arounf this problem in 1.0rc2 by always using a empty requestURI and adding the excludeParams="*" so the parameters don't just keep appending to the previous request.
It would be great if this behavior was configurable through a table tag attribute, so I can co-exist with other portlets that need the default behavior in the weblogic portal (since weblogic portal is one big webapp I can't do it via a properties file).
so that if the requestURI begins with a "/" the context will be prepended to
whatever is in the requestURI.
So I am using this in a portlet environment, the portlet is in it's own webapp called /ExamplePortlet and the portal itself is in another webapp called /portal. When a user is accessing the portal all requests go through the /portal webapp, a user would never directly goto the /ExamplePortlet webapp when accessing that portlet. I fill in the requestURI attribute with the output from the <portlet:actionURL/> tag which creates a long portal specific url which always starts with a "/". Displaytag seeing this long url beginning with a "/" prepends it with /ExmaplePortlet so I end up with http://localhost:8080/ExamplePortlet/portal/..... Instead of http://localhost:8080/portal/.....
This change is noted in the change notes for 1.0rc1.
I am sure this functionality helps folks out who are not doing portlet work, but it really causes problems ina portal environment. I can partially get arounf this problem in 1.0rc2 by always using a empty requestURI and adding the excludeParams="*" so the parameters don't just keep appending to the previous request.
It would be great if this behavior was configurable through a table tag attribute, so I can co-exist with other portlets that need the default behavior in the weblogic portal (since weblogic portal is one big webapp I can't do it via a properties file).