[gatein-issues] [JBoss JIRA] (GTNPORTAL-2496) Invalid encoding in gadget source not handled properly

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/GTNPORTAL-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710659#comment-12710659 ] 

RH Bugzilla Integration commented on GTNPORTAL-2496:
----------------------------------------------------

Peter Palaga <ppalaga at redhat.com> made a comment on [bug 803115|https://bugzilla.redhat.com/show_bug.cgi?id=803115]

@theute: No, this is not a regression. Setting target to 5.2.x.

@mcupak: Thank you for your consequent checks. I could track the problem down to JCR not including the charset in the response's Content-Type. I am going to ask JCR people if that can be fixed.
                
> Invalid encoding in gadget source not handled properly
> ------------------------------------------------------
>
>                 Key: GTNPORTAL-2496
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-2496
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>             Fix For: 3.4.0.Final
>
>
> Originally reported by Miroslav Cupák on 2012-03-13 21:51:51 EDT:
> Description of problem:
> Invalid encoding in gadget source leads to SAXParseException and an "Unknown error" message. The exception should be caught and a proper error message should be displayed.
> More specifically, there are two different error messages you can get depending on how you mess up the encoding. You can either run into "org.xml.sax.SAXParseException: Content is not allowed in prolog." (with e.g. "UTF-16" as the encoding) or "org.xml.sax.SAXParseException: Invalid encoding name" (with e.g. "UsadfTF-8" as the encoding).
> Steps to Reproduce:
> 1. Sign in as "root".
> 2. Go to "Group" > "Administration" > "Application Registry" and switch to "Gadget".
> 3. Try to create a gadget with an invalid encoding as described above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira