Bug 817275

Summary:	Setting the ResourceResponse.HTTP_STATUS_CODE property does not modify the actual server response status code
Product:	[JBoss] JBoss Enterprise Application Platform 5	Reporter:	dpardon
Component:	distribution	Assignee:	Christopher O'Brien <cobrien>
Status:	CLOSED NEXTRELEASE	QA Contact:	Len DiMaggio <ldimaggi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.1.2
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-02 16:04:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dpardon 2012-04-28 14:30:09 UTC

Description of problem: Setting the ResourceResponse.HTTP_STATUS_CODE property does not modify the actual server response status code


Version-Release number of selected component (if applicable):


How reproducible:always


Steps to Reproduce:
1.Set the status code from a serveResource Portlet context: resourceResponse.setProperty(ResourceResponse.HTTP_STATUS_CODE,"500")
2.Invoke the above serveResource from a client-side ajax request
3.Inspect the status code received in a web browser console: the web browser always receives a status code "200" .
  
Actual results:"200"


Expected results:"500"
This code works for instance with Gatein 3.2, the expected status code is correctly received on client-side.

Additional info:. It is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=793073, closed 2 years ago.