QUESTION: Have any best practices been cited for creating Jersey REST
services with emphasis on using Eclipse and package/class layout?
ENVIRONMENT: jersey-bundle-1.0.1-SNAPSHOT, jersey-multipart, jaxb-api,
jab-impl, stax-api, jsr311-api-1.0
CONTEXT
For our normal web application development, we have a standard
skeleton project that is preconfigured with necessary project
dependencies, common Spring configuration files, and whatever is
needed. We are trying to determine a similar skeleton for our Jersey
REST services. This raises several key questions:
1. Is there a particular package layout that is best suited to Jersey
REST services?
2. When should REST services be split up into multiple classes versus
aggregated resources?
3. Should a REST service that consumes and produces XML have a single
XSD that covers both request and response XML data or separate XSDs?
I appreciate any assistance and insights!
Sincerely,
Andrew
--
Andrew Feller, Analyst
LSU University Information Services
200 Frey Computing Services Center
Baton Rouge, LA 70803
Office: 225.578.3737
Fax: 225.578.6400