[
https://issues.apache.org/jira/browse/WINK-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724687#action_12724687
]
Mike Rheinheimer commented on WINK-10:
--------------------------------------
Also, I'm not tied to the fix suggested by fixcandidate_01 patch. Please
review and critique or change if needed -- or send comments and ideas my way.
Also, FYI, I had a two test failures and two test errors in common, but they
were unrelated to this patch. The failures were due to the position of the
namespace declarations in some XML being checked in an assert. I did not check
on the errors, but it looked like NPEs coming from a missing application
validator object?? Anyway, this fix patch didn't cause those. :)
> 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
> 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.
