Bug 905210 - Unable to Retrieve Alert Count
Summary: Unable to Retrieve Alert Count
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: REST
Version: 4.5
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.6
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
URL:
Whiteboard:
: 906158 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-28 20:57 UTC by Fernando Ribeiro
Modified: 2013-08-31 10:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-31 10:12:33 UTC
Embargoed:

Attachments (Terms of Use)

Description Fernando Ribeiro 2013-01-28 20:57:33 UTC 
Description of problem:

All attempts to retrieve the "alert/count" resource in the "application/xml" format fail with the following message:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rhqErrorWrapper>
  <message>Could not find MessageBodyWriter for response object of type: java.lang.Integer of media type: application/xml</message>
</rhqErrorWrapper>

No problems when using the "application/json" or "text/plain" formats.

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

4.5.1

How reproducible:

Steps to Reproduce:
1. Set the "Accept" header to "application/xml"
2. Retrieve the "alert/count" resource
3. Investigate stack trace
  
Actual results:

The error message mentioned in the description.

Expected results:

A proper response.

Additional info:

None
Comment 1 Heiko W. Rupp 2013-02-04 08:51:10 UTC 
In the past this method was only sending a single number, which was not valid for XML.
This has now been changed into

<value value="..."/>

Similar for the StringValue type

master 564ac02d1aa2c
Comment 2 Fernando Ribeiro 2013-02-04 15:58:34 UTC 
Great, thanks!
Comment 3 Heiko W. Rupp 2013-02-07 09:35:38 UTC 
*** Bug 906158 has been marked as a duplicate of this bug. ***
Comment 4 Heiko W. Rupp 2013-08-31 10:12:33 UTC 
Bulk close of old bugs in VERIFIED state.
Note You need to log in before you can comment on or make changes to this bug.