Sub-resource Locators (only supports returning of instantiated objects rather than classes, as MuServer does not instantiate classes for the API user).Resource methods implemented with GET, POST, PUT, DELETE, PATCH, OPTIONS, HEAD support.N/A Not applicable as only singletons supported 3.3 Resource Methods N/A There are no restrictions or requirements around constructors of your resources, as you instantiate your own Per request resources will never be implemented.Singletons where lifecycle is handled by the user.Following the principle of only supporting programaticĬonfigration, Mu-Server only supports singletons, so any constructors or fields are ignored by MuServer. Singletons, such amongst concurrent requests. The spec specifies two lifecycles for resource classes: per-request instantiation (via reflection) or Registered programmatically using the io. class. Such the .rs.core.Application class is not supported. The Mu Jax-RS implementation does not support classpath scanning or definition of Resource classes, and as The numbers and headers are taken directly from the Later, and which parts will never be implemented. This section goes into detail about which parts of the spec are implemented, which parts may be implemented
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |