LTP: Possible backward incompatibility in DefaultPersistenceDelegate

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: P3
    • None
    • Affects Version/s: 6
    • Component/s: client-libs
    • None
    • generic
    • generic

      Scott Violet wrote:

      I think we should consider putting the code that dug out fields back :(
      The important thing is none of our public API relies on it, so that you can persist any public classes in a sandbox without reflection hacks. Developers that want to use LTP to persist private fields, should be allowed to, assuming they have the right permissions.

      Shannon Hickey wrote:

      What do you think about reverting part of your change for compatibility reasons? That is, favor field access if you have the right permissions, otherwise use getters.

            Assignee:
            Sergey Malenkov (Inactive)
            Reporter:
            Sergey Malenkov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: