3 Replies Latest reply on Mar 23, 2005 2:26 PM by Thomas Reimann

    Corrupted Field After EntityBean-Update

    Thomas Reimann Newbie

      Hello, we're using JBoss 4.0 with an Oracle 8i database.
      Our application (Swing-Client) uses SessionBeans in order to create/modify EntityBeans (2.x) and persist them via a configured XA Datasource using ojdbc14.jar.

      Now our problem is: creating an EntityBean works well, all data is saved correctly in our database. We do an update within a SessionBean-method. There we first get our Bean (with DOCTYPELocal dot = dotHome.findByPrimaryKey(vo.getID());), then
      we modify several attributes with the public setter-methods. Datatypes are int, String, Timestamp, boolean like
      dot.setNAME(vo.getName());
      dot.setVALIDFROM(vo.getValidFrom());
      dot.setTBCLASSNAME(vo.getTBClassName());
      dot.setDESCRIPTION(vo.getDescription());
      dot.setISTESTONLY(vo.isTestOnly());
      dot.setLASTMODIFIED(new Timestamp(System.currentTimeMillis()));
      dot.setLASTMODIFIER(vo.getModifier());
      dot.setMAXCOUNTSERIAL(vo.getMaxCountSerial());
      The ValueObject vo holds the correct values!
      After returning from our method the data of the TBCLASSNAME-field always is corrupted at the first 3 characters! TBCLASSNAME is a VARCHAR2(255) not null db-column.

      Every other action or Bean is working well, everything is (or seems to be) configured well. What may be the problem of the damaged field?
      Is it a JBoss-problem or may it be an Oracle-problem? When using DB2 everything works.

      Any help may be appreciated.
      Thomas