[10:27:04 CDT(-0500)] <EricDalquist> well 4.0.6 is cut but found a bug in one of the last minute merges
[10:27:09 CDT(-0500)] <EricDalquist> so time for 4.0.6.SR1
[10:37:31 CDT(-0500)] <drewwills> any reason not to use string 3.1.x in a portlet? are we already doing that elsewhere?
[10:37:50 CDT(-0500)] <EricDalquist> only requirement is that you're on up4
[10:39:25 CDT(-0500)] <drewwills> roger
[10:39:52 CDT(-0500)] <drewwills> (working on the 286 port of the email-preview)
[10:40:04 CDT(-0500)] <EricDalquist> cool
[10:56:09 CDT(-0500)] <athena> yes, i'd recommend using spring 3.1
[11:01:15 CDT(-0500)] <drewwills> athena is there a good example of sending a non-200 HTTP status in case of an error in a ReaourceRequest? (and would that be appropriate)
[11:01:41 CDT(-0500)] <athena> should be pretty straightforward
[11:01:50 CDT(-0500)] <athena> just need to set the response code
[11:01:54 CDT(-0500)] <athena> like you would for a servlet
[11:02:19 CDT(-0500)] <EricDalquist> well if your forwarding to a servlet
[11:02:36 CDT(-0500)] <EricDalquist> on as plain ResourceResponse: http://portals.apache.org/pluto/portlet-2.0-apidocs/javax/portlet/ResourceResponse.html
[11:02:37 CDT(-0500)] <athena> take a look at the ResourceRequest API
[11:02:54 CDT(-0500)] <EricDalquist> note the HTTP_STATUS_CODE constant
[11:03:10 CDT(-0500)] <athena> yep
[11:03:16 CDT(-0500)] <athena> and status codes are all the same, of course
[11:06:31 CDT(-0500)] <drewwills> (should have just looked at the javadoc instead of digging through examples)
[11:18:28 CDT(-0500)] <drewwills> set it as a string? surprising
[11:18:46 CDT(-0500)] <EricDalquist> yeah, just an API limitation
[11:18:57 CDT(-0500)] <EricDalquist> but it has been tested
[11:19:04 CDT(-0500)] <EricDalquist> you can actually set any HTTP header via setProperty