ClassName checking

From: Andrus (andru..bjectstyle.org)
Date: Mon Nov 18 2002 - 23:23:43 EST

  • Next message: Craig Miskell: "Re: ClassName checking"

    Maybe we are being too strict with the new class vs. entity name policies?

    For instance it is normal for CayenneModeler to have 2 ObjEntities with
    null class name during the editing. The only thing that must be unique for
    the modeler to work is "ObjectEntity name". Right now an attempt to create
    2 ObjEntities with different names but null class would give an exception
    shown below. I will file a bug report for this, but basically all we need
    is to remove extra strict checking for class name uniquness.

    Andrus

    CayenneModeler Info
    Version: 1.0b1-dev
    Build Date: November 18 2002
    Exception:
    =================================

    java.lang.IllegalArgumentException: org.objectstyle.cayenne.map.DataMap:
    Cannot add ObjEntity UntitledObjEntity2 because this DataMap already has an
    ObjEntity (UntitledObjEntity1) for the class null
            at org.objectstyle.cayenne.map.DataMap.addObjEntity(DataMap.java:249)
            at
    org.objectstyle.cayenne.modeler.action.CreateObjEntityAction.createObjEntity(CreateObjEntityAction.java:94)
            at
    org.objectstyle.cayenne.modeler.action.CreateObjEntityAction.performAction(CreateObjEntityAction.java:85)
            at
    org.objectstyle.cayenne.modeler.action.CayenneAction.actionPerformed(CayenneAction.java:172)
            at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1767)

    This archive was generated by hypermail 2.0.0 : Mon Nov 18 2002 - 23:23:01 EST