[
https://issues.apache.org/jira/browse/CXF-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909212#action_12909212
]
Sergey Beryozkin commented on CXF-2986:
---------------------------------------
Actually - my analysis is incomplete.
if we have ?option then we should end up with a collection containing a single
empty value which would be consistent with what I said above thus having an
empty collection as requested by this JIRA is indeed correct , when no a given
query key exists...will try to fix it this week...
> sets null instead of empty List/Set/SortedSet when value isn't in query string
> ------------------------------------------------------------------------------
>
> Key: CXF-2986
> URL: https://issues.apache.org/jira/browse/CXF-2986
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 2.2.10
> Reporter: Brad Cupit
> Priority: Minor
>
> CXF sets a null collection, rather than an empty one, when the query param
> isn't in the request
> Example:
> @GET
> @Path("/stuff")
> public Response get(@QueryParam("option") Set<String> options) { ... }
> and http://localhost:8080/stuff is called (but ?option=abc is not on the
> query string), then options will be null, but it should be an empty Set
> The javadocs in @DefaultValue says:
> If this annotation is not used and the corresponding metadata is not present
> in the request, the value will be an empty collection for List, Set or
> SortedSet
> this seems similar to CXF-1675
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
