Message:
The following issue has been resolved as FIXED.
Resolver: fabrizio giustina
Date: Sun, 14 Nov 2004 10:08 AM
committed to cvs for rc2:
new requestURIcontext boolean attribute added to tabletag.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/DISPL-104
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DISPL-104
Summary: Need ability to disable prepending of context to the contents of
the requestURI attribute
Type: Improvement
Status: Resolved
Priority: Major
Resolution: FIXED
Original Estimate: 2 hours
Time Spent: Unknown
Remaining: 2 hours
Project: DisplayTag
Components:
Configuration
Fix Fors:
1.0 RC2
Versions:
1.0 RC2
Assignee: fabrizio giustina
Reporter: James Chamberlain
Created: Wed, 10 Nov 2004 10:07 PM
Updated: Sun, 14 Nov 2004 10:08 AM
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).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
displaytag-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
