Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-3903

Conversational support should prevent seam-gen CRUD from losing information

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1.0.SP1, 2.1.1.GA
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Lets say you have 2 classes:

      class Parent{
      private Long id; private Integer version; private String name;
      private Set <Child> children;
      }

      and

      class Child{
      private Long id;private Integer version; private String name;
      private Parent parent;
      }

      with a typical one to many / many to one relationship (Parent.children.Child/Child.parent.Parent)

      So you want them to become @Entities and add the required @Annotations. Then you run seam-gen on them, and run you generated application:

      1. You click the Parent List menu option.
      2. You are presented with the page ParentList.seam that allows you search parents, or to create a new one.
      3. You click the Create parent button.
      4. You write a name for the parent: "Peter".
      5. You click "Save".
      6. You are presented with the page Parent.seam, that displays you newly persisted entity in a "read-only way"
      7. You click "Done"

      so far so good... but then

      1. You click the Child List menu option.
      2. You are presented with the page ChildList.seam that allows you search children, or to create a new one
      3. You click the Create child button.
      4. You are presented with the page ChildEdit.seam.
      5. You write a name for your new Child entity: "John"
      6. You decide that you want connect this new Child entity with a parent entity, and then you click "Select parent".
      7. You are presented again with ParentList.seam that allows you to "select" a parent.
      8. So, you select "Peter" by clicking in the "Select" link
      9. And you return to ChildEdit.seam, but the value for the name property of the Child is now LOST.

      I think seam-gen should be able to do this correctly (without losing the values in ChildEdit.seam).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                luxspes Francisco Jose Peredo Noguez
              • Votes:
                3 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: