Hi All, There were TWO Carbon JIRA's raised pertaining to the $subject [1] & [2] concerning Governance Registry being unable to browse resource with UTF-8 names and content.
These were are currently being assigned to me, and I manged to fix them
locally (not committed to trunk). Following is how I can break down the
fixes made.
The reference I used is here [3].
*Handle GET Requests:*
Updated the Connector definitions in *
<GREG_HOME>/repository/conf/tomcat/catalina-server.xml* as follows,
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="9763"
. . .
*URIEncoding="UTF-8"*/>
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="9443"
. . .
*URIEncoding="UTF-8"*/>
*Handle POST Requests:*
*
*
I overcame this by introducing a servert filter (refer to the attached
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.java) to *
org.wso2.carbon.tomcat.ext* bundle, this sets the character encoding in the
*<GREG_HOME>/repository/conf/tomcat/carbon/WEB-INF/web.xml* by configuring
the servel filter in it as follows,
<web-app . . .>
. . .
<filter>
<filter-name>*CharsetFilter*</filter-name>
<filter-class>*org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter*
</filter-class>
<init-param>
*<!-- specifying the encoding -->*
<param-name>requestEncoding</param-name>
<param-value>UTF-8</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>*CharsetFilter*</filter-name>
<url-pattern>*/**</url-pattern>
</filter-mapping>
. . .
</web-app>
*Handling the JSPs:*
Also, I had to update all the *.jsp pages found in *
org.wso2.carbon.registry.resource.ui* bundle to add the pageEncoding
attribute.
<%@ page contentType="text/html;charset=UTF-8" language="java" *
pageEncoding="UTF-8"* %>
I haven't committed any of the above changes, I would like to know your
feedback on this, since this I feel affects at Carbon level.
[1] https://wso2.org/jira/browse/REGISTRY-879
[2] https://wso2.org/jira/browse/REGISTRY-882
[3]
http://stackoverflow.com/questions/138948/how-to-get-utf-8-working-in-java-webapps
Thanks,
Fazlan
On Thu, May 31, 2012 at 8:31 PM, Senaka Fernando <[email protected]> wrote:
> Hi Pradeep,
>
> I don't understand what you mean by "reference model". What we explained
> is was working in the last release and not working in current trunk. If
> some fix or improvement broke it, it needs to be added back. It might be a
> fix in our code or Tomcat, but it needs to be fixed or its a regression
> issue and hence an L1.
>
> If your question was about whether the same worked in the last release if
> you deployed Carbon as a webapp on standalone Tomcat, Ajith can validate
> that for you.
>
> Thanks,
> Senaka.
>
>
> On Thu, May 31, 2012 at 2:47 PM, Pradeep Fernando <[email protected]>wrote:
>
>> Hi,
>>
>> hold on!.it wasn't a blind delete. we ported some code, removed some.
>> AFAIU, we introduced these wrapper classes to overcome Appserver
>> specific serialization issues.
>>
>> Right now, our reference model is, standalone tomcat. So what is the
>> behaviour with standalone tomcat.
>>
>>
>> --Pradeep
>>
>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Thanks,
Fazlan
CharacterSetFilter.java
Description: Binary data
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
