[jira] [Commented] (CXF-8122) CXF 2.7.9 memory leak when shutdown Tomcat 6.0.35
[ https://issues.apache.org/jira/browse/CXF-8122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938417#comment-16938417 ] Colm O hEigeartaigh commented on CXF-8122: -- Please try with the latest Tomcat and CXF releases. If the issue persists then please attach the log outputs that show the error. > CXF 2.7.9 memory leak when shutdown Tomcat 6.0.35 > - > > Key: CXF-8122 > URL: https://issues.apache.org/jira/browse/CXF-8122 > Project: CXF > Issue Type: Bug >Affects Versions: 2.7.9 > Environment: Tomcat 6.0.25 >Reporter: Fang Ping >Priority: Major > > We built a project using Spring, CXF and WSDL. We deployed it to Tomcat > 6.0.25, and there always some warnings when I shutdown Tomcat. (Warnings > like X started a thread named XXX but faild to stop it . This is very > likely to create a memory leak.) > Using Tomcat 6.0.25, JDK 1.6.0.23 and CXF 2.7.9. > I even upgraded JDK to 1.8, Tomcat to 7.0, and CXF to 3.0.16 , but still > have warnings. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version
[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938428#comment-16938428 ] Colm O hEigeartaigh commented on CXF-8057: -- Hi [~ffang] , Please go ahead with this, as the latest Jackson 2.9.10 (which is already upgraded on master) requires stax2-api 4.2. Colm. > upgrade to use stax2-api and woodstox-core latest version > - > > Key: CXF-8057 > URL: https://issues.apache.org/jira/browse/CXF-8057 > Project: CXF > Issue Type: Task >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.4.0 > > > since stax2-api 3.1.4 was released 5 years ago. > And also need t latest woodstox-core to make OSGi happy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CXF-8119) Can't Inject "javax.ws.rs.core.Context" annotation with camel blueprint
[
https://issues.apache.org/jira/browse/CXF-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tenti updated CXF-8119:
-
Priority: Major (was: Minor)
> Can't Inject "javax.ws.rs.core.Context" annotation with camel blueprint
> ---
>
> Key: CXF-8119
> URL: https://issues.apache.org/jira/browse/CXF-8119
> Project: CXF
> Issue Type: Bug
> Components: Bus, Core, JAX-RS, OSGi, Resources
>Affects Versions: 3.2.7
>Reporter: Marco Tenti
>Priority: Major
>
> I have a REST Service project build for a Red Hat Fuse.
> it's a simple set up of a rest service with a "blueprint.xml" and the
> "cxf:rsServer" and it's work just fine.
> But i need to use the @Context annotation of javax.ws.rs and i ca't find a
> way to inject dynamically the @Context on my java class.
> A full project for test of the problem can be found here:
> [bug-load-context-annotation-blueprint|https://github.com/p4535992/bug-load-context-annotation-blueprint]
> My goal is to set the value of the field;
> {code:java}
> @javax.ws.rs.core.Context
> public javax.ws.rs.core.HttpHeaders httpHeaders;
> {code}
> Another strange bug is if i call the method:
> {code:java}
> @GET
> @Path("/ping")
> @Produces(MediaType.APPLICATION_JSON)
> @WebMethod(operationName = "ping")
> @WebResult(name = "Response")
> @ApiResponses(value = {
> @ApiResponse(code = 200, message = "Success") ,
> @ApiResponse(code = 500, message = "Error")
> }
> )
> @ApiOperation( "Get operation with Response and @Default value")
> public Response ping() {
> logger.info("PING SIGNATURE SERVICE");
> return Response.ok().entity("PING SIGNATURE SERVICE").build();
> }
> }
> {code}
> it's work just fine , but if i call this (i just add the @Context HttpHeaders
> httpHeaders parameter on the method) :
> {code:java}
> @GET
> @Path("/ping")
> @Produces(MediaType.APPLICATION_JSON)
> @WebMethod(operationName = "ping")
> @WebResult(name = "Response")
> @ApiResponses(value =
> { @ApiResponse(code = 200, message = "Success") , @ApiResponse(code = 500,
> message = "Error") }
> )
> @ApiOperation( "Get operation with Response and @Default value")
> public Response ping(@Context HttpHeaders httpHeaders)
> { logger.info("PING SIGNATURE SERVICE"); return Response.ok().entity("PING
> SIGNATURE SERVICE").build(); }
> }
> {code}
> i get this error:
> {code}
> 415 Error: Unsupported Media Type
> {code}
> Teh documentation say something about the attribute "propagateContexts" to
> true, but seem do nothing:
> {code:}
> uri="cxfrs:bean:myRestSereer?performInvocation=true&bindingStyle=SimpleConsumer&propagateContexts=true"/>
> {code}
> ANOTHER example i can't undestand, the first method is injected with succes,
> the second give me the "415 Error: Unsupported Media Type":
> {code:java}
> /**
>* THIS WORK
>*/
> @GET
> @Path("/getheader")
> public Response getHeaderDetails(
> @HeaderParam("User-Agent") String userAgent,
> @HeaderParam("Content-Type") String contentType,
> @HeaderParam("Accept") String accept
> ) {
> String header = "User-Agent: " + userAgent +
> "\nContent-Type: " + contentType +
> "\nAccept: " + accept;
> return Response.status(200).entity(header).build();
> }
> /**
>* THIS NOT WORK error "415 Error: Unsupported Media Type"
>*/
> @GET
> @Path("/getallheader")
> public Response getAllHeader(@Context HttpHeaders httpHeaders) {
> // local variables
> StringBuffer stringBuffer = new StringBuffer();
> String headerValue = "";
> for(String header : httpHeaders.getRequestHeaders().keySet()) {
> headerValue =
> httpHeaders.getRequestHeader(header).get(0);
> stringBuffer.append(header + ": " + headerValue + "\n");
> }
> logger.info(stringBuffer.toString());
> return
> Response.status(200).entity(stringBuffer.toString()).build();
> }
> {code}
> Anyone know what i'm doing wrong with camel-blueprint?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CXF-8123) FIQL parser throws a StringIndexOutOfBoundsException on a wildcard character
Colm O hEigeartaigh created CXF-8123: Summary: FIQL parser throws a StringIndexOutOfBoundsException on a wildcard character Key: CXF-8123 URL: https://issues.apache.org/jira/browse/CXF-8123 Project: CXF Issue Type: Bug Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.4.0, 3.2.11, 3.3.4 The FIQL parser throws a StringIndexOutOfBoundsException on a (single) wildcard character. This is not a valid search term - however it should catch the exception and throw a meaningful error back to the client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version
[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938512#comment-16938512 ] Freeman Yue Fang commented on CXF-8057: --- [~coheigea], done! Cheers Freeman > upgrade to use stax2-api and woodstox-core latest version > - > > Key: CXF-8057 > URL: https://issues.apache.org/jira/browse/CXF-8057 > Project: CXF > Issue Type: Task >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.4.0 > > > since stax2-api 3.1.4 was released 5 years ago. > And also need t latest woodstox-core to make OSGi happy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CXF-8057) upgrade to use stax2-api and woodstox-core latest version
[ https://issues.apache.org/jira/browse/CXF-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Yue Fang resolved CXF-8057. --- Resolution: Fixed > upgrade to use stax2-api and woodstox-core latest version > - > > Key: CXF-8057 > URL: https://issues.apache.org/jira/browse/CXF-8057 > Project: CXF > Issue Type: Task >Reporter: Freeman Yue Fang >Assignee: Freeman Yue Fang >Priority: Major > Fix For: 3.4.0 > > > since stax2-api 3.1.4 was released 5 years ago. > And also need t latest woodstox-core to make OSGi happy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CXF-8123) FIQL parser throws a StringIndexOutOfBoundsException on a wildcard character
[ https://issues.apache.org/jira/browse/CXF-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-8123. -- Resolution: Fixed > FIQL parser throws a StringIndexOutOfBoundsException on a wildcard character > > > Key: CXF-8123 > URL: https://issues.apache.org/jira/browse/CXF-8123 > Project: CXF > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.4.0, 3.2.11, 3.3.4 > > > The FIQL parser throws a StringIndexOutOfBoundsException on a (single) > wildcard character. This is not a valid search term - however it should catch > the exception and throw a meaningful error back to the client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CXF-8120) JAX-RS 2.1 SSE client: forbidden response without WebApplicationException
[
https://issues.apache.org/jira/browse/CXF-8120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko resolved CXF-8120.
---
Resolution: Fixed
> JAX-RS 2.1 SSE client: forbidden response without WebApplicationException
> -
>
> Key: CXF-8120
> URL: https://issues.apache.org/jira/browse/CXF-8120
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 3.2.10, 3.3.3
>Reporter: Krisztian Kurucz
>Assignee: Andriy Redko
>Priority: Major
>
> SSE client is trying to process the events even if the response was not OK
> (200).
> E.g.: when response status code is 403
> {quote}4.5.2 Client Runtime
> [...] Note that the client runtime will only throw an instance of
> WebApplicationException (or any of its subclasses) as a result of a response
> from the server with status codes 3xx, 4xx or 5xx.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8119) Can't Inject "javax.ws.rs.core.Context" annotation with camel blueprint
[
https://issues.apache.org/jira/browse/CXF-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939057#comment-16939057
]
Andriy Redko commented on CXF-8119:
---
Hi [~4535992],
I quickly looked at the use case, the 415 happens because for some reason CXF
tries to read HttpHeaders from the body instead of injecting it, may be because
Camel does write the HttpHeaders into the request body. Something is off here,
I think we may step back and start with a very basic CXF + Camel integration, I
will try to help out this week or the next one.
Best Regards,
Andriy Redko
> Can't Inject "javax.ws.rs.core.Context" annotation with camel blueprint
> ---
>
> Key: CXF-8119
> URL: https://issues.apache.org/jira/browse/CXF-8119
> Project: CXF
> Issue Type: Bug
> Components: Bus, Core, JAX-RS, OSGi, Resources
>Affects Versions: 3.2.7
>Reporter: Marco Tenti
>Priority: Major
>
> I have a REST Service project build for a Red Hat Fuse.
> it's a simple set up of a rest service with a "blueprint.xml" and the
> "cxf:rsServer" and it's work just fine.
> But i need to use the @Context annotation of javax.ws.rs and i ca't find a
> way to inject dynamically the @Context on my java class.
> A full project for test of the problem can be found here:
> [bug-load-context-annotation-blueprint|https://github.com/p4535992/bug-load-context-annotation-blueprint]
> My goal is to set the value of the field;
> {code:java}
> @javax.ws.rs.core.Context
> public javax.ws.rs.core.HttpHeaders httpHeaders;
> {code}
> Another strange bug is if i call the method:
> {code:java}
> @GET
> @Path("/ping")
> @Produces(MediaType.APPLICATION_JSON)
> @WebMethod(operationName = "ping")
> @WebResult(name = "Response")
> @ApiResponses(value = {
> @ApiResponse(code = 200, message = "Success") ,
> @ApiResponse(code = 500, message = "Error")
> }
> )
> @ApiOperation( "Get operation with Response and @Default value")
> public Response ping() {
> logger.info("PING SIGNATURE SERVICE");
> return Response.ok().entity("PING SIGNATURE SERVICE").build();
> }
> }
> {code}
> it's work just fine , but if i call this (i just add the @Context HttpHeaders
> httpHeaders parameter on the method) :
> {code:java}
> @GET
> @Path("/ping")
> @Produces(MediaType.APPLICATION_JSON)
> @WebMethod(operationName = "ping")
> @WebResult(name = "Response")
> @ApiResponses(value =
> { @ApiResponse(code = 200, message = "Success") , @ApiResponse(code = 500,
> message = "Error") }
> )
> @ApiOperation( "Get operation with Response and @Default value")
> public Response ping(@Context HttpHeaders httpHeaders)
> { logger.info("PING SIGNATURE SERVICE"); return Response.ok().entity("PING
> SIGNATURE SERVICE").build(); }
> }
> {code}
> i get this error:
> {code}
> 415 Error: Unsupported Media Type
> {code}
> Teh documentation say something about the attribute "propagateContexts" to
> true, but seem do nothing:
> {code:}
> uri="cxfrs:bean:myRestSereer?performInvocation=true&bindingStyle=SimpleConsumer&propagateContexts=true"/>
> {code}
> ANOTHER example i can't undestand, the first method is injected with succes,
> the second give me the "415 Error: Unsupported Media Type":
> {code:java}
> /**
>* THIS WORK
>*/
> @GET
> @Path("/getheader")
> public Response getHeaderDetails(
> @HeaderParam("User-Agent") String userAgent,
> @HeaderParam("Content-Type") String contentType,
> @HeaderParam("Accept") String accept
> ) {
> String header = "User-Agent: " + userAgent +
> "\nContent-Type: " + contentType +
> "\nAccept: " + accept;
> return Response.status(200).entity(header).build();
> }
> /**
>* THIS NOT WORK error "415 Error: Unsupported Media Type"
>*/
> @GET
> @Path("/getallheader")
> public Response getAllHeader(@Context HttpHeaders httpHeaders) {
> // local variables
> StringBuffer stringBuffer = new StringBuffer();
> String headerValue = "";
> for(String header : httpHeaders.getRequestHeaders().keySet()) {
> headerValue =
> httpHeaders.getRequestHeader(header).get(0);
> stringBuffer.append(header + ": " + headerValue + "\n");
> }
> logger.info(stringBuffer.toString());
> return
> Response.status(200).entity(stringBuffer.toString()).build();
> }
> {code}
> Anyone know what i'm doing wrong with camel-blueprint?
--
This m
