[jira] [Commented] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350671#comment-15350671
]
Sergey Beryozkin commented on CXF-6941:
---
Neal,
FYI, I'm not seeing where PHP supports it, apparent;y it is listed as one of
the options, but a replicating the field names is typed as being the best
approach. I can also see from the link you posted some people expressing
concerns about collapsing the values.
The following does not mention this option either:
https://en.wikipedia.org/wiki/Query_string
(Web Forms)
I've asked earlier, do you have some clients in production that basically must
do "a=1,2,3" to support a multi-value 'a' ? If you are migrating to JAX-RS and
use either JAX-RS 2.0 client or CXF WebClient/proxies, then you'd see
a=1&a=2&a=3".
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350671#comment-15350671
]
Sergey Beryozkin edited comment on CXF-6941 at 6/27/16 9:07 AM:
Neal,
FYI, I'm not seeing where PHP supports it, apparently it is listed as one of
the options, but a replicating the field names is typed as being the best
approach. I can also see from the link you posted some people expressing
concerns about collapsing the values.
The following does not mention this option either:
https://en.wikipedia.org/wiki/Query_string
(Web Forms)
I've asked earlier, do you have some clients in production that basically must
do "a=1,2,3" to support a multi-value 'a' ? If you are migrating to JAX-RS and
use either JAX-RS 2.0 client or CXF WebClient/proxies, then you'd see
a=1&a=2&a=3".
was (Author: sergey_beryozkin):
Neal,
FYI, I'm not seeing where PHP supports it, apparent;y it is listed as one of
the options, but a replicating the field names is typed as being the best
approach. I can also see from the link you posted some people expressing
concerns about collapsing the values.
The following does not mention this option either:
https://en.wikipedia.org/wiki/Query_string
(Web Forms)
I've asked earlier, do you have some clients in production that basically must
do "a=1,2,3" to support a multi-value 'a' ? If you are migrating to JAX-RS and
use either JAX-RS 2.0 client or CXF WebClient/proxies, then you'd see
a=1&a=2&a=3".
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6869) Consider adding Spring Boot starter
[
https://issues.apache.org/jira/browse/CXF-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350726#comment-15350726
]
Sergey Beryozkin commented on CXF-6869:
---
Hi Vedran
I'm planning to update a "cxf.path" property to "cxf.servlet-path" property. It
would be more in line with Spring MVC's server.servlet-path, are you OK with it
?
Thanks, Sergey
> Consider adding Spring Boot starter
> ---
>
> Key: CXF-6869
> URL: https://issues.apache.org/jira/browse/CXF-6869
> Project: CXF
> Issue Type: New Feature
> Components: Integration
>Reporter: Vedran Pavic
>Assignee: Sergey Beryozkin
> Fix For: 3.1.7, 3.2.0
>
>
> I've recently authored a PR in Spring Boot to add support for
> auto-configuration of {{CXFServlet}} and default CXF's configuration:
> https://github.com/spring-projects/spring-boot/pull/5659
> The PR was closed with "won't fix" resolution since Boot team are unwilling
> to add CXF as a dependency to the project. Instead a 3rd party starter was
> suggested.
> The concept of a 3rd party starter is generally encouraged for technologies
> that don't have first-class support in projects from Spring portfolio. Such
> 3rd party starters are listed here:
> https://github.com/spring-projects/spring-boot/blob/master/spring-boot-starters/README.adoc
> If CXF team is interested, I'm willing to port my PR to CXF.
> Note that the original PR was focused around JAX-WS support, but can be
> easily expanded to include JAX-RS support as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350811#comment-15350811
]
Neal Hu commented on CXF-6941:
--
Yes, after investigated our app client(ios AFNetworking), I agree to migrate
our client from "a=1,2,3" and a[]=1&a[]=2&a[]=3 to a=1&a=2&a=3.
Thanks for your time.
Neal
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6869) Consider adding Spring Boot starter
[
https://issues.apache.org/jira/browse/CXF-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350823#comment-15350823
]
Sergey Beryozkin commented on CXF-6869:
---
Or may be "cxf.servlet.path" so that a 'path' can be aligned in yaml with
(cxf.servlet.) "init"
> Consider adding Spring Boot starter
> ---
>
> Key: CXF-6869
> URL: https://issues.apache.org/jira/browse/CXF-6869
> Project: CXF
> Issue Type: New Feature
> Components: Integration
>Reporter: Vedran Pavic
>Assignee: Sergey Beryozkin
> Fix For: 3.1.7, 3.2.0
>
>
> I've recently authored a PR in Spring Boot to add support for
> auto-configuration of {{CXFServlet}} and default CXF's configuration:
> https://github.com/spring-projects/spring-boot/pull/5659
> The PR was closed with "won't fix" resolution since Boot team are unwilling
> to add CXF as a dependency to the project. Instead a 3rd party starter was
> suggested.
> The concept of a 3rd party starter is generally encouraged for technologies
> that don't have first-class support in projects from Spring portfolio. Such
> 3rd party starters are listed here:
> https://github.com/spring-projects/spring-boot/blob/master/spring-boot-starters/README.adoc
> If CXF team is interested, I'm willing to port my PR to CXF.
> Note that the original PR was focused around JAX-WS support, but can be
> easily expanded to include JAX-RS support as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350858#comment-15350858
]
Sergey Beryozkin commented on CXF-6941:
---
Hi Neal
thanks, the most important thing here is that most WEB clients will all support
"a=1&a=2&a=3" and most server frameworks will handle it correctly. It appears
to be the most portable option.
Lets keep this issue open for a while though in case you see some difficulties
with the migration. Ping me off line if you'd like too,
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350858#comment-15350858
]
Sergey Beryozkin edited comment on CXF-6941 at 6/27/16 11:50 AM:
-
Hi Neal
thanks, the most important thing here is that most WEB clients will all support
"a=1&a=2&a=3" and most server frameworks will handle it correctly. It appears
to be the most portable option.
Lets keep this issue open for a while though in case you see some difficulties
with the migration. Ping me off line if you'd like too.
was (Author: sergey_beryozkin):
Hi Neal
thanks, the most important thing here is that most WEB clients will all support
"a=1&a=2&a=3" and most server frameworks will handle it correctly. It appears
to be the most portable option.
Lets keep this issue open for a while though in case you see some difficulties
with the migration. Ping me off line if you'd like too,
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350858#comment-15350858
]
Sergey Beryozkin edited comment on CXF-6941 at 6/27/16 11:52 AM:
-
Hi Neal
thanks, the most important thing here is that most WEB clients will all support
"a=1&a=2&a=3" and most server frameworks will handle it correctly. It appears
to be the most interoperable option.
Lets keep this issue open for a while though in case you see some difficulties
with the migration. Ping me off line if you'd like too.
was (Author: sergey_beryozkin):
Hi Neal
thanks, the most important thing here is that most WEB clients will all support
"a=1&a=2&a=3" and most server frameworks will handle it correctly. It appears
to be the most portable option.
Lets keep this issue open for a while though in case you see some difficulties
with the migration. Ping me off line if you'd like too.
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350880#comment-15350880
]
Neal Hu commented on CXF-6941:
--
Sure. If we plan to support the scenario, it will be the alternative way via
property. Thanks.
Neal
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CXF-6953) Update service list formatters for REST endpoints to optionally link to Swagger
Sergey Beryozkin created CXF-6953: - Summary: Update service list formatters for REST endpoints to optionally link to Swagger Key: CXF-6953 URL: https://issues.apache.org/jira/browse/CXF-6953 Project: CXF Issue Type: Improvement Components: JAX-RS, Transports Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Priority: Minor Fix For: 3.1.7, 3.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CXF-6953) Update service list formatters for REST endpoints to optionally link to Swagger
[ https://issues.apache.org/jira/browse/CXF-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-6953. --- Resolution: Fixed > Update service list formatters for REST endpoints to optionally link to > Swagger > --- > > Key: CXF-6953 > URL: https://issues.apache.org/jira/browse/CXF-6953 > Project: CXF > Issue Type: Improvement > Components: JAX-RS, Transports >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin >Priority: Minor > Fix For: 3.1.7, 3.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CXF-6954) JAXRSUtils.parseMediaTypes does not support semicolons
Ryan Diehl created CXF-6954: --- Summary: JAXRSUtils.parseMediaTypes does not support semicolons Key: CXF-6954 URL: https://issues.apache.org/jira/browse/CXF-6954 Project: CXF Issue Type: Bug Components: JAX-RS Affects Versions: 3.1.6 Reporter: Ryan Diehl We have a client application sending an Accept header in the following format: Accept=*/*; q=0.5; application/json The HTTP spec seems to allow for both comma and semicolon as separator characters in this use case. When a client sends this request, it is not split up, and results in an unsupported media type and an HTTP 406 error. Fortunately in our case, we are in control of the client, so we can modify the accept header. However, this may not always be the case for us, so I am logging this ticket in hopes of getting clarification on the expected behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6954) JAXRSUtils.parseMediaTypes does not support semicolons
[ https://issues.apache.org/jira/browse/CXF-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351804#comment-15351804 ] Sergey Beryozkin commented on CXF-6954: --- Well, how would a runtime know where the next media type starts ? Especially if more than one parameter for a given media type is available. Can you point me please to the relevant spec text ? > JAXRSUtils.parseMediaTypes does not support semicolons > -- > > Key: CXF-6954 > URL: https://issues.apache.org/jira/browse/CXF-6954 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.1.6 >Reporter: Ryan Diehl > > We have a client application sending an Accept header in the following > format: > Accept=*/*; q=0.5; application/json > The HTTP spec seems to allow for both comma and semicolon as separator > characters in this use case. When a client sends this request, it is not > split up, and results in an unsupported media type and an HTTP 406 error. > Fortunately in our case, we are in control of the client, so we can modify > the accept header. However, this may not always be the case for us, so I am > logging this ticket in hopes of getting clarification on the expected > behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6954) JAXRSUtils.parseMediaTypes does not support semicolons
[ https://issues.apache.org/jira/browse/CXF-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351806#comment-15351806 ] Sergey Beryozkin commented on CXF-6954: --- Note, once can always use pre-matching ContainerRequestFilter to modify various request properties to adapt the clients > JAXRSUtils.parseMediaTypes does not support semicolons > -- > > Key: CXF-6954 > URL: https://issues.apache.org/jira/browse/CXF-6954 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.1.6 >Reporter: Ryan Diehl > > We have a client application sending an Accept header in the following > format: > Accept=*/*; q=0.5; application/json > The HTTP spec seems to allow for both comma and semicolon as separator > characters in this use case. When a client sends this request, it is not > split up, and results in an unsupported media type and an HTTP 406 error. > Fortunately in our case, we are in control of the client, so we can modify > the accept header. However, this may not always be the case for us, so I am > logging this ticket in hopes of getting clarification on the expected > behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CXF-6954) JAXRSUtils.parseMediaTypes does not support semicolons
[ https://issues.apache.org/jira/browse/CXF-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351806#comment-15351806 ] Sergey Beryozkin edited comment on CXF-6954 at 6/27/16 9:02 PM: Note, one can always use pre-matching ContainerRequestFilter to modify various request properties to adapt the clients was (Author: sergey_beryozkin): Note, once can always use pre-matching ContainerRequestFilter to modify various request properties to adapt the clients > JAXRSUtils.parseMediaTypes does not support semicolons > -- > > Key: CXF-6954 > URL: https://issues.apache.org/jira/browse/CXF-6954 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.1.6 >Reporter: Ryan Diehl > > We have a client application sending an Accept header in the following > format: > Accept=*/*; q=0.5; application/json > The HTTP spec seems to allow for both comma and semicolon as separator > characters in this use case. When a client sends this request, it is not > split up, and results in an unsupported media type and an HTTP 406 error. > Fortunately in our case, we are in control of the client, so we can modify > the accept header. However, this may not always be the case for us, so I am > logging this ticket in hopes of getting clarification on the expected > behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6941) Send Comma Separated Array in url request
[
https://issues.apache.org/jira/browse/CXF-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351825#comment-15351825
]
Sergey Beryozkin commented on CXF-6941:
---
Note pre-matching ContainerRequestFilter can be used to reset the request URI.
However I'm getting more positive again about implementing the option. If one
has a client that may have to talk to a variety of servers, each of them having
different conventions (ex, Rails and JAX-RS) then it can become a problem.
I guess I can try to implement it for 3.1.7 or 3.1.8.
> Send Comma Separated Array in url request
> -
>
> Key: CXF-6941
> URL: https://issues.apache.org/jira/browse/CXF-6941
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 3.1.6
> Environment: Mac
>Reporter: Neal Hu
> Fix For: 3.2.0, 3.1.8
>
>
> http://stackoverflow.com/questions/11889997/how-to-send-a-array-in-url-request
> Spring MVC and PHP support send comma separated array in the url request:
> http://localhost:8080/MovieDB/GetJson?name=Actor1,Actor2,Actor3&startDate=20120101&endDate=20120505
> @RequestMapping(value = "/GetJson", method = RequestMethod.GET)
> public void getJson(@RequestParam("name") String[] ticker,
> @RequestParam("startDate") String startDate, @RequestParam("endDate") String
> endDate) {
>//code to get results from db for those params.
> }
> Now jax-rs only support below:
> http://localhost:8080/JerseyPojo/jaxrs/BasicResource/test?nameList=xx&nameList=xxx&nameList=ddd
> {code:java}
> @Path("/test")
> @GET
>public String getQueryList(@QueryParam("nameList") List nameList) {
> return "name list is: " + nameList.size() + nameList.toString();
> }
> {code}
> When we migrate from Spring MVC to jax-rs, found problem.
> Neal
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-6942) cxf-codegen-plugin wsdlArtifact failed to resolve WSDL
[ https://issues.apache.org/jira/browse/CXF-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351838#comment-15351838 ] Eivind Bergtøl commented on CXF-6942: - I have the same problem (maven 3.3.9). I have been trying to publish wsdl-files to nexus and only depend on the wsdl (wsdl first). At first I had problems with multiple wsdl-files in the same pom leaving only the first generated wsdl in the repository. This is fixed in CXF-6420. However this fix uses the classifier and it seams that, at least version 3.6.1 can't handle the classifier. The problem as it seams is that maven needs a dependency with ```Classifier.wsdl``` as type instead of ```wsdl``` and classifier in classifier tag. Not Working: ``` my.group webservices 0-SNAPSHOT wsdl MyService ``` Working: ``` my.groupl webservices 0-SNAPSHOT MyService.wsdl The problem is then that AbstractCodegenMoho that is checking for the dependencies only checks for ```"wsdl".equals(pArtifact.getType())``` and ignoring classifier. So either fix the dependency module, or have AbstractCodegenMoho check for ```pArtifact.getClassifier()+".wsdl").equals(pArtifact.getType())``` in addition to the checks that are there now. > cxf-codegen-plugin wsdlArtifact failed to resolve WSDL > -- > > Key: CXF-6942 > URL: https://issues.apache.org/jira/browse/CXF-6942 > Project: CXF > Issue Type: Sub-task > Components: Core >Affects Versions: 3.1.6 >Reporter: Torkel Røisli > Fix For: 3.0.0-milestone1 > > > Failed to resolve WSDL artifact no.xxx:artifactId-wsdl:master-SNAPSHOT. > > no.xxx > artifactId-wsdl > master-SNAPSHOT > > Verified to work ok with 3.0.0-milestone1, but failes with 3.1.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CXF-6942) cxf-codegen-plugin wsdlArtifact failed to resolve WSDL
[ https://issues.apache.org/jira/browse/CXF-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351838#comment-15351838 ] Eivind Bergtøl edited comment on CXF-6942 at 6/27/16 9:21 PM: -- I have the same problem (maven 3.3.9). I have been trying to publish wsdl-files to nexus and only depend on the wsdl (wsdl first). At first I had problems with multiple wsdl-files in the same pom leaving only the first generated wsdl in the repository. This is fixed in CXF-6420. However this fix uses the classifier and it seams that, at least version 3.6.1 can't handle the classifier. The problem as it seams is that maven needs a dependency with ```Classifier.wsdl``` as type instead of ```wsdl``` and classifier in classifier tag. Not Working: my.group webservices 0-SNAPSHOT wsdl MyService Working: my.groupl webservices 0-SNAPSHOT MyService.wsdl The problem is then that AbstractCodegenMoho that is checking for the dependencies only checks for "wsdl".equals(pArtifact.getType()) and ignoring classifier. So either fix the dependency module, or have AbstractCodegenMoho check for pArtifact.getClassifier()+".wsdl").equals(pArtifact.getType()) in addition to the checks that are there now. was (Author: eivinhb): I have the same problem (maven 3.3.9). I have been trying to publish wsdl-files to nexus and only depend on the wsdl (wsdl first). At first I had problems with multiple wsdl-files in the same pom leaving only the first generated wsdl in the repository. This is fixed in CXF-6420. However this fix uses the classifier and it seams that, at least version 3.6.1 can't handle the classifier. The problem as it seams is that maven needs a dependency with ```Classifier.wsdl``` as type instead of ```wsdl``` and classifier in classifier tag. Not Working: ``` my.group webservices 0-SNAPSHOT wsdl MyService ``` Working: ``` my.groupl webservices 0-SNAPSHOT MyService.wsdl The problem is then that AbstractCodegenMoho that is checking for the dependencies only checks for ```"wsdl".equals(pArtifact.getType())``` and ignoring classifier. So either fix the dependency module, or have AbstractCodegenMoho check for ```pArtifact.getClassifier()+".wsdl").equals(pArtifact.getType())``` in addition to the checks that are there now. > cxf-codegen-plugin wsdlArtifact failed to resolve WSDL > -- > > Key: CXF-6942 > URL: https://issues.apache.org/jira/browse/CXF-6942 > Project: CXF > Issue Type: Sub-task > Components: Core >Affects Versions: 3.1.6 >Reporter: Torkel Røisli > Fix For: 3.0.0-milestone1 > > > Failed to resolve WSDL artifact no.xxx:artifactId-wsdl:master-SNAPSHOT. > > no.xxx > artifactId-wsdl > master-SNAPSHOT > > Verified to work ok with 3.0.0-milestone1, but failes with 3.1.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CXF-6869) Consider adding Spring Boot starter
[
https://issues.apache.org/jira/browse/CXF-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352404#comment-15352404
]
Vedran Pavic commented on CXF-6869:
---
Hi Sergey!
I've originally modeled the names of configuration properties to be consistent
with [Spring Boot
properties|http://docs.spring.io/spring-boot/docs/1.4.0.M3/reference/htmlsingle/#common-application-properties]
that register additional servlets, namely with:
{code}
spring.webservices.path=/services # Path that serves as the base URI for the
services.
spring.h2.console.path=/h2-console # Path at which the console will be
available.
{code}
You are of course free to adjust these to match your preferences, if the
originally chosen names aren't descriptive enough.
Among your suggested alternatives, {{cxf.servlet-path}} makes more sense to me.
> Consider adding Spring Boot starter
> ---
>
> Key: CXF-6869
> URL: https://issues.apache.org/jira/browse/CXF-6869
> Project: CXF
> Issue Type: New Feature
> Components: Integration
>Reporter: Vedran Pavic
>Assignee: Sergey Beryozkin
> Fix For: 3.1.7, 3.2.0
>
>
> I've recently authored a PR in Spring Boot to add support for
> auto-configuration of {{CXFServlet}} and default CXF's configuration:
> https://github.com/spring-projects/spring-boot/pull/5659
> The PR was closed with "won't fix" resolution since Boot team are unwilling
> to add CXF as a dependency to the project. Instead a 3rd party starter was
> suggested.
> The concept of a 3rd party starter is generally encouraged for technologies
> that don't have first-class support in projects from Spring portfolio. Such
> 3rd party starters are listed here:
> https://github.com/spring-projects/spring-boot/blob/master/spring-boot-starters/README.adoc
> If CXF team is interested, I'm willing to port my PR to CXF.
> Note that the original PR was focused around JAX-WS support, but can be
> easily expanded to include JAX-RS support as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CXF-5791) Could not send a message. Caused by HTTP response '404: Not Found'
[
https://issues.apache.org/jira/browse/CXF-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352413#comment-15352413
]
Maninder Singh commented on CXF-5791:
-
Hi,
Can you please let me know, from which version onward the fix is present ?
Thanks & Regards,
Maninder
> Could not send a message. Caused by HTTP response '404: Not Found'
> --
>
> Key: CXF-5791
> URL: https://issues.apache.org/jira/browse/CXF-5791
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.0.1
> Environment: GNU/Linux Debian sid with jdk1.7.0_60 (Java HotSpot(TM)
> 64-Bit Server VM (build 24.60-b09, mixed mode))
>Reporter: Guilherme Veloso Neves Oliveira
>Assignee: Akitoshi Yoshida
> Labels: patch
> Fix For: 3.0.1
>
> Attachments: NettyHttpClientRequest.patch
>
>
> The issue https://issues.apache.org/jira/browse/CXF-5781 was resolved the
> exception "port out of range: -1", but introduced the new exception below
> (Could not send Message - HTTP response '404: Not Found')
> What is surprising for me is that the application server hosting the
> webservice runs an instance of JBoss (Red Hat) and not IIS (Microsoft). I say
> this because the HTTP header response for code 404 was produced by an IIS
> server (Microsoft). In DEBUG mode, I collected the correct header produced by
> JBOSS and wrong produced by IIS (Microsoft). I caught these two headers
> stopping code execution in getResponseCode () method of the class $
> org.apache.cxf.transport.http.netty.client.NettyHttpConduit
> NettyWrappedOutputStream.
> The wrong HTTP header was produced simply running the code!
> The correct HTTP header was produced as follows: at runtime, in
> initializePorts() method of class org.apache.cxf.jaxws.ServiceImpl.java the
> value of the local variable called "address" (in line 210, before calling the
> method addPort) was changed to include the number of TCP port 443
> (https://homologwsincom.in.gov.br:443/services/servicoIN). With this change
> again (the reasons are described in
> https://issues.apache.org/jira/browse/CXF-5781), everything worked normally.
> Despite trying to create a patch, I did not get success. So, I would ask that
> the TCP port number was not removed from the local variable called "address".
> Below the headers HTTP:
> ==
> Correct Header
> DefaultFullHttpResponse(decodeResult: success)
> HTTP/1.1 200 OK
> Date: Mon, 09 Jun 2014 01:22:57 GMT
> X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
> Content-Type: text/xml;charset=UTF-8
> Vary: Accept-Encoding,User-Agent
> Keep-Alive: timeout=20, max=100
> Connection: Keep-Alive
> Content-Length: 730
> -
> Wrong Header
> DefaultFullHttpResponse(decodeResult: success)
> HTTP/1.1 404 Not Found
> Date: Mon, 09 Jun 2014 01:20:52 GMT
> Server: Microsoft-IIS/7.5
> Content-Type: text/html; charset=ISO-8859-1
> X-Powered-By: ASP.NET
> Vary: Accept-Encoding,User-Agent
> Keep-Alive: timeout=5, max=100
> Connection: Keep-Alive
> Content-Length: 1245
> =
> Below, the stacktrace:
> Jun 08, 2014 10:09:05 PM org.apache.cxf.phase.PhaseInterceptorChain
> doDefaultLogging
> WARNING: Interceptor for
> {http://xfire.ws.incom}servicoIN#{http://xfire.ws.incom}ConsultaFormasPagamento
> has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: Could not send Message.
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:326)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:279)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:137)
> at com.sun.proxy.$Proxy35.consultaFormasPagamento(Unknown Source)
> at
> incom.ws.xfire.ServicoINPortType_ServicoINHttpPort_Client.main(ServicoINPortType_ServicoINHttpPort_Client.java:60)
> Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '404:
> Not Found' when communicating with
> https://homologwsincom.in.gov.br/services/servicoIN
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1573)
> at
> org.apache.cxf.tran
[jira] [Commented] (CXF-5781) Port ou of Range: -1
[
https://issues.apache.org/jira/browse/CXF-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352415#comment-15352415
]
Maninder Singh commented on CXF-5781:
-
Hi,
Can you please let me know, from which version onward the fix is present ?
Thanks & Regards,
Maninder
> Port ou of Range: -1
>
>
> Key: CXF-5781
> URL: https://issues.apache.org/jira/browse/CXF-5781
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 3.0.0
> Environment: GNU/Linux Debian sid with jdk1.7.0_60 (Java HotSpot(TM)
> 64-Bit Server VM (build 24.60-b09, mixed mode))
>Reporter: Guilherme Veloso Neves Oliveira
>Assignee: Akitoshi Yoshida
>Priority: Critical
> Fix For: 3.0.1
>
>
> I'm trying to access a service available in the URL
> (https://homologwsincom.in.gov.br/services/servicoIN) and when I run the
> ServicoINPortType_ServicoINHttpPort_Client.java (write automatic for CXF 3.0)
> class, with appropriate amendments security header, happens the exception
> below. All classes containing this url in the code generated automatically
> been changed to possess the number of tcp port 443 getting written as
> ("https://homologwsincom.in.gov.br:443/services/servicoIN";). I add the port
> number 443 in the URL as an attempt to fix the problem.
> In initializePorts() method of class org.apache.cxf.jaxws.ServiceImpl.java
> the URL (https://homologwsincom.in.gov.br:443/services/servicoIN?wsdl) was
> changed to (https:// homologwsincom.in.gov.br/services/servicoIN) without the
> TCP port number.
> At runtime, the realized change in the value of the local variable called
> "address" to include the number of TCP port 443 again and everything worked
> normally. I would like the above method does not alter the provided URL.
> Below, the stacktrace:
> ADVERTÊNCIA: Interceptor for
> {http://xfire.ws.incom}servicoIN#{http://xfire.ws.incom}ConsultaFormasPagamento
> has thrown exception, unwinding now
> java.lang.IllegalArgumentException: IllegalArgumentException invoking
> https://homologwsincom.in.gov.br/services/servicoIN: port out of range:-1
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1359)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1348)
> at
> org.apache.cxf.transport.http.netty.client.NettyHttpConduit$NettyWrappedOutputStream.close(NettyHttpConduit.java:153)
> at
> org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:56)
> at
> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:215)
> at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:638)
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:326)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:279)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:137)
> at com.sun.proxy.$Proxy40.consultaFormasPagamento(Unknown Source)
> at
> incom.ws.xfire.ServicoINPortType_ServicoINHttpPort_Client.main(ServicoINPortType_ServicoINHttpPort_Client.java:62)
> Caused by: java.lang.IllegalArgumentException: port out of range:-1
> at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
> at java.net.InetSocketAddress.(InetSocketAddress.java:224)
> at
> org.apache.cxf.transport.http.netty.client.NettyHttpConduit$NettyWrappedOutputStream.connect(NettyHttpConduit.java:293)
> at
> org.apache.cxf.transport.http.netty.client.NettyHttpConduit$NettyWrappedOutputStream.setupWrappedStream(NettyHttpConduit.java:243)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleHeadersTrustCaching(HTTPConduit.java:1302)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStrea
