[jira] [Resolved] (CXF-5827) Use only local name matching for inbound rpc/literal processing to support some older rpc/literal implementation

[ https://issues.apache.org/jira/browse/CXF-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5827. -- Resolution: Fixed Fix Version/s: 3.0.1 2.7.12 2.6.15 > Use o

[jira] [Commented] (CXF-5827) Use only local name matching for inbound rpc/literal processing to support some older rpc/literal implementation

[ https://issues.apache.org/jira/browse/CXF-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048758#comment-14048758 ] Aki Yoshida commented on CXF-5827: -- Hi Dan, thanks for your reply on the list. yes. from th

[jira] [Resolved] (CXF-5834) WS-RM's JAXB marshalling/unmarshalling is not thread-safe

[ https://issues.apache.org/jira/browse/CXF-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5834. -- Resolution: Fixed Fix Version/s: 3.0.1 2.7.12 2.6.15 > WS-RM

[jira] [Created] (CXF-5834) WS-RM's JAXB marshalling/unmarshalling is not thread-safe

Aki Yoshida created CXF-5834: Summary: WS-RM's JAXB marshalling/unmarshalling is not thread-safe Key: CXF-5834 URL: https://issues.apache.org/jira/browse/CXF-5834 Project: CXF Issue Type: Bug

[jira] [Updated] (CXF-5827) Use only local name matching for inbound rpc/literal processing to support some older rpc/literal implementation

[ https://issues.apache.org/jira/browse/CXF-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5827: - Description: Although WS-i BP R2735 states the part parameter elements must be in no namespace, some old r

[jira] [Updated] (CXF-5827) Use only local name matching for inbound rpc/literal processing to support some older rpc/literal implementation

[ https://issues.apache.org/jira/browse/CXF-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5827: - Description: Although WS-i BP R2735 states the part parameter elements must be in no namespace, some old r

[jira] [Resolved] (CXF-5809) WebSocket transport supporting concurrent asynchronous calls

[ https://issues.apache.org/jira/browse/CXF-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5809. -- Resolution: Fixed > WebSocket transport supporting concurrent asynchronous calls > --

[jira] [Commented] (CXF-5827) Use only local name matching for inbound rpc/literal processing to support some older rpc/literal implementation

[ https://issues.apache.org/jira/browse/CXF-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046010#comment-14046010 ] Aki Yoshida commented on CXF-5827: -- Hi Dan, thanks for your comment on dev@cxf and I answer

[jira] [Created] (CXF-5827) Use only local name matching for inbound rpc/literal processing to support some older rpc/literal implementation

Aki Yoshida created CXF-5827: Summary: Use only local name matching for inbound rpc/literal processing to support some older rpc/literal implementation Key: CXF-5827 URL: https://issues.apache.org/jira/browse/CXF-5827

[jira] [Resolved] (CXF-5812) When I am synchronously or asynchornously calling the web services it's throwing an issue like avax.xml.ws.soap.SOAPFaultException: java.lang.IllegalStateException: Inval

[ https://issues.apache.org/jira/browse/CXF-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5812. -- Resolution: Invalid Hi Lakshmi, This is not a place to ask questions or get a quick help. Please post you

[jira] [Resolved] (CXF-5804) Improvement Issue CXF 5781 and CXF 5791

[ https://issues.apache.org/jira/browse/CXF-5804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5804. -- Resolution: Won't Fix Hi Guilherme, thanks. I'm closing this ticket as won't fix. regards, aki > Improv

[jira] [Created] (CXF-5809) WebSocket transport supporting concurrent asynchronous calls

Aki Yoshida created CXF-5809: Summary: WebSocket transport supporting concurrent asynchronous calls Key: CXF-5809 URL: https://issues.apache.org/jira/browse/CXF-5809 Project: CXF Issue Type: Imp

[jira] [Resolved] (CXF-5746) WebsocketConduit to use the id header so that it can correlate requests and responses

[ https://issues.apache.org/jira/browse/CXF-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5746. -- Resolution: Fixed > WebsocketConduit to use the id header so that it can correlate requests and > respon

[jira] [Commented] (CXF-5623) Failed to invoke WSDLToJava - is already defined

[ https://issues.apache.org/jira/browse/CXF-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032437#comment-14032437 ] Aki Yoshida commented on CXF-5623: -- I think what Dan described is rather the correct way th

[jira] [Commented] (CXF-5804) Improvement Issue CXF 5781 and CXF 5791

[ https://issues.apache.org/jira/browse/CXF-5804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032316#comment-14032316 ] Aki Yoshida commented on CXF-5804: -- Well, I think this change will change the semantics of

[jira] [Resolved] (CXF-5805) Invalid SOAP Envelope names are accepted

[ https://issues.apache.org/jira/browse/CXF-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5805. -- Resolution: Fixed Fix Version/s: 3.0.1 2.7.12 2.6.15 > Inval

[jira] [Created] (CXF-5805) Invalid SOAP Envelope names are accepted

Aki Yoshida created CXF-5805: Summary: Invalid SOAP Envelope names are accepted Key: CXF-5805 URL: https://issues.apache.org/jira/browse/CXF-5805 Project: CXF Issue Type: Bug Components

[jira] [Resolved] (CXF-5798) WebSocket transport fails to transport a large message

[ https://issues.apache.org/jira/browse/CXF-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5798. -- Resolution: Fixed Fix Version/s: 3.0.1 fixed the issue using one approach that buffers the output

[jira] [Created] (CXF-5798) WebSocket transport fails to transport a large message

Aki Yoshida created CXF-5798: Summary: WebSocket transport fails to transport a large message Key: CXF-5798 URL: https://issues.apache.org/jira/browse/CXF-5798 Project: CXF Issue Type: Bug

[jira] [Resolved] (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:all-tabpanel ] Aki Yoshida resolved CXF-5791. -- Resolution: Fixed Fix Version/s: 3.0.1 Guilherme's patch applied. thanks. > Could not send a mess

[jira] [Assigned] (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:all-tabpanel ] Aki Yoshida reassigned CXF-5791: Assignee: Aki Yoshida > Could not send a message. Caused by HTTP response '404: Not Found' >

[jira] [Resolved] (CXF-5794) DynamicClientFactory createClient fails for Simple Rpc Service (java.lang.IllegalStateException: no source files )

[ https://issues.apache.org/jira/browse/CXF-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5794. -- Resolution: Fixed Fix Version/s: 3.0.1 2.7.12 2.6.15 > Dynam

[jira] [Created] (CXF-5794) DynamicClientFactory createClient fails for Simple Rpc Service (java.lang.IllegalStateException: no source files )

Aki Yoshida created CXF-5794: Summary: DynamicClientFactory createClient fails for Simple Rpc Service (java.lang.IllegalStateException: no source files ) Key: CXF-5794 URL: https://issues.apache.org/jira/browse/CXF-57

[jira] [Updated] (CXF-5790) Response-Code is logged for the response sent over a decoupled endpoint

[ https://issues.apache.org/jira/browse/CXF-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5790: - Component/s: (was: WS-* Components) Core > Response-Code is logged for the response se

[jira] [Resolved] (CXF-5790) Response-Code is logged for the response sent over a decoupled endpoint

[ https://issues.apache.org/jira/browse/CXF-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5790. -- Resolution: Fixed Fix Version/s: 3.0.1 2.7.12 2.6.15 > Respo

[jira] [Created] (CXF-5790) Response-Code is logged for the response sent over a decoupled endpoint

Aki Yoshida created CXF-5790: Summary: Response-Code is logged for the response sent over a decoupled endpoint Key: CXF-5790 URL: https://issues.apache.org/jira/browse/CXF-5790 Project: CXF Issu

[jira] [Resolved] (CXF-5781) Port ou of Range: -1

[ https://issues.apache.org/jira/browse/CXF-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5781. -- Resolution: Fixed Fix Version/s: 3.0.1 > Port ou of Range: -1 > > >

[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=14018042#comment-14018042 ] Aki Yoshida commented on CXF-5781: -- it looks like the default port handling is missing in N

[jira] [Assigned] (CXF-5781) Port ou of Range: -1

[ https://issues.apache.org/jira/browse/CXF-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida reassigned CXF-5781: Assignee: Aki Yoshida > Port ou of Range: -1 > > > Key: CXF-5781

[jira] [Resolved] (CXF-5747) Add a karaf feature for the websocket transport

[ https://issues.apache.org/jira/browse/CXF-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5747. -- Resolution: Fixed > Add a karaf feature for the websocket transport > ---

[jira] [Resolved] (CXF-5752) Unable to find the target operation when using websocket transport without atmosphere

[ https://issues.apache.org/jira/browse/CXF-5752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5752. -- Resolution: Fixed > Unable to find the target operation when using websocket transport without > atmosph

[jira] [Created] (CXF-5752) Unable to find the target operation when using websocket transport without atmosphere

Aki Yoshida created CXF-5752: Summary: Unable to find the target operation when using websocket transport without atmosphere Key: CXF-5752 URL: https://issues.apache.org/jira/browse/CXF-5752 Project: CXF

[jira] [Commented] (CXF-3272) WS-RM returns Fault for duplicate message received, should probably return acknowledgement instead

[ https://issues.apache.org/jira/browse/CXF-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002533#comment-14002533 ] Aki Yoshida commented on CXF-3272: -- Hi Dennis, For the oneway case, most clients expect to

[jira] [Commented] (CXF-3272) WS-RM returns Fault for duplicate message received, should probably return acknowledgement instead

[ https://issues.apache.org/jira/browse/CXF-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001685#comment-14001685 ] Aki Yoshida commented on CXF-3272: -- Hi Dennis, do you have an update to this item? thanks.

[jira] [Created] (CXF-5747) Add a karaf feature for the websocket transport

Aki Yoshida created CXF-5747: Summary: Add a karaf feature for the websocket transport Key: CXF-5747 URL: https://issues.apache.org/jira/browse/CXF-5747 Project: CXF Issue Type: Improvement

[jira] [Created] (CXF-5746) WebsocketConduit to use the id header so that it can correlate requests and responses

Aki Yoshida created CXF-5746: Summary: WebsocketConduit to use the id header so that it can correlate requests and responses Key: CXF-5746 URL: https://issues.apache.org/jira/browse/CXF-5746 Project: CXF

[jira] [Updated] (CXF-5698) Use the service root path instead of the initial request path to restrict websocket service access

[ https://issues.apache.org/jira/browse/CXF-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5698: - Fix Version/s: (was: 3.0.0) > Use the service root path instead of the initial request path to restrict

[jira] [Resolved] (CXF-5715) Add a conduit part to WebSocket transport

[ https://issues.apache.org/jira/browse/CXF-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5715. -- Resolution: Fixed I close this ticked as resolved with the limitation that is mentioned in my comment en

[jira] [Resolved] (CXF-5604) Add atmosphere based implementation in websocket transport

[ https://issues.apache.org/jira/browse/CXF-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5604. -- Resolution: Fixed Fix Version/s: 3.0.0 > Add atmosphere based implementation in websocket transpor

[jira] [Updated] (CXF-5679) WS-S after upgrade fails with org.apache.ws.security.WSSecurityException: The signature or decryption was invalid

[ https://issues.apache.org/jira/browse/CXF-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5679: - Attachment: ParseBodyTest.java an updated file to show the initial/trailing whitespace cases that i meant.

[jira] [Updated] (CXF-5679) WS-S after upgrade fails with org.apache.ws.security.WSSecurityException: The signature or decryption was invalid

[ https://issues.apache.org/jira/browse/CXF-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5679: - Attachment: (was: ParseBodyTest.java) > WS-S after upgrade fails with org.apache.ws.security.WSSecurity

[jira] [Updated] (CXF-5679) WS-S after upgrade fails with org.apache.ws.security.WSSecurityException: The signature or decryption was invalid

[ https://issues.apache.org/jira/browse/CXF-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5679: - Attachment: ParseBodyTest.java I think StaxUtils.copy using SAAJStreamWriter loses the initial and trailing

[jira] [Resolved] (CXF-5711) SOAP 1.2 fault reason xml:lang attribute should follow XML standard

[ https://issues.apache.org/jira/browse/CXF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5711. -- Resolution: Fixed Fix Version/s: 2.7.12 2.6.15 applied the patch provided by Ir

[jira] [Comment Edited] (CXF-5711) SOAP 1.2 fault reason xml:lang attribute should follow XML standard

[ https://issues.apache.org/jira/browse/CXF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984182#comment-13984182 ] Aki Yoshida edited comment on CXF-5711 at 4/29/14 10:35 AM: Hi I

[jira] [Commented] (CXF-5711) SOAP 1.2 fault reason xml:lang attribute should follow XML standard

[ https://issues.apache.org/jira/browse/CXF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984182#comment-13984182 ] Aki Yoshida commented on CXF-5711: -- Hi Iris, it's all clear. sorry for the delay. I needed

[jira] [Commented] (CXF-5715) Add a conduit part to WebSocket transport

[ https://issues.apache.org/jira/browse/CXF-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982986#comment-13982986 ] Aki Yoshida commented on CXF-5715: -- Hi Sergey, yes. we have some interesting part (bindings

[jira] [Commented] (CXF-5715) Add a conduit part to WebSocket transport

[ https://issues.apache.org/jira/browse/CXF-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982880#comment-13982880 ] Aki Yoshida commented on CXF-5715: -- hi, just committed a conduit implementation that matche

[jira] [Created] (CXF-5715) Add a conduit part to WebSocket transport

Aki Yoshida created CXF-5715: Summary: Add a conduit part to WebSocket transport Key: CXF-5715 URL: https://issues.apache.org/jira/browse/CXF-5715 Project: CXF Issue Type: New Feature C

[jira] [Assigned] (CXF-5711) SOAP 1.2 fault reason xml:lang attribute should follow XML standard

[ https://issues.apache.org/jira/browse/CXF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida reassigned CXF-5711: Assignee: Aki Yoshida > SOAP 1.2 fault reason xml:lang attribute should follow XML standard > --

[jira] [Commented] (CXF-5711) SOAP 1.2 fault reason xml:lang attribute should follow XML standard

[ https://issues.apache.org/jira/browse/CXF-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980870#comment-13980870 ] Aki Yoshida commented on CXF-5711: -- in jdk6, Locale.toString() generates the underscored s

[jira] [Commented] (CXF-5479) Create a Maven plugin for generating WADL at build time

[ https://issues.apache.org/jira/browse/CXF-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980857#comment-13980857 ] Aki Yoshida commented on CXF-5479: -- hi, is this build working on OSX JDK6? I'm getting this

[jira] [Resolved] (CXF-5709) WSRM 1.1 TerminateSequence should not overwrite the default replyTo to none

[ https://issues.apache.org/jira/browse/CXF-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5709. -- Resolution: Fixed Fix Version/s: 3.0.0 2.7.12 2.6.15 > WSRM

[jira] [Created] (CXF-5709) WSRM 1.1 TerminateSequence should not overwrite the default replyTo to none

Aki Yoshida created CXF-5709: Summary: WSRM 1.1 TerminateSequence should not overwrite the default replyTo to none Key: CXF-5709 URL: https://issues.apache.org/jira/browse/CXF-5709 Project: CXF

[jira] [Comment Edited] (CXF-5698) Use the service root path instead of the initial request path to restrict websocket service access

[ https://issues.apache.org/jira/browse/CXF-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973061#comment-13973061 ] Aki Yoshida edited comment on CXF-5698 at 4/17/14 3:48 PM: --- Hi Ser

[jira] [Commented] (CXF-5698) Use the service root path instead of the initial request path to restrict websocket service access

[ https://issues.apache.org/jira/browse/CXF-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973061#comment-13973061 ] Aki Yoshida commented on CXF-5698: -- Hi Sergey, The original intention was, let's say, using

[jira] [Created] (CXF-5698) Use the service root path instead of the initial request path to restrict websocket service access

Aki Yoshida created CXF-5698: Summary: Use the service root path instead of the initial request path to restrict websocket service access Key: CXF-5698 URL: https://issues.apache.org/jira/browse/CXF-5698

[jira] [Resolved] (CXF-5676) IllegalArgumentException: wrong number of arguments while invoking operation with only an implicit header parameter

[ https://issues.apache.org/jira/browse/CXF-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5676. -- Resolution: Fixed Fix Version/s: 3.0.0 2.7.12 2.6.15 I commi

[jira] [Resolved] (CXF-5677) Operation without body but non empty header causes IllegalArgumentException

[ https://issues.apache.org/jira/browse/CXF-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5677. -- Resolution: Fixed Fix Version/s: 3.0.0 2.7.12 2.6.15

[jira] [Commented] (CXF-5677) Operation without body but non empty header causes IllegalArgumentException

[ https://issues.apache.org/jira/browse/CXF-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969328#comment-13969328 ] Aki Yoshida commented on CXF-5677: -- I think this is a duplicate of CXF-5676 and the fix is

[jira] [Assigned] (CXF-5676) IllegalArgumentException: wrong number of arguments while invoking operation with only an implicit header parameter

[ https://issues.apache.org/jira/browse/CXF-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida reassigned CXF-5676: Assignee: Aki Yoshida > IllegalArgumentException: wrong number of arguments while invoking operation

[jira] [Commented] (CXF-5676) IllegalArgumentException: wrong number of arguments while invoking operation with only an implicit header parameter

[ https://issues.apache.org/jira/browse/CXF-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964178#comment-13964178 ] Aki Yoshida commented on CXF-5676: -- there seems to be some irregularity in the processing w

[jira] [Commented] (CXF-5611) [joda-time] different versions in maven and feature descriptor

[ https://issues.apache.org/jira/browse/CXF-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937553#comment-13937553 ] Aki Yoshida commented on CXF-5611: -- Hi Freeman, sure. I somehow missed the original intenti

[jira] [Commented] (CXF-5611) [joda-time] different versions in maven and feature descriptor

[ https://issues.apache.org/jira/browse/CXF-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935160#comment-13935160 ] Aki Yoshida commented on CXF-5611: -- Hi Freeman, Shouldn't Alexey's project itself add the c

[jira] [Resolved] (CXF-5546) NPE may be thrown and logged during WS-RM's retransmission

[ https://issues.apache.org/jira/browse/CXF-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5546. -- Resolution: Fixed Fix Version/s: 2.7.11 3.0.0 > NPE may be thrown and logged du

[jira] [Resolved] (CXF-5614) CachedOutputStream may fail to read the data when encryption is turned on

[ https://issues.apache.org/jira/browse/CXF-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5614. -- Resolution: Fixed > CachedOutputStream may fail to read the data when encryption is turned on > -

[jira] [Updated] (CXF-5614) CachedOutputStream may fail to read the data when encryption is turned on

[ https://issues.apache.org/jira/browse/CXF-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5614: - Affects Version/s: 3.0.0-milestone2 > CachedOutputStream may fail to read the data when encryption is turne

[jira] [Updated] (CXF-5614) CachedOutputStream may fail to read the data when encryption is turned on

[ https://issues.apache.org/jira/browse/CXF-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5614: - Fix Version/s: 2.7.11 3.0.0 > CachedOutputStream may fail to read the data when encrypti

[jira] [Updated] (CXF-5614) CachedOutputStream may fail to read the data when encryption is turned on

[ https://issues.apache.org/jira/browse/CXF-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-5614: - Affects Version/s: (was: 2.6.12) > CachedOutputStream may fail to read the data when encryption is turn

[jira] [Created] (CXF-5614) CachedOutputStream may fail to read the data when encryption is turned on

Aki Yoshida created CXF-5614: Summary: CachedOutputStream may fail to read the data when encryption is turned on Key: CXF-5614 URL: https://issues.apache.org/jira/browse/CXF-5614 Project: CXF Is

[jira] [Commented] (CXF-5611) [joda-time] different versions in maven and feature descriptor

[ https://issues.apache.org/jira/browse/CXF-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933600#comment-13933600 ] Aki Yoshida commented on CXF-5611: -- I don't know why you have the range [2.2,3). I just che

[jira] [Created] (CXF-5604) Add atmosphere based implementation in websocket transport

Aki Yoshida created CXF-5604: Summary: Add atmosphere based implementation in websocket transport Key: CXF-5604 URL: https://issues.apache.org/jira/browse/CXF-5604 Project: CXF Issue Type: Improv

[jira] [Resolved] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5339. -- Resolution: Fixed Fix Version/s: 3.0.0 Hi all, I moved the code into a separate transport componen

[jira] [Reopened] (CXF-5587) CXF version 2.2.9 is not recognising my url-pattern

[ https://issues.apache.org/jira/browse/CXF-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida reopened CXF-5587: -- didn't know sergey was following. > CXF version 2.2.9 is not recognising my url-pattern >

[jira] [Closed] (CXF-5587) CXF version 2.2.9 is not recognising my url-pattern

[ https://issues.apache.org/jira/browse/CXF-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida closed CXF-5587. Resolution: Incomplete > CXF version 2.2.9 is not recognising my url-pattern > --

[jira] [Commented] (CXF-5587) CXF version 2.2.9 is not recognising my url-pattern

[ https://issues.apache.org/jira/browse/CXF-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930451#comment-13930451 ] Aki Yoshida commented on CXF-5587: -- Hi, Is there any way you could use cxf 2.7.x or 2.6.x?

[jira] [Resolved] (CXF-5600) WSDL generation at WS-RM endpoint leads to NPE in the server's log

[ https://issues.apache.org/jira/browse/CXF-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5600. -- Resolution: Fixed > WSDL generation at WS-RM endpoint leads to NPE in the server's log >

[jira] [Created] (CXF-5600) WSDL generation at WS-RM endpoint leads to NPE in the server's log

Aki Yoshida created CXF-5600: Summary: WSDL generation at WS-RM endpoint leads to NPE in the server's log Key: CXF-5600 URL: https://issues.apache.org/jira/browse/CXF-5600 Project: CXF Issue Typ

[jira] [Commented] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915620#comment-13915620 ] Aki Yoshida commented on CXF-5339: -- Hi sergey, thanks. yes. I just committed the change we

[jira] [Commented] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914658#comment-13914658 ] Aki Yoshida commented on CXF-5339: -- hi sergey, regarding the to-do's and the ideas to compa

[jira] [Commented] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914314#comment-13914314 ] Aki Yoshida commented on CXF-5339: -- it looks like the permgen issue that I was seeing has s

[jira] [Commented] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912753#comment-13912753 ] Aki Yoshida commented on CXF-5339: -- HI Sergey, thanks. I agree that it's better to have a s

[jira] [Comment Edited] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911880#comment-13911880 ] Aki Yoshida edited comment on CXF-5339 at 2/25/14 7:07 PM: --- Hi Ser

[jira] [Commented] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911880#comment-13911880 ] Aki Yoshida commented on CXF-5339: -- Hi Sergery, all, just committed the early working code

[jira] [Assigned] (CXF-5339) Introduce WebSocket CXF Transport

[ https://issues.apache.org/jira/browse/CXF-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida reassigned CXF-5339: Assignee: Aki Yoshida > Introduce WebSocket CXF Transport > - > >

[jira] [Commented] (CXF-5551) Creating a custom bus in Blueprint does not seem to work

[ https://issues.apache.org/jira/browse/CXF-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896612#comment-13896612 ] Aki Yoshida commented on CXF-5551: -- Hi Sergey, I'm sorry, I made some typos, it should say

[jira] [Commented] (CXF-5551) Creating a custom bus in Blueprint does not seem to work

[ https://issues.apache.org/jira/browse/CXF-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896508#comment-13896508 ] Aki Yoshida commented on CXF-5551: -- Hi Sergey, I think it should be working when using the

[jira] [Created] (CXF-5546) NPE may be thrown and logged during WS-RM's retransmission

Aki Yoshida created CXF-5546: Summary: NPE may be thrown and logged during WS-RM's retransmission Key: CXF-5546 URL: https://issues.apache.org/jira/browse/CXF-5546 Project: CXF Issue Type: Bug

[jira] [Resolved] (CXF-5517) Incorrect check for VOID type

[ https://issues.apache.org/jira/browse/CXF-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5517. -- Resolution: Fixed Fix Version/s: 2.7.10 2.6.13 3.0.0-mileston

[jira] [Assigned] (CXF-5517) Incorrect check for VOID type

[ https://issues.apache.org/jira/browse/CXF-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida reassigned CXF-5517: Assignee: Aki Yoshida > Incorrect check for VOID type > - > >

[jira] [Commented] (CXF-5517) Incorrect check for VOID type

[ https://issues.apache.org/jira/browse/CXF-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887826#comment-13887826 ] Aki Yoshida commented on CXF-5517: -- Maybe we need to fix this. but Void.TYPE is the same th

[jira] [Commented] (CXF-5509) NullPointerException if class with generic-array parameters is set to rootClassNames

[ https://issues.apache.org/jira/browse/CXF-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884228#comment-13884228 ] Aki Yoshida commented on CXF-5509: -- Bright, okay. I see. You could get this error spotted i

[jira] [Commented] (CXF-5509) NullPointerException if class with generic-array parameters is set to rootClassNames

[ https://issues.apache.org/jira/browse/CXF-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882731#comment-13882731 ] Aki Yoshida commented on CXF-5509: -- Hi, Is the unit test that you included in your zip file

[jira] [Resolved] (CXF-5507) Missing alternativeSelector handling in ws-policy feature's blueprint configuration

[ https://issues.apache.org/jira/browse/CXF-5507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5507. -- Resolution: Fixed > Missing alternativeSelector handling in ws-policy feature's blueprint > configuratio

[jira] [Created] (CXF-5507) Missing alternativeSelector handling in ws-policy feature's blueprint configuration

Aki Yoshida created CXF-5507: Summary: Missing alternativeSelector handling in ws-policy feature's blueprint configuration Key: CXF-5507 URL: https://issues.apache.org/jira/browse/CXF-5507 Project: CXF

[jira] [Resolved] (CXF-5506) Make ws-addressing schema available during blueprint schema resolution

[ https://issues.apache.org/jira/browse/CXF-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5506. -- Resolution: Fixed Fix Version/s: 2.7.9 2.6.12 3.0.0-milestone

[jira] [Created] (CXF-5506) Make ws-addressing schema available during blueprint schema resolution

Aki Yoshida created CXF-5506: Summary: Make ws-addressing schema available during blueprint schema resolution Key: CXF-5506 URL: https://issues.apache.org/jira/browse/CXF-5506 Project: CXF Issue

[jira] [Resolved] (CXF-5465) policy.xsd used in rt-ws-policy's blueprint configuration is inconsistent

[ https://issues.apache.org/jira/browse/CXF-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5465. -- Resolution: Fixed Fix Version/s: 2.7.9 2.6.12 3.0.0-milestone

[jira] [Resolved] (CXF-5461) Add ws-securitypolicy-1.2.xsd to rt-ws-policy's schema resolution

[ https://issues.apache.org/jira/browse/CXF-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5461. -- Resolution: Fixed Fix Version/s: 2.7.9 2.6.12 3.0.0-milestone

[jira] [Resolved] (CXF-5459) Some imported xsd schemas are not resolved in spring when referenced from another schema

[ https://issues.apache.org/jira/browse/CXF-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5459. -- Resolution: Fixed Fix Version/s: 2.7.9 2.6.12 3.0.0-milestone

[jira] [Resolved] (CXF-5405) WS-RM with anonymous endpoint throwing security policy validation exception for SequenceAck

[ https://issues.apache.org/jira/browse/CXF-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-5405. -- Resolution: Fixed Fix Version/s: 3.0.0-milestone2 > WS-RM with anonymous endpoint throwing securit

  1   2   3   4   5   >