Page Comparison

[10:42:09 CST(-0600)] <Bananobot> I'm trying to get a portlet to read the client's GET request parameters to select the output. But it seems as though the output is being cached too heavily, so when I feed it a different value in the URL, the output isn't updated. Is there a way for the portlet to work around this without forcing all navigation to use POST?
[11:10:36 CST(-0600)] <holdorph> Bananobot, there are two things you need to look at. One, make sure the portlet.xml doesn't have caching turn on.
[11:11:16 CST(-0600)] <holdorph> Two, you must use the portlet container to create any URLs that the user can click on. Hand crafting URLs is not supported by the portlet spec
[11:11:46 CST(-0600)] <holdorph> that means, for example if you are using a .jsp file, using the portlet tag library and creating renderUrls
[11:11:49 CST(-0600)] <Bananobot> Caching is turned on in portlet.xml, but I would think that if a GET parameter is specified, targeting that specified portlet, the portal should know that it can't use the same cache as a request with a different GET parameter..
[11:12:30 CST(-0600)] <holdorph> you're right, assuming your following the second consideration i mention
[11:12:39 CST(-0600)] <Bananobot> Okay, I'll look into that
[11:13:45 CST(-0600)] <EricDalquist> If a portlet is targeted by a URL generated by the portlet API for that portlet the cache will be invalidated
[11:13:46 CST(-0600)] <Bananobot> Actually, hm... I'm using Spring's form tags, and I'm setting the "path" attributes for the form controls. The generated "name" attributes in the HTML are just being set to the literal value, rather than something translated for the portal..
[11:14:00 CST(-0600)] <EricDalquist> also all forms for portlets must use POST
[11:14:07 CST(-0600)] <EricDalquist> and the path must be set to a portlet API generated URL
[11:14:43 CST(-0600)] <Bananobot> EricDalquist: Why do they all have to be POST? The form isn't to post content, it's to request a resource.