1 Reply Latest reply on Jan 31, 2007 7:07 PM by Gavin King

    seam-gen vs. reference doc re Home setId()

    Leo Baschy Novice

      seam-gen with generate-entities keeps generating methods like setSomethingId() and getSomethingId() in

      public class SomethingHome extends EntityHome<Something> {
      
       public void setSomethingId(String id) {
       setId(id);
       }
      
       public String getSomethingId() {
       return (String) getId();
       }
      
       @Override
       protected Something createInstance() {
       Something result = new Something();
       return result;
       }
      }


      Then in the generated Something.page.xml there is

      <page>
       <param name="somethingFrom"/>
       <param name="somethingId" value="#{somethingHome.somethingId}"/>
      </page>


      In contrast, seam reference doc shows

      <param name="personId" value="#{personHome.id}"/>


      and no methods wrapping setId() and getId(), i.e. no setSomethingId() and no getSomethingId().

      Big Question: Is it safe to not have setSomethingId() and not have getSomethingId() in my own code, just use setId() and getId()?

      And, are setSomethingId() and getSomethingId() there for a good reason we should know?

      And, will setSomethingId() and getSomethingId() be removed in the future?