[jira] [Created] (CXF-5869) Temporary file caching using encryption may get corrupted data in some ciphers

Akitoshi Yoshida created CXF-5869: - Summary: Temporary file caching using encryption may get corrupted data in some ciphers Key: CXF-5869 URL: https://issues.apache.org/jira/browse/CXF-5869 Project:

[jira] [Resolved] (CXF-5869) Temporary file caching using encryption may get corrupted data in some ciphers

[ https://issues.apache.org/jira/browse/CXF-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5869. --- Resolution: Fixed Temporary file caching using encryption may get corrupted data in some

[jira] [Created] (CXF-5893) Websocket transport sporadically fails with corrupted data

Akitoshi Yoshida created CXF-5893: - Summary: Websocket transport sporadically fails with corrupted data Key: CXF-5893 URL: https://issues.apache.org/jira/browse/CXF-5893 Project: CXF Issue

[jira] [Commented] (CXF-5875) Problems in WS-Addressing with anonymous replyTo or faultTo Address

[ https://issues.apache.org/jira/browse/CXF-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068342#comment-14068342 ] Akitoshi Yoshida commented on CXF-5875: --- I can certainly expect case 3 and case 4 are

[jira] [Commented] (CXF-5893) Websocket transport sporadically fails with corrupted data

[ https://issues.apache.org/jira/browse/CXF-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068346#comment-14068346 ] Akitoshi Yoshida commented on CXF-5893: --- This is regression from CXF-5809 which added

[jira] [Resolved] (CXF-5893) Websocket transport sporadically fails with corrupted data

[ https://issues.apache.org/jira/browse/CXF-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5893. --- Resolution: Fixed Fix Version/s: 3.0.2 Websocket transport sporadically fails with

[jira] [Created] (CXF-5900) websocket destination in osgi fails to start after being stopped

Akitoshi Yoshida created CXF-5900: - Summary: websocket destination in osgi fails to start after being stopped Key: CXF-5900 URL: https://issues.apache.org/jira/browse/CXF-5900 Project: CXF

[jira] [Updated] (CXF-5900) websocket destination in osgi fails to start after being stopped

[ https://issues.apache.org/jira/browse/CXF-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida updated CXF-5900: -- Description: A websocket destination in OSGi fails to start after it is being stopped. The

[jira] [Assigned] (CXF-5878) Disabling policy engine causes NPE

[ https://issues.apache.org/jira/browse/CXF-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reassigned CXF-5878: - Assignee: Akitoshi Yoshida Disabling policy engine causes NPE

[jira] [Commented] (CXF-5878) Disabling policy engine causes NPE

[ https://issues.apache.org/jira/browse/CXF-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077526#comment-14077526 ] Akitoshi Yoshida commented on CXF-5878: --- it looks like there is some inconsistency in

[jira] [Resolved] (CXF-5878) Disabling policy engine causes NPE

[ https://issues.apache.org/jira/browse/CXF-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5878. --- Resolution: Fixed Fix Version/s: 3.1.0 3.0.2

[jira] [Commented] (CXF-5878) Disabling policy engine causes NPE

[ https://issues.apache.org/jira/browse/CXF-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14079348#comment-14079348 ] Akitoshi Yoshida commented on CXF-5878: --- Hi Luca, this patch should fix the issue. By

[jira] [Created] (CXF-5949) LogBrowser not working

Akitoshi Yoshida created CXF-5949: - Summary: LogBrowser not working Key: CXF-5949 URL: https://issues.apache.org/jira/browse/CXF-5949 Project: CXF Issue Type: Bug Components:

[jira] [Resolved] (CXF-5949) LogBrowser not working

[ https://issues.apache.org/jira/browse/CXF-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5949. --- Resolution: Fixed LogBrowser not working -- Key:

[jira] [Created] (CXF-5962) Make LogBrowser sample also run in OSGi

Akitoshi Yoshida created CXF-5962: - Summary: Make LogBrowser sample also run in OSGi Key: CXF-5962 URL: https://issues.apache.org/jira/browse/CXF-5962 Project: CXF Issue Type: Improvement

[jira] [Commented] (CXF-5962) Make LogBrowser sample also run in OSGi

[ https://issues.apache.org/jira/browse/CXF-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103679#comment-14103679 ] Akitoshi Yoshida commented on CXF-5962: --- describing the status below: the pushed code

[jira] [Resolved] (CXF-5962) Make LogBrowser sample also run in OSGi

[ https://issues.apache.org/jira/browse/CXF-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5962. --- Resolution: Fixed Fix Version/s: 3.1.0 3.0.2 the settings reference

[jira] [Reopened] (CXF-5962) Make LogBrowser sample also run in OSGi

[ https://issues.apache.org/jira/browse/CXF-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reopened CXF-5962: --- add a blueprint version that works with other cxf endpoints. Make LogBrowser sample also run in

[jira] [Resolved] (CXF-5962) Make LogBrowser sample also run in OSGi

[ https://issues.apache.org/jira/browse/CXF-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5962. --- Resolution: Fixed Make LogBrowser sample also run in OSGi

[jira] [Commented] (CXF-5582) Enhance CXF LogBrowser to receive Log events in real time via WebSocket

[ https://issues.apache.org/jira/browse/CXF-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14113601#comment-14113601 ] Akitoshi Yoshida commented on CXF-5582: --- Hi, I experimented this in the

[jira] [Commented] (CXF-5582) Enhance CXF LogBrowser to receive Log events in real time via WebSocket

[ https://issues.apache.org/jira/browse/CXF-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14113787#comment-14113787 ] Akitoshi Yoshida commented on CXF-5582: --- Hi Sergey, thanks for your comments. I

[jira] [Created] (CXF-5979) Allow some headers to be returned in WebSocket's streaming responses

Akitoshi Yoshida created CXF-5979: - Summary: Allow some headers to be returned in WebSocket's streaming responses Key: CXF-5979 URL: https://issues.apache.org/jira/browse/CXF-5979 Project: CXF

[jira] [Resolved] (CXF-5979) Allow some headers to be returned in WebSocket's streaming responses

[ https://issues.apache.org/jira/browse/CXF-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5979. --- Resolution: Fixed Fix Version/s: 3.1.0 3.0.2 Allow some headers to

[jira] [Created] (CXF-5984) Provide a simple way start a decoupled servlet endpoint

Akitoshi Yoshida created CXF-5984: - Summary: Provide a simple way start a decoupled servlet endpoint Key: CXF-5984 URL: https://issues.apache.org/jira/browse/CXF-5984 Project: CXF Issue

[jira] [Resolved] (CXF-5984) Provide a simple way start a decoupled servlet endpoint

[ https://issues.apache.org/jira/browse/CXF-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-5984. --- Resolution: Fixed Fix Version/s: 3.1.0 3.0.2 Provide a simple way

[jira] [Resolved] (CXF-6000) Wrong default algorithm is used for TrustManagerFactory instantiation

[ https://issues.apache.org/jira/browse/CXF-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6000. --- Resolution: Fixed Thanks to Joerg Kessler for identifying the cause. Wrong default algorithm

[jira] [Created] (CXF-6075) NPE may occur at websocket destination under high load

Akitoshi Yoshida created CXF-6075: - Summary: NPE may occur at websocket destination under high load Key: CXF-6075 URL: https://issues.apache.org/jira/browse/CXF-6075 Project: CXF Issue Type:

[jira] [Resolved] (CXF-6075) NPE may occur at websocket destination under high load

[ https://issues.apache.org/jira/browse/CXF-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6075. --- Resolution: Fixed NPE may occur at websocket destination under high load

[jira] [Commented] (CXF-6127) Check entire cause chain for SOAPFaultException

[ https://issues.apache.org/jira/browse/CXF-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14233143#comment-14233143 ] Akitoshi Yoshida commented on CXF-6127: --- Does the statement in that section imply the

[jira] [Commented] (CXF-5738) given soap action does not match any operation

[ https://issues.apache.org/jira/browse/CXF-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14233224#comment-14233224 ] Akitoshi Yoshida commented on CXF-5738: --- You mean the wsdl that you see at your cxf's

[jira] [Assigned] (CXF-6127) Check entire cause chain for SOAPFaultException

[ https://issues.apache.org/jira/browse/CXF-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reassigned CXF-6127: - Assignee: Akitoshi Yoshida Check entire cause chain for SOAPFaultException

[jira] [Assigned] (CXF-6147) Part of demo wsdl_first_soap12 doesnt work

[ https://issues.apache.org/jira/browse/CXF-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reassigned CXF-6147: - Assignee: Akitoshi Yoshida Part of demo wsdl_first_soap12 doesnt work

[jira] [Commented] (CXF-6145) WS-RM demo server throws exception

[ https://issues.apache.org/jira/browse/CXF-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242433#comment-14242433 ] Akitoshi Yoshida commented on CXF-6145: --- This issue needs to be analyzed before making

[jira] [Commented] (CXF-6127) Check entire cause chain for SOAPFaultException

[ https://issues.apache.org/jira/browse/CXF-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242758#comment-14242758 ] Akitoshi Yoshida commented on CXF-6127: --- I commented on your PR. Check entire cause

[jira] [Resolved] (CXF-6147) Part of demo wsdl_first_soap12 doesnt work

[ https://issues.apache.org/jira/browse/CXF-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6147. --- Resolution: Fixed Fix Version/s: 2.7.15 3.1.0 applied the patch from

[jira] [Commented] (CXF-6145) WS-RM demo server throws exception

[ https://issues.apache.org/jira/browse/CXF-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244049#comment-14244049 ] Akitoshi Yoshida commented on CXF-6145: --- @Guopu, Okay. If the code is sending back an

[jira] [Created] (CXF-6152) WSDLValidator may throw ClassCastException under verbose mode

Akitoshi Yoshida created CXF-6152: - Summary: WSDLValidator may throw ClassCastException under verbose mode Key: CXF-6152 URL: https://issues.apache.org/jira/browse/CXF-6152 Project: CXF

[jira] [Resolved] (CXF-6152) WSDLValidator may throw ClassCastException under verbose mode

[ https://issues.apache.org/jira/browse/CXF-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6152. --- Resolution: Fixed Fix Version/s: 2.7.15 3.0.4 3.1.0

[jira] [Commented] (CXF-6159) Apache cxf command line wsdlvalidator does not validate incorrect prefix:elements.

[ https://issues.apache.org/jira/browse/CXF-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14249988#comment-14249988 ] Akitoshi Yoshida commented on CXF-6159: --- i think this is neither a bug nor a schema

[jira] [Commented] (CXF-6151) Apache-cxf wsdlvalidator returns error in mime:part

[ https://issues.apache.org/jira/browse/CXF-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250003#comment-14250003 ] Akitoshi Yoshida commented on CXF-6151: --- sorry for the delay in replying. i though

[jira] [Assigned] (CXF-6151) Apache-cxf wsdlvalidator returns error in mime:part

[ https://issues.apache.org/jira/browse/CXF-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reassigned CXF-6151: - Assignee: Akitoshi Yoshida Apache-cxf wsdlvalidator returns error in mime:part

[jira] [Commented] (CXF-6151) Apache-cxf wsdlvalidator returns error in mime:part

[ https://issues.apache.org/jira/browse/CXF-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14257566#comment-14257566 ] Akitoshi Yoshida commented on CXF-6151: --- You are right. we should just replace the

[jira] [Resolved] (CXF-6151) Apache-cxf wsdlvalidator returns error in mime:part

[ https://issues.apache.org/jira/browse/CXF-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6151. --- Resolution: Fixed Fix Version/s: 3.1.0 2.7.15 3.0.4

[jira] [Resolved] (CXF-6127) Check thrown Exception's cause for SOAPFaultException

[ https://issues.apache.org/jira/browse/CXF-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6127. --- Resolution: Fixed Fix Version/s: 3.1.0 2.7.15 3.0.4

[jira] [Commented] (CXF-6228) Using XSLTFeature with large messages creates unremovable temporary files

[ https://issues.apache.org/jira/browse/CXF-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301997#comment-14301997 ] Akitoshi Yoshida commented on CXF-6228: --- @Papp The patch has been submitted into

[jira] [Assigned] (CXF-6228) Using XSLTFeature with large messages creates unremovable temporary files

[ https://issues.apache.org/jira/browse/CXF-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reassigned CXF-6228: - Assignee: Akitoshi Yoshida Using XSLTFeature with large messages creates unremovable

[jira] [Commented] (CXF-6228) Using XSLTFeature with large messages creates unremovable temporary files

[ https://issues.apache.org/jira/browse/CXF-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301232#comment-14301232 ] Akitoshi Yoshida commented on CXF-6228: --- [~pip25] thanks for the test. The problem is

[jira] [Commented] (CXF-6228) Using XSLTFeature with large messages creates unremovable temporary files

[ https://issues.apache.org/jira/browse/CXF-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14305085#comment-14305085 ] Akitoshi Yoshida commented on CXF-6228: --- Thank you :-) Using XSLTFeature with large

[jira] [Commented] (CXF-6143) SSL/TLS hostname verification does not strictly follow HTTPS RFC2818

[ https://issues.apache.org/jira/browse/CXF-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14283467#comment-14283467 ] Akitoshi Yoshida commented on CXF-6143: --- Hi Colm, For the second part, we can use

[jira] [Commented] (CXF-6143) SSL/TLS hostname verification does not strictly follow HTTPS RFC2818

[ https://issues.apache.org/jira/browse/CXF-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14283561#comment-14283561 ] Akitoshi Yoshida commented on CXF-6143: --- Hi Colm, for the first part, while reading

[jira] [Commented] (CXF-6143) SSL/TLS hostname verification does not strictly follow HTTPS RFC2818

[ https://issues.apache.org/jira/browse/CXF-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14282628#comment-14282628 ] Akitoshi Yoshida commented on CXF-6143: --- I noticed a few things with this change.

[jira] [Created] (CXF-6250) WebSocket conduit fails to process String based responses and throws NPE

Akitoshi Yoshida created CXF-6250: - Summary: WebSocket conduit fails to process String based responses and throws NPE Key: CXF-6250 URL: https://issues.apache.org/jira/browse/CXF-6250 Project: CXF

[jira] [Resolved] (CXF-6250) WebSocket conduit fails to process String based responses and throws NPE

[ https://issues.apache.org/jira/browse/CXF-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6250. --- Resolution: Fixed Fix Version/s: 3.1.0 WebSocket conduit fails to process String based

[jira] [Resolved] (CXF-6232) Refactor CXF's Atmosphere based WebSocket transport for more flexible and extensible handling

[ https://issues.apache.org/jira/browse/CXF-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6232. --- Resolution: Fixed Fix Version/s: 3.0.5 3.1.0 Refactor CXF's

[jira] [Commented] (CXF-6198) No SOAPFault for HTTP error code 400

[ https://issues.apache.org/jira/browse/CXF-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14368863#comment-14368863 ] Akitoshi Yoshida commented on CXF-6198: --- I am not sure if this is a real problem. Why

[jira] [Created] (CXF-6308) Make WebSocket transport's embedded jetty mode to use atmosphere if available

Akitoshi Yoshida created CXF-6308: - Summary: Make WebSocket transport's embedded jetty mode to use atmosphere if available Key: CXF-6308 URL: https://issues.apache.org/jira/browse/CXF-6308 Project:

[jira] [Created] (CXF-6305) Add an option to include or exclude specific response headers in WebSocket's transport

Akitoshi Yoshida created CXF-6305: - Summary: Add an option to include or exclude specific response headers in WebSocket's transport Key: CXF-6305 URL: https://issues.apache.org/jira/browse/CXF-6305

[jira] [Commented] (CXF-6198) No SOAPFault for HTTP error code 400

[ https://issues.apache.org/jira/browse/CXF-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14369462#comment-14369462 ] Akitoshi Yoshida commented on CXF-6198: --- My interpretation was that the server may

[jira] [Created] (CXF-6318) Execute JAXRS WebSocket systests with and without atmosphere

Akitoshi Yoshida created CXF-6318: - Summary: Execute JAXRS WebSocket systests with and without atmosphere Key: CXF-6318 URL: https://issues.apache.org/jira/browse/CXF-6318 Project: CXF

[jira] [Resolved] (CXF-6274) NullPointerException in DestinationSequence because of RMCaptureInInterceptor not in interceptor chain

[ https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6274. --- Resolution: Not a Problem Assignee: Akitoshi Yoshida Hi Jochen, As you already found it

[jira] [Commented] (CXF-6274) NullPointerException in DestinationSequence because of RMCaptureInInterceptor not in interceptor chain

[ https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381872#comment-14381872 ] Akitoshi Yoshida commented on CXF-6274: --- the only thing that we can improve is that we

[jira] [Commented] (CXF-6239) Out of memory when using Async connections in Apache CXF

[ https://issues.apache.org/jira/browse/CXF-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343069#comment-14343069 ] Akitoshi Yoshida commented on CXF-6239: --- Hi Atul, I have a couple of questions. - What

[jira] [Commented] (CXF-6257) Creating and Endpoint using JAX-WS API, getting the binding and then publishing causes a NullPointerException

[ https://issues.apache.org/jira/browse/CXF-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381898#comment-14381898 ] Akitoshi Yoshida commented on CXF-6257: --- sorry for the delay. i didn't realize there

[jira] [Assigned] (CXF-6257) Creating and Endpoint using JAX-WS API, getting the binding and then publishing causes a NullPointerException

[ https://issues.apache.org/jira/browse/CXF-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reassigned CXF-6257: - Assignee: Akitoshi Yoshida Creating and Endpoint using JAX-WS API, getting the binding

[jira] [Resolved] (CXF-6305) Add an option to include or exclude specific response headers in WebSocket's transport

[ https://issues.apache.org/jira/browse/CXF-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6305. --- Resolution: Fixed Fix Version/s: 3.1.0 Add an option to include or exclude specific

[jira] [Commented] (CXF-6305) Add an option to include or exclude specific response headers in WebSocket's transport

[ https://issues.apache.org/jira/browse/CXF-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14369564#comment-14369564 ] Akitoshi Yoshida commented on CXF-6305: --- pushed the relevant commit with the wrong

[jira] [Commented] (CXF-6232) Refactor CXF's Atmosphere based WebSocket transport for more flexible and extensible handling

[ https://issues.apache.org/jira/browse/CXF-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14369580#comment-14369580 ] Akitoshi Yoshida commented on CXF-6232: --- I just noticed that I had incorrectly pushed

[jira] [Commented] (CXF-6257) Creating and Endpoint using JAX-WS API, getting the binding and then publishing causes a NullPointerException

[ https://issues.apache.org/jira/browse/CXF-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381996#comment-14381996 ] Akitoshi Yoshida commented on CXF-6257: --- Hi Carlos, indeed. As you have described,

[jira] [Resolved] (CXF-6257) Creating and Endpoint using JAX-WS API, getting the binding and then publishing causes a NullPointerException

[ https://issues.apache.org/jira/browse/CXF-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6257. --- Resolution: Fixed Fix Version/s: 3.0.5 2.7.16 3.1.0

[jira] [Commented] (CXF-6231) Getting the wsdl from a cxf webservice throws an exception

[ https://issues.apache.org/jira/browse/CXF-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298453#comment-14298453 ] Akitoshi Yoshida commented on CXF-6231: --- @Guillaume I think there is something

[jira] [Commented] (CXF-6228) Using XSLTFeature with large messages creates unremovable temporary files

[ https://issues.apache.org/jira/browse/CXF-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298489#comment-14298489 ] Akitoshi Yoshida commented on CXF-6228: --- If a file doesn't get deleted, that means

[jira] [Created] (CXF-6232) Refactor CXF's Atmosphere based WebSocket transport for more flexible and extensible handling

Akitoshi Yoshida created CXF-6232: - Summary: Refactor CXF's Atmosphere based WebSocket transport for more flexible and extensible handling Key: CXF-6232 URL: https://issues.apache.org/jira/browse/CXF-6232

[jira] [Created] (CXF-6314) WebSocket transport should not require dependency to jetty

Akitoshi Yoshida created CXF-6314: - Summary: WebSocket transport should not require dependency to jetty Key: CXF-6314 URL: https://issues.apache.org/jira/browse/CXF-6314 Project: CXF Issue

[jira] [Reopened] (CXF-6329) Allow multiple atmosphere interceptors to be configured for the websocket transport

[ https://issues.apache.org/jira/browse/CXF-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reopened CXF-6329: --- seem to have broken 3.0.5 build. need a rework for 3.0.5. Allow multiple atmosphere interceptors

[jira] [Created] (CXF-6329) Allow multiple atmosphere interceptors to be configured for the websocket transport

Akitoshi Yoshida created CXF-6329: - Summary: Allow multiple atmosphere interceptors to be configured for the websocket transport Key: CXF-6329 URL: https://issues.apache.org/jira/browse/CXF-6329

[jira] [Resolved] (CXF-6329) Allow multiple atmosphere interceptors to be configured for the websocket transport

[ https://issues.apache.org/jira/browse/CXF-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6329. --- Resolution: Fixed Fix Version/s: 3.0.5 3.1.0 Allow multiple

[jira] [Commented] (CXF-6349) Introduce HTTP/2 Transport

[ https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14502533#comment-14502533 ] Akitoshi Yoshida commented on CXF-6349: --- I agree with what Sergey says above. If the

[jira] [Commented] (CXF-6323) WS-RM redelivery not implemented

[ https://issues.apache.org/jira/browse/CXF-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519274#comment-14519274 ] Akitoshi Yoshida commented on CXF-6323: --- I have a code that I prepared for CXF-4209

[jira] [Commented] (CXF-6323) WS-RM redelivery not implemented

[ https://issues.apache.org/jira/browse/CXF-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519296#comment-14519296 ] Akitoshi Yoshida commented on CXF-6323: --- One option currently frequently used is to

[jira] [Commented] (CXF-6274) NullPointerException in DestinationSequence because of RMCaptureInInterceptor not in interceptor chain

[ https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519003#comment-14519003 ] Akitoshi Yoshida commented on CXF-6274: --- Hi Jim, you are right. Thanks a lot. I didn't

[jira] [Commented] (CXF-6274) NullPointerException in DestinationSequence because of RMCaptureInInterceptor not in interceptor chain

[ https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519340#comment-14519340 ] Akitoshi Yoshida commented on CXF-6274: --- Hi Jochen, I am really sorry about not

[jira] [Updated] (CXF-6274) NullPointerException in DestinationSequence because of RMCaptureInInterceptor not in interceptor chain

[ https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida updated CXF-6274: -- Fix Version/s: 2.7.16 NullPointerException in DestinationSequence because of

[jira] [Resolved] (CXF-6274) NullPointerException in DestinationSequence because of RMCaptureInInterceptor not in interceptor chain

[ https://issues.apache.org/jira/browse/CXF-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6274. --- Resolution: Fixed Fix Version/s: 3.1.0 NullPointerException in DestinationSequence

[jira] [Created] (CXF-6394) Add an option to add the namespace map of the container element in the message

Akitoshi Yoshida created CXF-6394: - Summary: Add an option to add the namespace map of the container element in the message Key: CXF-6394 URL: https://issues.apache.org/jira/browse/CXF-6394 Project:

[jira] [Commented] (CXF-6323) WS-RM redelivery not implemented

[ https://issues.apache.org/jira/browse/CXF-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530811#comment-14530811 ] Akitoshi Yoshida commented on CXF-6323: --- @Jim For the inbound to the RMStore, I don't

[jira] [Resolved] (CXF-6394) Add an option to add the namespace map of the container element in the message

[ https://issues.apache.org/jira/browse/CXF-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6394. --- Resolution: Fixed Fix Version/s: 2.7.17 3.0.6 3.1.1

[jira] [Created] (CXF-6397) Upgrade atmosphere to 2.3.1

Akitoshi Yoshida created CXF-6397: - Summary: Upgrade atmosphere to 2.3.1 Key: CXF-6397 URL: https://issues.apache.org/jira/browse/CXF-6397 Project: CXF Issue Type: Task Components:

[jira] [Created] (CXF-6399) Add attributes transform handling in transform feature

Akitoshi Yoshida created CXF-6399: - Summary: Add attributes transform handling in transform feature Key: CXF-6399 URL: https://issues.apache.org/jira/browse/CXF-6399 Project: CXF Issue Type:

[jira] [Resolved] (CXF-6399) Add attributes transform handling in transform feature

[ https://issues.apache.org/jira/browse/CXF-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6399. --- Resolution: Fixed Fix Version/s: 3.0.6 3.1.1 Add attributes

[jira] [Updated] (CXF-6397) Upgrade atmosphere to 2.3.0

[ https://issues.apache.org/jira/browse/CXF-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida updated CXF-6397: -- Summary: Upgrade atmosphere to 2.3.0 (was: Upgrade atmosphere to 2.3.1) Upgrade atmosphere to

[jira] [Commented] (CXF-6397) Upgrade atmosphere to 2.3.0

[ https://issues.apache.org/jira/browse/CXF-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548174#comment-14548174 ] Akitoshi Yoshida commented on CXF-6397: --- Initially, intended to upgrade to 2.3.1 but

[jira] [Assigned] (CXF-6406) WS-RM persistence with RMTxStore does not work with JNDI Lookup

[ https://issues.apache.org/jira/browse/CXF-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida reassigned CXF-6406: - Assignee: Akitoshi Yoshida WS-RM persistence with RMTxStore does not work with JNDI

[jira] [Resolved] (CXF-6308) Make WebSocket transport's embedded jetty mode to use atmosphere if available

[ https://issues.apache.org/jira/browse/CXF-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6308. --- Resolution: Fixed Make WebSocket transport's embedded jetty mode to use atmosphere if

[jira] [Resolved] (CXF-6341) Add atmosphere when installing feature cxf-transports-websocket-server

[ https://issues.apache.org/jira/browse/CXF-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6341. --- Resolution: Fixed Fix Version/s: 3.0.5 3.1.0 Add atmosphere when

[jira] [Updated] (CXF-6308) Make WebSocket transport's embedded jetty mode to use atmosphere if available

[ https://issues.apache.org/jira/browse/CXF-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida updated CXF-6308: -- Fix Version/s: 3.1.0 Make WebSocket transport's embedded jetty mode to use atmosphere if

[jira] [Created] (CXF-6341) Add atmosphere when installing feature cxf-transports-websocket-server

Akitoshi Yoshida created CXF-6341: - Summary: Add atmosphere when installing feature cxf-transports-websocket-server Key: CXF-6341 URL: https://issues.apache.org/jira/browse/CXF-6341 Project: CXF

[jira] [Resolved] (CXF-6329) Allow multiple atmosphere interceptors to be configured for the websocket transport

[ https://issues.apache.org/jira/browse/CXF-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6329. --- Resolution: Fixed Allow multiple atmosphere interceptors to be configured for the websocket

[jira] [Resolved] (CXF-6314) WebSocket transport should not require dependency to jetty

[ https://issues.apache.org/jira/browse/CXF-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6314. --- Resolution: Fixed WebSocket transport should not require dependency to jetty

[jira] [Resolved] (CXF-6318) Execute JAXRS WebSocket systests with and without atmosphere

[ https://issues.apache.org/jira/browse/CXF-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akitoshi Yoshida resolved CXF-6318. --- Resolution: Fixed Fix Version/s: 3.0.5 3.1.0 Execute JAXRS WebSocket

[jira] [Commented] (CXF-6406) WS-RM persistence with RMTxStore does not work with JNDI Lookup

[ https://issues.apache.org/jira/browse/CXF-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550383#comment-14550383 ] Akitoshi Yoshida commented on CXF-6406: --- Hi Viral, thank you for reporting this bug.

  1   2   3   >