WebLogic Workshop 8.1 SP6: Use with Multibyte Environments
Points of Caution for WebLogic Workshop 8.1
Known Problems
Corrected Problems
The necessary functions for use with multibyte environments have been implemented in WebLogic Workshop 8.1. WebLogic Workshop operates based on WebLogic Server. Accordingly, the existing restrictions of WebLogic Server apply to applications developed with Workshop.
WebLogic Server's Web service is compliant with the specifications for SOAP 1.1 and SOAP 1.2. HTTP/SOAP messages based on the SOAP1.1 specification have text/xml media type, and the encoding for these messages is handled according to RFC2376. HTTP/SOAP messages based on the SOAP 1.2 specification have application/soap+xml media type, and the encoding for these messages is handled according to RFC3023. The following are behaviors based on the RFC specification:
Interpretation of the HTTP/SOAP request character set is determined by the charset parameter of ContentType in the HTTP header. The encoding attribute is ignored for SOAP messages' XML declaration. When ContentType's charset parameter is abbreviated, it is regarded and processed as US-ASCII.
Interpretation of the HTTP/SOAP request character set is determined by the charset parameter of ContentType in the HTTP header. The encoding attribute is ignored for SOAP messages' XML declaration. When ContentType's charset parameter is abbreviated, the encoding attribute of the XML declaration is referred to. If neither ContentType's charset parameter nor the XML declaration's encoding attribute exists, it is regarded and processed as utf-8.
In order to make WebLogic Server 8.1 operate in compliance with this specification, WebLogic Workshop's operations also correspond to this. Consequently, you should make sure that clients using HTTP/SOAP to invoke Web services developed with WebLogic Workshop have ContentType's charset properly specified.
For WebLogic Server, HTTP/SOAP messages are generated with utf-8 as the default. At the time of generation, 'encoding=UTF-8' is added to the SOAP message's ContentType header.
Note: When WebLogic Server is started in an English locale (A LANG=C environment on UNIX), Only us-ascii characters can be used for SOAP messages. Other characters fall outside the guarantee of proper operation. Be sure to start WebLogic Server in a corresponding locale when multibyte characters will be used in a Web service.
When WebLogic Server has been started in an English locale and characters other than us-ascii are used, define the following startup options in the WebLogic Server startup script file. This generates messages in utf-8, even if the WebLogic Server is running on the English locale.
-Dweblogic.webservice.i18n.charset=utf-8
Note: Always use UTF-8 characters for the SOAP message when using a non-ASCII character.
Default Encoding: UTF-8
Specification Method: Specify with xml's encoding attribute
Example: <?xml version="1.0" encoding="UTF-8" ?>
Default Encoding: ISO-8859-1
Specification Method: Specify with META tag's content attribute.
Example: <META http-equiv="Content-Type" content="text/html;charset=Shift_JIS">
Default Encoding: ISO-8859-1
Specification Methods: Specify with page tag.
Example: <%@ page language="java" contentType="text/html;charset=UTF-8"%>
Specify with weblogic.xml
Example: <jsp-param>
<param-name>encoding</param-name>
<param-value>UTF-8</param-value>
</jsp-param>
* If encoding is specified in both, the page tag specification is given priority.
Default Encoding: ISO-8859-1
Specification Method: Specify with weblogic.xml
Example: <jsp-param>
<param-name>encoding</param-name>
<param-value>UTF-8</param-value>
</jsp-param>
Default Encoding: UTF-8
Specification Method: Specify with xml's encoding attribute
Example: <?xml version="1.0" encoding="UTF-8" ?>
Default Encoding: UTF-8
Specification Method: Specify with xml's encoding attribute
Example: <?xml version="1.0" encoding="UTF-8" ?>
Default Encoding: UTF-8
Specification Method: Specify with xml's encoding attribute
Example: <?xml version="1.0" encoding="UTF-8" ?>
Default Encoding: UTF-8
Specification Method: Specify with xml's encoding attribute
Example: <?xml version="1.0" encoding="UTF-8" ?>
Files are read/written with Java VM default encoding. Encoding specification is not performed.
The default encoding for Web applications is UTF-8.
If you wish to create applications with other encoding, you can specify [Tools] - [Application Properties] - [Encoding].
This setting is reflected in the value for weblogic-application.xml's webapp.encoding.default parameter.
For webapp.encoding.default parameter, see J2EE Default Encoding Specification.
When multibyte characters are used in XScript files, reading of the XScript file will fail, and the build cannot be done. (CR138066)
Multibyte characters cannot be included in HTML files by Workshop IDE when the meta tag's Content-Type is not specified.
Avoidance Measures: Static include files containing multibyte characters can be edited with Workshop IDE by using a JSP fragment file (extension:jspf) instead of an HTML file, and specifying the encoding to be saved in the weblogic.xml file.
According to J2EE's JSP specification, a compile error occurs when a statically included file is JSP and the page directive's contentType is specified in both the JSP for the include source and the JSP for the include destination.
Avoidance Measure: Both of the two avoidance measures below are valid, but for WebLogic Workshop, 1. is recommended.
<!-- Comment the jspServlet param out to go back to weblogic's jspc -->
<!-- <jsp-param>
<param-name>jspServlet</param-name>
<param-value>weblogic.servlet.WlwJSPServlet</param-value>
</jsp-param> -->
<jsp-param>
<param-name>backwardCompatible</param-name>
<param-value>true</param-value>
</jsp-param><br>
Workshop IDE cannot include multibyte characters in HTML files that have optional attributes within the <html> element (example: <html version="1.0">).
In WebLogic Workshop, character encoding is not properly handled for WSDL files or URI references to Web services within JWS controls. Because of this restriction, multibyte characters cannot be included in Web service project names, folder names, JWS filenames, etc.
Error messages are displayed in English when performing compiles for java/jsp/jws/jpd/jdx/dtf/xq, etc. in the development environment.
English help is not added to the existing help (language other than English) even when installing third-party Workshop IDE extension functions having only English help.
The name of the folder in which the Japanese-version online help is stored has been changed from "ja" to "ja_JP" in versions after Service Pack 3. For this reason, when installing online help that comes with extension functions created for SP2, the following procedure is necessary.
By doing this, the extension function's help files are added to the Japanese version online help files, and at the same time, the indexes for the table of contents and search are merged.
DBScripter's online help is bundled in SP2 format with Workshop IDE as a sample, and it is installed in the following directory.
\weblogic81\samples\workshop\ExtensionDevKit\ControlDevKit\DBScripter\docs\help\doc\ja
In order to merge this online help with IDE's online help, it is necessary to change the above folder name as follows.
\weblogic81\samples\workshop\ExtensionDevKit\ControlDevKit\DBScripter\docs\help\doc\ja_JP
Due to the dialog size restriction, parts of the explanation text cannot be displayed when new applications are created if the window font type is not "Default", and the font size is not "10".
Avoidance Measures: Although there is no operational problem when all of the explanation text cannot be read, if you wish to display all of the explanation text, set the window font's type and size as mentioned above.
When WebLogic Server is started from the WebLogic Workshop menu's [Tools | WebLogic Server | Start WebLogic Server], the console screen starts, but this console (xterm) cannot handle multibyte characters. Because of this, if WebLogic Server is started in a multibyte-capable locale, messages output from the server result in invalid characters.
Avoidance Measure: Manually start WebLogic Server from a console compatible with multibyte characters such as kterm.
The Schema Project Properties Build setting cannot be set to an abnormal value. Doing so displays an error message and closes Workshop IDE. (CR200460)
You cannot install when names containing multibyte characters are set for BEA Home or the Installation Directory. Doing so results in garbled characters in the Workshop IDE Server Properties JDK Home and WebLogic Home paths.
The Workshop IDE "Immediate" Debug Window cannot display multibyte characters. (CR129930)
When a message with http-xml, jms-soap, or jms-soap12 protocol contained multibyte characters, an error resulted because the message could not be parsed, but this has been corrected with 8.1SP3.
When Web service messages containing multibyte characters were encrypted via WS-Security, an error would result when the message was parsed, but this has been corrected in 8.1 SP3.
In the Tuxedo Control Function's help, only the English version was distributed for BEA Tuxedo Control in WebLogic Workshop 8.1 SP2, but in the WebLogic Workshop 8.1 SP3 release, the Japanese version of help has been included, and it can be found in the following directory.
%WL_HOME%\workshop\help\doc\ja_JP\Tuxedo
On WebLogic Servers with the weblogic.http.URIDecodeEncoding option, there was a problem inputting multibyte characters in the Web Service Test Browser, but this has been corrected in 8.1 SP4. (CR129900)
The Entity Bean build failed when created from a database using multibyte characters in the column name, but this has been fixed in 8.1 SP4. (CR122203)
When a Japanese name was used for the application or project name, a ServletException was invoked upon deploying the application with previous versions. However, this problem has been fixed in 8.1SP6. (CR238604)
When debugging the page flow using a Japanese application name, an error message indicating "specified path is not found" appeared on the test browser with previous versions. However, this problem has been fixed in 8.1SP6.
