Use with Multibyte Environments
|
 |
 |
|
This document describes the known problems and some notes when using BEA AquaLogic Service Bus 2.1 under multibyte environment. The contents include:
This chapter describes the necessary preparation and some notes when using BEA AquaLogic Service Bus 2.1 under multibyte environment.
In order to display multibyte characters correctly in XQuery Mapper, you may need to do the font setting for Eclipse manually in some cases. In such cases, follow the next sequence: Open the menu Window - Preferences, and select General - Appearance - Colors and Fonts. From the list for colors and fonts displayed on the right side, select an element named xxxx Font, then click Change... button. In the dialogue that appears to show the character set, change the language to the appropriate one.
Although XQuery Mapper is based on Eclipse 3.1.1, it does not contain Eclipse language pack. The language pack can be downloaded from the following page. Note however that the operation of the software with language pack applied has not been verified by BEA.
http://www.eclipse.org/downloads/index.php
This chapter describes the important changes from v2.0 developed by the modifications or enhancements applied to BEA AquaLogic Service Bus 2.1.
In v2.1, the enhancement has been made to allow handling of query-strings encoded by any encodings. The enhancements on proxy service side and those on business side are separately explained below.
"Proxy service"
In v2.0, all query-strings that were URL-encoded were assumed to be encoded based on UTF-8 and therefore uniformly processed. In v2.1, any encodings can now be accepted by designating the request encoding at the definition of proxy service. The processing will be done in the following priority:
*1 Though Content-Type/charset attribute in HTTP header has the highest priority for the sake of implementation, HTTP header is considered to be rarely specified in GET method and thus request encoding will practically have the highest priority.
"Business service"
In v2.0, business service itself did not have the ability to do URL encoding. In v2.1, URL encoding function has been added to business service, and by using the specified request encoding at service definition for a base encoding, any encodings can now be handled. The processing will be done in the following priority:
*2 This means that whenever multibyte characters are included in a query-string, request encoding must be specified.
In v2.0, when any XML messages were handled in File or FTP transport, the request encoding for proxy setting and actual XML file encoding must always be the same. (See "Known Problems" in the old version for details.) In v2.1, this has been improved so that in the absence of request encoding, the encoding declaration in XML file is referred to be used. The processing priority in v2.1 will be as follows:
In v2.1, the encoding handlings for HTTP and e-mail transport have been reviewed and changed. The major changes are as follows. Also the encoding handlings for each transport in v2.1 are described in "BEA AquaLogic Service Bus Encoding Handling" for your reference.
This chapter describes the known problems with the use of BEA AquaLogic Service Bus 2.1 under multibyte environment.
When the product is installed under the directory containing multibyte characters, XQuery Mapper may not be started correctly.
Workaround: Replace the contents of the following file by the results of executing native2ascii command supplied by JDK. An example of execution (on Windows OS) is shown below.
% cd c:\bea\eclipse301\links % ren com.bea.wli.ide.mapper.feature.link com.bea.wli.ide.mapper.feature.link.bak % c:\bea\jrockit90_150_03\bin\native2ascii com.bea.wli.ide.mapper.feature.link.bak com.bea.wli.ide.mapper.feature.link
This chapter describes some restrictions under the multibyte environment for BEA AquaLogic Service Bus.
When an alert occurs where Send an alert to a JMS Destination is selected, the message sent will be BytesMessage type. (You cannot specify Text type.) The contents will be a byte array encoded by the encoding specified by Request encoding.
Multibyte characters cannot be used as delimiters in FormatBuilder.
In v2.1, the function to specify URL to obtain resources from external Service Bus Servers has been added. The URL format in this case will be as follows:
http://localhost:7021/sbresource?WSDL/[project name]/[folder name]/[resource name]
[project name] is the name of the project where the resource is registered
[folder name] is the name of the folder where the resource is registered
[resource name] is the name of the resource
When multibyte characters are used in any of project, folder or resource names for the resource you want to obtain, you must specify the character string that is URL encoded by UTF-8.
From v2.1, loading resources from zip files becomes possible by specifying .zip or .jar files. (Project Explorer - Create Resource - Bulk - Zipped Resources) This function does not work properly when any file name in the zip file contain multibyte characters. When multibyte file names are included, you must use jar files.
Following known problems are resolved in this release (v2.1). For the details of known problems, see the corresponding document of the old version.
|
|
|