I apologize for posting this in the wrong area yesterday.
====Original Question=====
We are still struggling with Jersey and resource routing. We can access
top-level resources with REST-ful requests, but when it comes to nested,
1-to-many object relationships (List<Class>), we can't get the routes to
work unless we create a "<Class>Resources" and
"<Class>Resource" implementation for each entity type. Seems like a lot
of work for a framework that was meant to simplify access to resources.
What approach are you guys taking? Do you try to minimize the number of
resource classes regardless of the actual number of resources, such as
in the Bookstore example, or, are you taking the opposite approach, such
as in the Storage-Service example, where for each entity there is a
Resources/Resource component?
------------------------------------------------------------------------------
This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications.
==============================================================================