We are using Spring / Hibernate on WebSphere Application Server for AIX. On my Windows machine, the problem does not occur - only when starting AIX. When a user logs in with an account number, if the prefix "0" matches their login ID, the application rejects the login. In a DB2 table, the column is of numeric type and there should be no problem converting '090 ....' to '90 ... '

Does anyone have such a problem? Both machines have Java v1.5.

To be more specific, the thread is FormView -> LoginValidator -> LoginController

In LoginValidator, the login value is null, prefixed with 0. Without 0, the value will be what it should be (but again, this is only on AIX - this is fine on two Windows environments). Here's a code snippet where object is null ..

public class LoginValidator implements Validator  {

    public boolean supports(Class clazz) {
    return Login.class.equals(clazz);
    }

    @SuppressWarnings("all")
    public void validate(Object obj, Errors errors) {
        System.out.println("Inside LoginValidator");
        Login login = (Login) obj;
        //null value
        System.out.println("Before conversion in Validator, store id = " 
              + login.getStoreId()); 
    }
}

      

        
        
        
      

    

I also wrote this short Java program to construct a Long from String and using the java binary that is packaged in WebSphere

public class String2Long {
    public static void main(String[] args){
        String a = "09012179";
        String b = "9012179";

        Long _a = new Long(a);
        Long _b = new Long(b);

        System.out.println(a + " => " + _a); //09012179 => 9012179
        System.out.println(b + " => " + _b); //9012179 => 9012179
        System.out.println("_a.equals(_b) " + _a.equals(_b)); //_a.equals(_b) true
    }
}

      

        
        
        
      

    

DECISION