[
https://issues.apache.org/jira/browse/CXF-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369249#comment-15369249
]
J. Fiala commented on CXF-6965:
-------------------------------
h2. General CXF issues:
h3. Automatic bean-Validation only supported starting with 1.1
Currently there is Bean-Validation support starting with 1.1.
https://cwiki.apache.org/confluence/display/CXF20DOC/ValidationFeature
However, older JEE servers (like e.g. Jboss EAP 6) only allow Bean-Validation
1.0 and this can't easily be changed there (because it is usually one of the
core modules).
It would be great to have support for @Valid starting with 1.0!
Especially as nested parameters could also be supported there for
bean-validation!
Currently this has to be implemented manually for JEE containers with
bean-validation 1.0.
h3. @QueryParam always needs to define a value
@QueryParam("myparam") myparam
It would be great to have the value optional if the name is identical to the
parameter name (see e.g. Spring-REST @RequestParam).
> CXF Swagger2Feature does not correctly support QueryParam("") and DataHandler
> -----------------------------------------------------------------------------
>
> Key: CXF-6965
> URL: https://issues.apache.org/jira/browse/CXF-6965
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Reporter: Sergey Beryozkin
> Priority: Minor
> Fix For: 3.2.0, 3.1.8
>
>
> See
> https://github.com/swagger-api/swagger-codegen/issues/2017#issuecomment-230426728
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
