Performs a basic check on abstract resources. Validity check populates a list of potential issues with the given resource. The issues are divided into two categories: fatal and non-fatal issues. The former type prevents the resource to be deployed and makes the whole web application deployment fail.
To check a single resource class, one could use the {@link IntrospectionModeller#createResource(java.lang.Class)} methodto get an abstract resource model. {@link AbstractModelValidator#validate(com.sun.jersey.api.model.AbstractModelComponent)}method then populates the issue list, which could be then obtained by the {@link AbstractModelValidator#getIssueList()}. Unless you explicitly clear the list, subsequent calls to the validate method will add new items to the list, so that you can build the issue list for more than one resource. To clear the list, you may want to call {@link AbstractModelValidator#cleanIssueList()} method. @author Jakub Podlesak (jakub.podlesak at oracle.com)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|