| Summary: | Creating a package from DRL breaks Atom-based RESTful interface | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Lukáš Petrovický <lpetrovi> | ||||||
| Component: | BRM (Guvnor) | Assignee: | Jervis Liu <jliu> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | BRMS 5.3.0.GA | CC: | brms-jira, jliu, mproctor | ||||||
| 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: | 2011-11-23 12:36:01 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 535001 [details]
The DRL being submitted
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. 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. |
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.