public void doLogon(IRequestCycle cycle){
      System.out.println("Get username: "+this.getUsername());
      Author au=this.getUserDao().findAuthor(this.getUsername(),this.getPassword());
      if(null!=au){
         Visit v=(Visit)this.getVisit();
         v.setUsername(au.getAuthorName());
         v.setPassword(au.getAuthorPassword());
         cycle.activate("main");
      }else{
         this.setErrorMessage("³ö´íÁË:error in logon!");
         cycle.activate("logon");
      }
   }

CharScanner; panic: ClassNotFoundException: org.hibernate.hql.ast.HqlToken

BEA Weblogic issues
Hibernate3 uses ANTLR for the new query parser. Unfortunately BEA Weblogic includes a version of ANTLR in the system classpath which will be loaded before any application libraries and, because Weblog doesn't seem to support propert class loader isolation, will not see the Hibernate classes in the application's context. BEA seems to solve this issue by prefixing package names, but the distributed ANTLR doesn't have this prefix. Another source for this issue is the usage of Class.forName() in ANTLR itself.

Until both parties have solved these issues we can only provide workarounds: Place all your Hibernate and dependent libraries on the application server's boot classpath or use the old query parser as described above.

The Hibernate Team has send a fix for this issue to the ANTLR developers, and it should be included in the next release. We'll distribute this new version with a minor release of Hibernate in the next few weeks or months. For now we distribute a patched version of ANTLR with Hibernate 3.0 which uses the context classloader instead of Class.forName().

The Weblogic classloading and/or package prefix issues are unfortunately out of our reach. We encourage you to contact your BEA support representative.