[jira] [Commented] (CXF-5367) 2.7.7 schema validation incorrectly detects schema include recursion

[ https://issues.apache.org/jira/browse/CXF-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809516#comment-13809516 ] Jesse Pangburn commented on CXF-5367: - I have tested the 2.7.8-SNAPSHOT against this

[jira] [Commented] (CXF-5365) 2.7.7 schema validation seems broken

[ https://issues.apache.org/jira/browse/CXF-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808464#comment-13808464 ] Jesse Pangburn commented on CXF-5365: - OK, verified with addition of that dependency

[jira] [Created] (CXF-5367) 2.7.7 schema validation incorrectly detects schema include recursion

Jesse Pangburn created CXF-5367: --- Summary: 2.7.7 schema validation incorrectly detects schema include recursion Key: CXF-5367 URL: https://issues.apache.org/jira/browse/CXF-5367 Project: CXF

[jira] [Updated] (CXF-5367) 2.7.7 schema validation incorrectly detects schema include recursion

[ https://issues.apache.org/jira/browse/CXF-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-5367: Attachment: jaxws_dispatch_provider_schematest_XDSb_277.zip

[jira] [Created] (CXF-5365) 2.7.7 schema validation seems broken

Jesse Pangburn created CXF-5365: --- Summary: 2.7.7 schema validation seems broken Key: CXF-5365 URL: https://issues.apache.org/jira/browse/CXF-5365 Project: CXF Issue Type: Bug

[jira] [Updated] (CXF-5365) 2.7.7 schema validation seems broken

[ https://issues.apache.org/jira/browse/CXF-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-5365: Attachment: jaxws_dispatch_provider_schematest_276.zip

[jira] [Commented] (CXF-5354) faultTo address is ignored when fault is thrown

[ https://issues.apache.org/jira/browse/CXF-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804783#comment-13804783 ] Jesse Pangburn commented on CXF-5354: - I ran the test module and it was successful. I

[jira] [Updated] (CXF-5354) faultTo address is ignored when fault is thrown

[ https://issues.apache.org/jira/browse/CXF-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-5354: Attachment: jaxws_dispatch_provider_test_faultto.zip This is a modification of the 2.7.6

[jira] [Comment Edited] (CXF-5354) faultTo address is ignored when fault is thrown

[ https://issues.apache.org/jira/browse/CXF-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13803572#comment-13803572 ] Jesse Pangburn edited comment on CXF-5354 at 10/23/13 11:58 PM:

[jira] [Created] (CXF-5354) faultTo address is ignored when fault is thrown

Jesse Pangburn created CXF-5354: --- Summary: faultTo address is ignored when fault is thrown Key: CXF-5354 URL: https://issues.apache.org/jira/browse/CXF-5354 Project: CXF Issue Type: Bug

[jira] [Commented] (CXF-5354) faultTo address is ignored when fault is thrown

[ https://issues.apache.org/jira/browse/CXF-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13802531#comment-13802531 ] Jesse Pangburn commented on CXF-5354: - Issue 4382 indicates this should work, but at

[jira] [Created] (CXF-5317) Policy exception handler throws away useful exception stack trace

Jesse Pangburn created CXF-5317: --- Summary: Policy exception handler throws away useful exception stack trace Key: CXF-5317 URL: https://issues.apache.org/jira/browse/CXF-5317 Project: CXF

[jira] [Updated] (CXF-5317) Policy exception handler throws away useful exception stack trace

[ https://issues.apache.org/jira/browse/CXF-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-5317: Attachment: AbstractBindingBuilder.patch I copied the original 2.7.7 AbstractBindingBuilder.java to

[jira] [Updated] (CXF-5317) Policy exception handler throws away useful exception stack trace

[ https://issues.apache.org/jira/browse/CXF-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-5317: Description: I had a working WS-Policy which was encrypting the SOAP body with a UsernameToken

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776510#comment-13776510 ] Jesse Pangburn commented on CXF-5267: - Fixed in Java 7 is good to know, thanks! So for

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13765849#comment-13765849 ] Jesse Pangburn commented on CXF-5267: - I found this page about it:

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13764565#comment-13764565 ] Jesse Pangburn commented on CXF-5267: - Hi Sergey, well I can say I'm completely

[jira] [Commented] (CXF-5268) Automatic WS-Policy computation should be possible on Dispatch clients without setting operation manually

[ https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13764476#comment-13764476 ] Jesse Pangburn commented on CXF-5268: - Awesome! From the first time I looked at this

[jira] [Commented] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

[ https://issues.apache.org/jira/browse/CXF-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13764784#comment-13764784 ] Jesse Pangburn commented on CXF-5267: - Do you mean write a similar test using Apache

[jira] [Created] (CXF-5267) WebClient using POST with chunking enabled (the default) can't read 401 error response stream

Jesse Pangburn created CXF-5267: --- Summary: WebClient using POST with chunking enabled (the default) can't read 401 error response stream Key: CXF-5267 URL: https://issues.apache.org/jira/browse/CXF-5267

[jira] [Created] (CXF-5268) Automatic WS-Policy computation should be possible on Dispatch clients without setting operation manually

Jesse Pangburn created CXF-5268: --- Summary: Automatic WS-Policy computation should be possible on Dispatch clients without setting operation manually Key: CXF-5268 URL: https://issues.apache.org/jira/browse/CXF-5268

[jira] [Updated] (CXF-5268) Automatic WS-Policy computation should be possible on Dispatch clients without setting operation manually

[ https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-5268: Attachment: DispatchImpl.java.patch This patch goes on the 2.7.6 release version of

[jira] [Created] (CXF-4339) Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled

Jesse Pangburn created CXF-4339: --- Summary: Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled Key: CXF-4339 URL: https://issues.apache.org/jira/browse/CXF-4339

[jira] [Updated] (CXF-4339) Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled

[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-4339: Description: If I have a Dispatch client and I have WS-Addressing enabled on it and I send a

[jira] [Commented] (CXF-4339) Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled

[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13281997#comment-13281997 ] Jesse Pangburn commented on CXF-4339: - Hi Aki, I'm sorry, I thought the action taken

[jira] [Closed] (CXF-4339) Dispatch client fails to set soap action header automatically unless WS-Addressing is enabled

[ https://issues.apache.org/jira/browse/CXF-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn closed CXF-4339. --- Resolution: Not A Problem Fix Version/s: Invalid This was not a bug, it was my own

[jira] [Commented] (CXF-4262) oauth sample in 2.5.3 release does not build without POM changes

[ https://issues.apache.org/jira/browse/CXF-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13261193#comment-13261193 ] Jesse Pangburn commented on CXF-4262: - That is a better example in many ways, the only

[jira] [Created] (CXF-4262) oauth sample in 2.5.3 release does not build without POM changes

Jesse Pangburn created CXF-4262: --- Summary: oauth sample in 2.5.3 release does not build without POM changes Key: CXF-4262 URL: https://issues.apache.org/jira/browse/CXF-4262 Project: CXF

[jira] [Updated] (CXF-4262) oauth sample in 2.5.3 release does not build without POM changes

[ https://issues.apache.org/jira/browse/CXF-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-4262: Description: Tried building oauth client and server samples in 2.5.3 release using provided

[jira] [Created] (CXF-3802) jaxws Provider doesn't allow override of outbound ws addressing headers

jaxws Provider doesn't allow override of outbound ws addressing headers --- Key: CXF-3802 URL: https://issues.apache.org/jira/browse/CXF-3802 Project: CXF Issue Type: Bug

[jira] [Closed] (CXF-3747) Dispatch client fails to set WS-Addressing Action header when WSDL's soap:operation does not have a style attribute

[ https://issues.apache.org/jira/browse/CXF-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn closed CXF-3747. --- Verified by downloading latest version of affected file(s) from SVN on the 2.4.x fixes branch, building

[jira] [Closed] (CXF-3748) Using Dispatch API with SOAPMessage type fails to set WS-Addressing action header properly if there's whitespace after the soap:body

[ https://issues.apache.org/jira/browse/CXF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn closed CXF-3748. --- Verified by downloading latest version of affected file(s) from SVN on the 2.4.x fixes branch and

[jira] [Closed] (CXF-3749) Using Dispatch API with Source type fails to set WS-Addressing action header properly in MESSAGE mode with SOAP 1.2

[ https://issues.apache.org/jira/browse/CXF-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn closed CXF-3749. --- Verified by downloading latest version of affected file(s) from SVN on the 2.4.x fixes branch and checked

[jira] [Updated] (CXF-3754) Dispatch API's ServiceImpl class fails to copy address/properties/bus/handlers from jaxws:client spring configuration

[ https://issues.apache.org/jira/browse/CXF-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-3754: Attachment: patch3754.txt This patch is the same as the first one except it adds the handler chain

[jira] [Created] (CXF-3754) Dispatch API's ServiceImpl class fails to copy address/properties/bus/handlers from jaxws:client spring configuration

Dispatch API's ServiceImpl class fails to copy address/properties/bus/handlers from jaxws:client spring configuration - Key: CXF-3754 URL:

[jira] [Updated] (CXF-3754) Dispatch API's ServiceImpl class fails to copy address/properties/bus/handlers from jaxws:client spring configuration

[ https://issues.apache.org/jira/browse/CXF-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-3754: Attachment: patch3754_partial.txt This patch addresses all issues in this bug report except for the

[jira] [Created] (CXF-3755) setting wsa:addressing feature in cxf:bus causes wrong action header to be sent when using Dispatch API

setting wsa:addressing feature in cxf:bus causes wrong action header to be sent when using Dispatch API --- Key: CXF-3755 URL:

[jira] [Updated] (CXF-3755) setting wsa:addressing feature in cxf:bus causes wrong action header to be sent when using Dispatch API

[ https://issues.apache.org/jira/browse/CXF-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-3755: Attachment: patch3754_partial_and3755.txt The attached patch file fixes this bug (3755) and also

[jira] [Created] (CXF-3749) Using Dispatch API with Source type fails to set WS-Addressing action header properly in MESSAGE mode with SOAP 1.2

Using Dispatch API with Source type fails to set WS-Addressing action header properly in MESSAGE mode with SOAP 1.2 --- Key: CXF-3749 URL:

[jira] [Updated] (CXF-3749) Using Dispatch API with Source type fails to set WS-Addressing action header properly in MESSAGE mode with SOAP 1.2

[ https://issues.apache.org/jira/browse/CXF-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-3749: Attachment: patch3747and3748and3749.txt Since I've patched two other defects on this same file in

[jira] [Created] (CXF-3747) Dispatch client fails to set WS-Addressing Action header when WSDL's soap:operation does not have a style attribute

Dispatch client fails to set WS-Addressing Action header when WSDL's soap:operation does not have a style attribute --- Key: CXF-3747 URL:

[jira] [Created] (CXF-3748) Using Dispatch API with SOAPMessage type fails to set WS-Addressing action header properly if there's whitespace after the soap:body

Using Dispatch API with SOAPMessage type fails to set WS-Addressing action header properly if there's whitespace after the soap:body Key: CXF-3748

[jira] [Updated] (CXF-3748) Using Dispatch API with SOAPMessage type fails to set WS-Addressing action header properly if there's whitespace after the soap:body

[ https://issues.apache.org/jira/browse/CXF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-3748: Attachment: patch3747and3748.txt patch3748.txt Two patches are attached.

[jira] [Updated] (CXF-3747) Dispatch client fails to set WS-Addressing Action header when WSDL's soap:operation does not have a style attribute

[ https://issues.apache.org/jira/browse/CXF-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Pangburn updated CXF-3747: Attachment: patch3747and3748.txt patch3747.txt Two patches are attached.