[jira] [Resolved] (CXF-3442) Fault should not swallow the cause exception message

[ https://issues.apache.org/jira/browse/CXF-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-3442. --- Resolution: Fixed > Fault should not swallow the cause exception message >

[jira] [Resolved] (CXF-3445) Support the faultStackTraceEnabled option in Soap12FaultOutputInterceptor

[ https://issues.apache.org/jira/browse/CXF-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-3445. --- Resolution: Fixed Fix Version/s: 2.3.4 2.4 > Support the faultStackTraceEnabl

[jira] [Commented] (CXF-3307) SAAJ Issue with Weblogic 10.3.4 or 10.3.3

[ https://issues.apache.org/jira/browse/CXF-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019143#comment-13019143 ] Gladwin commented on CXF-3307: -- Web Service with CXF and Weblogic 11g issue has been resolved w

[jira] [Commented] (CXF-1750) CXF 2.1.1 And WebLogic 10

[ https://issues.apache.org/jira/browse/CXF-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019142#comment-13019142 ] Gladwin commented on CXF-1750: -- Web Service with CXF and Weblogic 11g issue has been resolved w

[jira] [Issue Comment Edited] (CXF-3363) Use MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL) instead of MessageFactory.newInstance()

[ https://issues.apache.org/jira/browse/CXF-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019139#comment-13019139 ] Gladwin edited comment on CXF-3363 at 4/13/11 12:37 AM: Tested and v

[jira] [Commented] (CXF-3363) Use MessageFactory.newInstance(SOAPConstants.SOAP_1_1_PROTOCOL) instead of MessageFactory.newInstance()

[ https://issues.apache.org/jira/browse/CXF-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019139#comment-13019139 ] Gladwin commented on CXF-3363: -- Tested and verified this fix on Weblogic 11g with CXF-2.3.4 >

[jira] [Commented] (CXF-3454) CXFRS doesn't work when there are multiple optional parameters in a @Path annotation

[ https://issues.apache.org/jira/browse/CXF-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019117#comment-13019117 ] Guillermo Castro commented on CXF-3454: --- Specify one path with several options? Let's

[jira] [Commented] (CXF-3455) Migrate to current version of Neethi (2.0.5 or 3.0.0)

[ https://issues.apache.org/jira/browse/CXF-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019089#comment-13019089 ] Gary D. Gregory commented on CXF-3455: -- Great, thank you Dan. > Migrate to current ve

[jira] [Resolved] (CXF-3455) Migrate to current version of Neethi (2.0.5 or 3.0.0)

[ https://issues.apache.org/jira/browse/CXF-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3455. -- Resolution: Fixed Fix Version/s: 2.3.4 2.4 Assignee: Daniel Kulp I ju

[jira] [Commented] (CXF-3454) CXFRS doesn't work when there are multiple optional parameters in a @Path annotation

[ https://issues.apache.org/jira/browse/CXF-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019042#comment-13019042 ] Sergey Beryozkin commented on CXF-3454: --- Every optional parameter has groups, so it is

[jira] [Created] (CXF-3455) Migrate to current version of Neethi (2.0.5 or 3.0.0)

Migrate to current version of Neethi (2.0.5 or 3.0.0) - Key: CXF-3455 URL: https://issues.apache.org/jira/browse/CXF-3455 Project: CXF Issue Type: Improvement Affects Versions: 2.3.3

[jira] [Updated] (CXF-3454) CXFRS doesn't work when there are multiple optional parameters in a @Path annotation

[ https://issues.apache.org/jira/browse/CXF-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillermo Castro updated CXF-3454: -- Attachment: URITemplateTest.java Test case for Issue > CXFRS doesn't work when there are multipl

[jira] [Created] (CXF-3454) CXFRS doesn't work when there are multiple optional parameters in a @Path annotation

CXFRS doesn't work when there are multiple optional parameters in a @Path annotation Key: CXF-3454 URL: https://issues.apache.org/jira/browse/CXF-3454 Project: CXF

[jira] [Reopened] (CXF-3453) WS-Security signed headers fail when schema validation enabled

[ https://issues.apache.org/jira/browse/CXF-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ross M. Lodge reopened CXF-3453: The applied changes only fix one of two reported errors: the tests in the attached zip produce both c

[jira] [Commented] (CXF-3452) WS-Security Encrypted headers fail with JAX-WS Binding

[ https://issues.apache.org/jira/browse/CXF-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018931#comment-13018931 ] Ross M. Lodge commented on CXF-3452: The fix applied in the latest snapshot definitely f

[jira] [Updated] (CXF-3366) Avoid parsing the SOAP Body to DOM in WS-Security processing unless necessary

[ https://issues.apache.org/jira/browse/CXF-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CXF-3366: - Description: This task is to take advantage of a new feature in WSS4J 1.6, which allows a

[jira] [Created] (DOSGI-93) CXF DOSGi single bundle distribution does not work with servlets 3.0

CXF DOSGi single bundle distribution does not work with servlets 3.0 Key: DOSGI-93 URL: https://issues.apache.org/jira/browse/DOSGI-93 Project: CXF Distributed OSGi Issue T

[jira] [Resolved] (CXF-3432) Support WS-SecurityPolicy SamlToken expressions

[ https://issues.apache.org/jira/browse/CXF-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-3432. -- Resolution: Fixed > Support WS-SecurityPolicy SamlToken expressions > ---