You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Nick Gallardo (JIRA)" <ji...@apache.org> on 2009/06/27 01:07:47 UTC

[jira] Assigned: (WINK-10) unnecessary constructor validation on subresource

     [ https://issues.apache.org/jira/browse/WINK-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Gallardo reassigned WINK-10:
---------------------------------

    Assignee: Nick Gallardo

> unnecessary constructor validation on subresource
> -------------------------------------------------
>
>                 Key: WINK-10
>                 URL: https://issues.apache.org/jira/browse/WINK-10
>             Project: Wink
>          Issue Type: Bug
>            Reporter: Mike Rheinheimer
>            Assignee: Nick Gallardo
>         Attachments: patch.txt, patch_fixcandidate_01.txt
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.