Page History

...

1. Considerations
   1. overview
      This is a major schema Change. so upgrade support is necessary for those with Live systems.
   2. Scope
      Using eca's provide two way updates.
      1. If the data is in the legacy format put in the new format
      2. if the data is in the new format put in the legacy format till the conversion process it complete.
2. Upgrade process
   1. What will be effected
      • PostalAddress entity
      • ContactMechTypes
      • ContactMech
   2. how to change
      • change PostalAddress from package-name="org.ofbiz.party.contact" to package-name="org.ofbiz.party.postal.
      • Create and move from PostalAddress.toName and PostalAddress.attnName contact Mech for each field and link to postal address.
      • remove PostalAddress.toName and PostalAddress.attnName
      • add PostalAddress.AddresslinesID PostalAddress.DirectionsLinesID PostalAddress.PremiseID with one to many relationships.
      • Code services to keep PostalAddress.Address1 PostalAddress.address2 in sync with the new entities. put in package-name="org.ofbiz.party.postal
      • code eca's to all new services when the PostalAddress is updated. if I understand david these should be EECA's

1. list