[WINK-10] unnecessary constructor validation on subresource

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 0.1
• Component/s: Common, Server
• Assignee: Nick Gallardo
• Reporter: Michael Rheinheimer
• Created: 26/Jun/09 18:04
• Updated: 15/Jul/09 16:07
• Resolved: 15/Jul/09 16:07

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.

Issue Links

• blocks: WINK-97 new integration tests: context, uriinfo, etc
• is part of: WINK-83 Singletons should be injected