jsr-283
  1. jsr-283
  2. JSR_283-273

Reason for adding Session.getLocks()

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: spec
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      273

      Description

      i was wondering why

      Lock[] Session.getLocks()

      was added to the specification.
      unfortunately i couldn't find any discussion within this issue tracking system
      nor a hint in the f2f-notes regarding this new method.

      i can see the potential use case, that a session wants to determine, which
      Node(s) it locked before. but is it more than convenience?

      thanks for clarification
      angela

        Issue Links

          Activity

          Hide
          Peeter Piegaze added a comment -

          wb change

          Show
          Peeter Piegaze added a comment - wb change
          Hide
          Peeter Piegaze added a comment -

          wb changed

          Show
          Peeter Piegaze added a comment - wb changed
          Hide
          anchela added a comment -

          hi peeter,

          what do you mean by "wb change" and why did you resolve this issue for
          later?

          if it has been decided (or discussed) somewhen, that Session.getLocks() should
          go into the session interface, this issue can simply be closed.

          if however it was just added for no good reason, i think it should be discussed.
          and if there is no argument for keeping the method or if nobody really feels
          affected to it or if it has been added for convenience only i would prefer to
          have it removed again.

          regards
          angela

          Show
          anchela added a comment - hi peeter, what do you mean by "wb change" and why did you resolve this issue for later? if it has been decided (or discussed) somewhen, that Session.getLocks() should go into the session interface, this issue can simply be closed. if however it was just added for no good reason, i think it should be discussed. and if there is no argument for keeping the method or if nobody really feels affected to it or if it has been added for convenience only i would prefer to have it removed again. regards angela
          Hide
          stefan_guggisberg added a comment -

          as per F2F decision in Basel, Sept 07:

          at least one implementor can't implement it, so remove the getLocks method

          Show
          stefan_guggisberg added a comment - as per F2F decision in Basel, Sept 07: at least one implementor can't implement it, so remove the getLocks method
          Hide
          anchela added a comment -

          remove 'Later' status

          Show
          anchela added a comment - remove 'Later' status
          Hide
          anchela added a comment -

          start issue for processing.

          Show
          anchela added a comment - start issue for processing.
          Hide
          Peeter Piegaze added a comment -

          RC17: Removed from src and spec

          Show
          Peeter Piegaze added a comment - RC17: Removed from src and spec

            People

            • Assignee:
              jsr-283-issues
              Reporter:
              anchela
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: