You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bridges-dev@portals.apache.org by "Thorsten Berger (JIRA)" <br...@portals.apache.org> on 2005/10/09 20:16:47 UTC

[jira] Created: (PB-14) unable to post unicode characters in struts bridge

unable to post unicode characters in struts bridge
--------------------------------------------------

         Key: PB-14
         URL: http://issues.apache.org/jira/browse/PB-14
     Project: Portals Bridges
        Type: Bug
  Components: struts  
    Versions: 0.4    
    Reporter: Thorsten Berger


Using struts forms to post unicode characters (e.g. german umlauts) results in a String with garbage characters.
I urgently need this to work for my portal, so I tracked down the problem and found it to be specific to Jetspeed.
I logged a JIRA issue for jetspeed, but maybe this problem also exists when using the struts bridge with another portal.

The main cause is decoding request parameters twice in o.a.j.engine.servlet.ServletRequestImpl (line 157):

                     try
                        {
                            paramValues[i] = new String(paramValues[i].getBytes("ISO-8859-1"), getCharacterEncoding());
                        }
                        catch (UnsupportedEncodingException e)
                        
This is called firstly by jetspeed itself (providing parameters to the StrutsPortlet) and secondly by the Struts RequestProcessor (to populate the form bean). It's clear that this results in garbage characters.
However, I don't think it's a struts bridge bug. For further explanation and a solution for Jetspeed, see JS2-376 (request parameter encoding problem)

Regards, Thorsten


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org


[jira] Commented: (PB-14) unable to post unicode characters in struts bridge

Posted by "Thorsten Berger (JIRA)" <br...@portals.apache.org>.
    [ http://issues.apache.org/jira/browse/PB-14?page=comments#action_12332621 ] 

Thorsten Berger commented on PB-14:
-----------------------------------

Ate,

as this has been resolved in Jetspeed and no one else seems to have this problem with another portal, this issue can be closed.

Regards, Thorsten


> unable to post unicode characters in struts bridge
> --------------------------------------------------
>
>          Key: PB-14
>          URL: http://issues.apache.org/jira/browse/PB-14
>      Project: Portals Bridges
>         Type: Bug
>   Components: struts
>     Versions: 0.4
>     Reporter: Thorsten Berger

>
> Using struts forms to post unicode characters (e.g. german umlauts) results in a String with garbage characters.
> I urgently need this to work for my portal, so I tracked down the problem and found it to be specific to Jetspeed.
> I logged a JIRA issue for jetspeed, but maybe this problem also exists when using the struts bridge with another portal.
> The main cause is decoding request parameters twice in o.a.j.engine.servlet.ServletRequestImpl (line 157):
>                      try
>                         {
>                             paramValues[i] = new String(paramValues[i].getBytes("ISO-8859-1"), getCharacterEncoding());
>                         }
>                         catch (UnsupportedEncodingException e)
>                         
> This is called firstly by jetspeed itself (providing parameters to the StrutsPortlet) and secondly by the Struts RequestProcessor (to populate the form bean). It's clear that this results in garbage characters.
> However, I don't think it's a struts bridge bug. For further explanation and a solution for Jetspeed, see JS2-376 (request parameter encoding problem)
> Regards, Thorsten

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org


[jira] Closed: (PB-14) unable to post unicode characters in struts bridge

Posted by "Ate Douma (JIRA)" <br...@portals.apache.org>.
     [ http://issues.apache.org/jira/browse/PB-14?page=all ]

Ate Douma closed PB-14.
-----------------------

    Resolution: Invalid

This was an bug in Jetspeed which has been resolved there

> unable to post unicode characters in struts bridge
> --------------------------------------------------
>
>                 Key: PB-14
>                 URL: http://issues.apache.org/jira/browse/PB-14
>             Project: Portals Bridges
>          Issue Type: Bug
>          Components: struts
>    Affects Versions: 1.0
>            Reporter: Thorsten Berger
>
> Using struts forms to post unicode characters (e.g. german umlauts) results in a String with garbage characters.
> I urgently need this to work for my portal, so I tracked down the problem and found it to be specific to Jetspeed.
> I logged a JIRA issue for jetspeed, but maybe this problem also exists when using the struts bridge with another portal.
> The main cause is decoding request parameters twice in o.a.j.engine.servlet.ServletRequestImpl (line 157):
>                      try
>                         {
>                             paramValues[i] = new String(paramValues[i].getBytes("ISO-8859-1"), getCharacterEncoding());
>                         }
>                         catch (UnsupportedEncodingException e)
>                         
> This is called firstly by jetspeed itself (providing parameters to the StrutsPortlet) and secondly by the Struts RequestProcessor (to populate the form bean). It's clear that this results in garbage characters.
> However, I don't think it's a struts bridge bug. For further explanation and a solution for Jetspeed, see JS2-376 (request parameter encoding problem)
> Regards, Thorsten

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: bridges-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: bridges-dev-help@portals.apache.org