[jira] [Resolved] (CXF-3740) CXF WSA handler have to throw WebServiceException on client side if addressing is required but not found in the message

[ https://issues.apache.org/jira/browse/CXF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3740. Resolution: Fixed Fix Version/s: (was: 2.3.7) > CXF WSA handler have to throw WebServiceException on clien

[jira] [Commented] (CXF-3740) CXF WSA handler have to throw WebServiceException on client side if addressing is required but not found in the message

[ https://issues.apache.org/jira/browse/CXF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087575#comment-13087575 ] jimma commented on CXF-3740: Patch is applied. Thanks Richard! > CXF WSA handler have to throw

[jira] [Assigned] (CXF-3740) CXF WSA handler have to throw WebServiceException on client side if addressing is required but not found in the message

[ https://issues.apache.org/jira/browse/CXF-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma reassigned CXF-3740: -- Assignee: jimma > CXF WSA handler have to throw WebServiceException on client side if > addressing is required b

[jira] [Issue Comment Edited] (CXF-3706) It's impossible to use wss4j.action.map and wss4j.processor.map with WS-Policy

[ https://issues.apache.org/jira/browse/CXF-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087568#comment-13087568 ] Sergey Zhemzhitsky edited comment on CXF-3706 at 8/19/11 6:26 AM:

[jira] [Commented] (CXF-3706) It's impossible to use wss4j.action.map and wss4j.processor.map with WS-Policy

[ https://issues.apache.org/jira/browse/CXF-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087568#comment-13087568 ] Sergey Zhemzhitsky commented on CXF-3706: - Hi Colm, I would like to use custom algo

[jira] [Commented] (CXF-3750) Sometimes, CXF servlet will blocked until bussiness logical finished for one-way operation

[ https://issues.apache.org/jira/browse/CXF-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087548#comment-13087548 ] ext2 commented on CXF-3750: --- if the execute sequence as following, every thing is ok. there is n

[jira] [Updated] (CXF-3750) Sometimes, CXF servlet will blocked until bussiness logical finished for one-way operation

[ https://issues.apache.org/jira/browse/CXF-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ext2 updated CXF-3750: -- Attachment: oneway-deadlock.zip ProductClient.java: it contains a comment indicate how to change source code of CXF to s

[jira] [Updated] (CXF-3750) Sometimes, CXF servlet will blocked until bussiness logical finished for one-way operation

[ https://issues.apache.org/jira/browse/CXF-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ext2 updated CXF-3750: -- Summary: Sometimes, CXF servlet will blocked until bussiness logical finished for one-way operation (was: Sometimes, CXF

[jira] [Created] (CXF-3750) Sometimes, CXF service will blocked until bussiness logical finished for one-way operation

Sometimes, CXF service will blocked until bussiness logical finished for one-way operation -- Key: CXF-3750 URL: https://issues.apache.org/jira/browse/CXF-3750 Pr

[jira] [Commented] (CXF-3741) Use the Jetty all-in-one jar

[ https://issues.apache.org/jira/browse/CXF-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087496#comment-13087496 ] Gary D. Gregory commented on CXF-3741: -- Hi Dan, Roger that. What kind of duplication?

[jira] [Reopened] (CXF-3741) Use the Jetty all-in-one jar

[ https://issues.apache.org/jira/browse/CXF-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp reopened CXF-3741: -- Missed the aggregate directory. Thanks. Definitely need to think about this a bit. It changes dependenci

[jira] [Commented] (CXF-3746) Migrate to Joda-Time 2.0 from 1.6.2.

[ https://issues.apache.org/jira/browse/CXF-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087488#comment-13087488 ] Gary D. Gregory commented on CXF-3746: -- Thank you for the explanation. > Migrate to J

[jira] [Commented] (CXF-3741) Use the Jetty all-in-one jar

[ https://issues.apache.org/jira/browse/CXF-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087487#comment-13087487 ] Gary D. Gregory commented on CXF-3741: -- But it is in the repo: http://repo1.maven.org/

[jira] [Resolved] (CXF-3738) Remove the Bouncy Castle license from the distribution.

[ https://issues.apache.org/jira/browse/CXF-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3738. -- Resolution: Fixed Fix Version/s: 2.4.3 Assignee: Daniel Kulp > Remove the Bouncy Castle l

[jira] [Resolved] (CXF-3741) Use the Jetty all-in-one jar

[ https://issues.apache.org/jira/browse/CXF-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3741. -- Resolution: Won't Fix Fix Version/s: Invalid Assignee: Daniel Kulp There isn't a jetty-a

[jira] [Resolved] (CXF-3746) Migrate to Joda-Time 2.0 from 1.6.2.

[ https://issues.apache.org/jira/browse/CXF-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3746. -- Resolution: Won't Fix Fix Version/s: Invalid Assignee: Daniel Kulp CXF doesn't depend di

[jira] [Resolved] (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 ] Daniel Kulp resolved CXF-3747. -- Resolution: Fixed Fix Version/s: 2.4.3 > Dispatch client fails to set WS-Addressing Action header

[jira] [Resolved] (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 ] Daniel Kulp resolved CXF-3749. -- Resolution: Fixed Fix Version/s: 2.4.3 Patch applied, but I had to fix some checkstyle issues and

[jira] [Resolved] (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 ] Daniel Kulp resolved CXF-3748. -- Resolution: Fixed Fix Version/s: 2.4.3 > Using Dispatch API with SOAPMessage type fails to set WS-

[jira] [Assigned] (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 ] Daniel Kulp reassigned CXF-3748: Assignee: Daniel Kulp > Using Dispatch API with SOAPMessage type fails to set WS-Addressing action >

[jira] [Assigned] (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 ] Daniel Kulp reassigned CXF-3747: Assignee: Daniel Kulp > Dispatch client fails to set WS-Addressing Action header when WSDL's > soap:

[jira] [Assigned] (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 ] Daniel Kulp reassigned CXF-3749: Assignee: Daniel Kulp > Using Dispatch API with Source type fails to set WS-Addressing action header

[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: https://issu

[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 the

[jira] [Commented] (CXF-3706) It's impossible to use wss4j.action.map and wss4j.processor.map with WS-Policy

[ https://issues.apache.org/jira/browse/CXF-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087065#comment-13087065 ] Colm O hEigeartaigh commented on CXF-3706: -- What kind of customization do you want

[jira] [Resolved] (CXF-3721) WS-Security does not work if java.security.Key.getEncoded() returns null for private and secret keys

[ https://issues.apache.org/jira/browse/CXF-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-3721. -- Resolution: Not A Problem Fix Version/s: (was: NeedMoreInfo) Resolving this a