Bug 755916 - Creating a package from DRL breaks Atom-based RESTful interface
Summary: Creating a package from DRL breaks Atom-based RESTful interface
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jervis Liu
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-22 12:08 UTC by Lukáš Petrovický
Modified: 2013-11-07 22:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-23 12:36:01 UTC
Type: ---

Attachments (Terms of Use)
HTTP communication in question (2.02 KB, text/plain)
2011-11-22 12:08 UTC, Lukáš Petrovický 		no flags Details
The DRL being submitted (1.47 KB, application/octet-stream)
2011-11-22 12:09 UTC, Lukáš Petrovický 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lukáš Petrovický 2011-11-22 12:08:43 UTC 
Created attachment 535000 [details]
HTTP communication in question

When trying to create a package from DRL using a Atom-based RESTful endpoint, I get the following exception in the server log, which results in an 500 Internal Server Error:

WARNING [org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper] (http-127.0.0.1-8080-1) WebApplicationException has been caught : org.apache.abdera.i18n.text.InvalidCharacterException: Invalid Character 0xfffd(?)

Both JSON/XML don't produce this exception.
Comment 1 Lukáš Petrovický 2011-11-22 12:09:16 UTC 
Created attachment 535001 [details]
The DRL being submitted
Comment 2 Lukáš Petrovický 2011-11-22 12:14:43 UTC 
Correction: the invalid character doesn't seem to be the root cause for this internal server error. But still, JSON and XML methods process the DRL just fine.
Comment 3 Lukáš Petrovický 2011-11-23 12:36:01 UTC 
The problem goes away when I explicitly specify that the server should run with UTF-8. Marking this as NOTABUG since this is a product of a mis-configuration on my side.
Note You need to log in before you can comment on or make changes to this bug.