Paul Sandoz wrote:
>
> The only solutions i can think of are:
>
> 1) Jersey supports an @Required annotation; or
> 2) Exposes a lower-level abstraction of MultivaluedParameterExtractor
> 3) One can utilize AOP method-level interceptors to support @Required
> and check for a null value.
>
I would assume that requiring a parameter is a common enough use case that
many people would want to use it, although if this issue hasn't come up
before perhaps I'm mistaken. If it is a common use case, option 1 makes the
most sense to me.
If there are situations in which users want to do more complex things with
parameter validation, then perhaps some kind of abstraction layer like you
suggested would be useful.
Paul Sandoz wrote:
>
> Could you log an issue so we can track this?
>
I found this
http://wikis.sun.com/display/Jersey/Accessing+Jersey+Issues+Tracker+using+Eclipse+IDE
wiki page about using the Issue Tracker through Eclipse. But it looks like
I have to create an account on Collabnet, install an Eclipse plugin and also
create an account on Java.net. I wasn't able to install the plugin due to
some subversion dependencies that I can't update because of our
behind-the-times set up in the office.
Is there a web based version of the Issue Tracker?
Cheers,
Dirk
--
View this message in context: http://n2.nabble.com/Required-parameters-on-a-Resource-tp3446928p3466240.html
Sent from the Jersey mailing list archive at Nabble.com.