[OS-JIRA] Created: (WOL-743) Add concept of a "Common Class Name" in addition to the existing "Class Name" and "Client Class Name"

From: David Avendasora (JIRA) ("David)
Date: Thu Mar 06 2008 - 08:28:25 EST

  • Next message: David Avendasora (JIRA): "[OS-JIRA] Created: (WOL-744) Entity Modeler doesn't update Client Class Name or Client Class Property of subclasses"

    Add concept of a "Common Class Name" in addition to the existing "Class Name" and "Client Class Name"
    -----------------------------------------------------------------------------------------------------

                     Key: WOL-743
                     URL: http://issues.objectstyle.org/jira/browse/WOL-743
                 Project: WOProject/WOLips
              Issue Type: New Feature
              Components: wolips
        Affects Versions: WOLips 3.3.2.* (nightly build please specify)
             Environment: OSX 10.5.2, WO 5.4.1, Eclipse 3.2.2, WOLips 4953
                Reporter: David Avendasora

    Add the ability to define a "Common Class Name" to an EOModel in addition to Class Name and Client Class Name and have Veogen be able to generate the classes for any Entity that has it defined for. This will require changes to three existing WOLips plugins: Entity Modeler and EOGenerator UI and Veogen.

    ENTITY MODELER:
    Add a text field to the Advanced tab of the Entity properties identical to the Client Class Name field. The only time the Common Class Name would be used is if a Client Class Name is already defined. The idea is to have a Common version of an Entity that exists on both the server- and client- sides of a Java Client WO application.

    Add a checkbox to the Advanced tab of the attribute and relationship properties for "Common Class Property". This checkbox should only be active if the Client Class Attribute is checked, and a Common Class Name has been defined for the Entity. If both these criteria are true, then it would be required for attribute or relationship to be a "Common Class Property" so having it in the UI is more of a help for the user than a UI requirement as other attributes determine if it should be checked or not.

    The information from both of these UI changes could potentially be stored in the same place Client Side information is stored as it is a separate construct from the rest of the .plist file anyway.

    EOGEN UI
    Add a "Common" option in addition to the "Java" and "Java Client" options. (See issue 742 regarding making them radio buttons). This would then set a -javacommon flag instead of -java or -javaclient.

    VEOGEN
    Extend the existing logic that will use either the Class Name or Client Class Name value depending upon the -javaclient flag passed when Veogen is called.

    Also, extend Issue WOL-741 to also return only attributes and relationships flagged in the Model as Common Class Properties when Veogen is called with the -javacommon flag set.

    -- 
    This message is automatically generated by JIRA.
    -
    If you think it was sent incorrectly contact one of the administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa
    -
    For more information on JIRA, see: http://www.atlassian.com/software/jira
    



    This archive was generated by hypermail 2.0.0 : Thu Mar 06 2008 - 08:30:00 EST