Wink
  1. Wink
  2. WINK-10

unnecessary constructor validation on subresource

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 0.1
    • Component/s: Common, Server
    • Labels:
      None

      Description

      Because a subresource does not have to conform to the JAX-RS rules regarding constructors, the code should not be enforcing these rules on subresources.

      Attached is a testcase to demo the problem. The hack I used to confirm that the runtime is enforcing the constructor rules on the subresource was to comment out the "continue L1;" call in AbstractMetadataCollector.parseConstructors

      The fix will be to make the AbstractMetadataCollector aware of what type of resource it is operating on; top-level resource vs. subresource.

      I'll work on this.

      1. updated-patch-gallardo.txt
        1 kB
        Nick Gallardo
      2. patch_fixcandidate_01.txt
        22 kB
        Mike Rheinheimer
      3. patch.txt
        8 kB
        Mike Rheinheimer

        Issue Links

          Activity

            People

            • Assignee:
              Nick Gallardo
              Reporter:
              Mike Rheinheimer
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development