Today I faced the problem of storing Japanese characters in ResourceBundles (Struts framework/Java). The Japanese characters are in UTF-8 encoding (which is ofcourse variable-length encoding scheme) are 3 bytes. So they cant be obviously stored in TXT files which uses some Latin based encoding schemes (which consider characters are 2 bytes). So only way to store them is store them as encoded utf data. To convert to utf encoded format I used the tool native2ascii which comes with JDK.
Before Conversion
今すぐ予約
After conversion using native2ascii
\u4eca\u3059\u3050\u4e88\u7d04
Thursday, February 03, 2005
Monday, January 31, 2005
Tomcat 5.5.7 Released
Apache Jakarta Tomcat 5.5.7 Stable Release
To me 5.5.x looks like a overhaul to previous version and should be more stable Tomcat 5.0.
Apache Jakarta Tomcat 5.5.7 Stable Release
To me 5.5.x looks like a overhaul to previous version and should be more stable Tomcat 5.0.
Friday, July 09, 2004
Monday, June 28, 2004
JAAS implements a Java version of the Pluggable Authentication Modules (PAM) framework. Sun Microsystems created PAM for its Solaris operating system; with JAAS, PAM is now available in a platform-independent form.
The main purpose of PAM is to allow application developers to write to a standard authentication interface at development time, leaving the decision of which authentication technologies will be used (and how they will be used) up to the system administrator. PAM allows new authentication techniques or technologies to be more easily added to existing applications. Likewise, an authentication policy can be changed by updating the login.config file, rather than rewriting the entire application.
JDK 1.4 comes with the following PAM modules. We'll use one of them and also practice writing two of our own later in the tutorial:
com.sun.security.auth.module.NTLoginModule
com.sun.security.auth.module.NTSystem
com.sun.security.auth.module.JndiLoginModule
com.sun.security.auth.module.KeyStoreLoginModule
com.sun.security.auth.module.Krb5LoginModule
com.sun.security.auth.module.SolarisSystem
com.sun.security.auth.module.UnixLoginModule
com.sun.security.auth.module.UnixSystem
The main purpose of PAM is to allow application developers to write to a standard authentication interface at development time, leaving the decision of which authentication technologies will be used (and how they will be used) up to the system administrator. PAM allows new authentication techniques or technologies to be more easily added to existing applications. Likewise, an authentication policy can be changed by updating the login.config file, rather than rewriting the entire application.
JDK 1.4 comes with the following PAM modules. We'll use one of them and also practice writing two of our own later in the tutorial:
com.sun.security.auth.module.NTLoginModule
com.sun.security.auth.module.NTSystem
com.sun.security.auth.module.JndiLoginModule
com.sun.security.auth.module.KeyStoreLoginModule
com.sun.security.auth.module.Krb5LoginModule
com.sun.security.auth.module.SolarisSystem
com.sun.security.auth.module.UnixLoginModule
com.sun.security.auth.module.UnixSystem
Tuesday, October 07, 2003
Subscribe to:
Posts (Atom)