Skip to main content

JEAP 5&6 - 編碼設定問題 (Encoding)

FAQ 系列:

常常會有人問JBoss 的編碼要如何設定,在這裡整理一下我知道的部分:
編碼的部分,除了自己程式該定好要定好之外,設定的部分大致上分為三個部分:

1. 與資料庫DataSource 連接存取的編碼問題。
這個設定與你使用的JDBC Driver 很有關係,所以參數要對照使用的資料庫,會有所不同。
不同的資料庫會有不同的參數,如 Postgresql 是 charset=UTF-8

2. 網路資料傳輸
這裡與Tomcat 有關係,因為JBoss 的 Web Container 底層是Tomcat,所以設定的也與 Tomcat一樣設定分成兩個部分,

Get
修改Server上的 URI Encoding 即可。

JBoss EAP 6

到 domain 或是 standalone.xml 裡面增加參數:

<system-properties>
<property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8"/>
<property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true"/>
</system-properties>



JBoss EAP 5

JBOSS_INSTALL_PATH/jboss-as/server/xxx/deploy/jbossweb.sar 下的
server.xml 裡面修改

<!-- A HTTP/1.1 Connector on port 8080 -->
<Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}" connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8useBodyEncodingForURI="true"/>


Post 
需要加入 Encoding 的 Filter 才可以。 HTTP/1.1 這個通訊協定上有寫明,會以 header裡面Content-Type 欄位為判斷編碼的標準。可惜現在大部份的瀏覽器好像都沒有支援好好地把這個部分帶上去(尤其是遇到Ajax的時候)。

所以只好靠Filter 去強制把編碼的改為你想要的,
做法就是下載 filters.jar 檔案,放到你的WEB-INF/lib
然後修改 web.xml 增加新的filter,


<filter>
    <filter-name>setCharacterFilter</filter-name>
    <filter-class>filters.SetCharacterEncodingFilter</filter-class>
    <init-param>
        <param-name>encoding</param-name>
        <param-value>Big5</param-value>
    </init-param>
</filter>
<filter-mapping>
    <filter-name>setCharacterFilter</filter-name>
    <url-pattern>*</url-pattern>
</filter-mapping>



3. JVM 設定
這個可以改變 JVM default 讀寫檔案的編碼。 再啟動JBoss 的 conf 裡面加上參數:

JEAP 6

JBOSS_INSTALL_PATH/bin/standalone.conf 或是 domain.conf 裡面
加上 JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF8

JEAP 5

JBOSS_INSTALL_PATH/jboss-as/bin 下的 run.conf (Linux) run.conf.bat (Window)中
加上 JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF8

Comments

Popular posts from this blog

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.


2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.


So, now we know …