From zcarey@example.org Mon Aug 03 08:14:30 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 32179 invoked from network); 3 Aug 2009 08:14:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Aug 2009 08:14:30 -0000 Received: (qmail 51756 invoked by uid 500); 3 Aug 2009 08:14:35 -0000 Delivered-To: zcarey@example.org Received: (qmail 51694 invoked by uid 500); 3 Aug 2009 08:14:35 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 51684 invoked by uid 99); 3 Aug 2009 08:14:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 08:14:35 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO minotaur.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 03 Aug 2009 08:14:32 +0000 Received: (qmail 32153 invoked by uid 2342); 3 Aug 2009 08:14:05 -0000 Date: 3 Aug 2009 08:14:00 -0000 Message-ID: <zcarey@example.org> TO: zcarey@example.org FROM: zcarey@example.org SUBJECT: Issues with Attachments: week of 2009-08-03 X-Virus-Checked: Checked by ClamAV on apache.org CXF - Monday, August 3, 2009 16 Issues with Attachments (sorted oldest to newest) [CXF-1459] ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2 (2008-02-29 - Improvement - Tom Schroedl) http://issues.apache.org/jira/browse/CXF-1459 [CXF-1497] Supplied WSDL soap:address not being updated with actual host name when queried. (2008-04-01 - Test - Brent Moore) http://issues.apache.org/jira/browse/CXF-1497 [CXF-1598] Soap message generated via JaxWsProxyFactoryBean created client fails (2008-05-20 - Bug - Alton Idowu) http://issues.apache.org/jira/browse/CXF-1598 [CXF-1768] WSDL First leads to javax.wsdl.WSDLException: WSDLException (2008-08-28 - Bug - Mirko Sertic) http://issues.apache.org/jira/browse/CXF-1768 [CXF-1785] wsdlLocation attribute and XmlBeans: Getting NullPointerException/UNMARSHALL_ERROR (2008-09-05 - Bug - Juan Velez) http://issues.apache.org/jira/browse/CXF-1785 [CXF-1956] Garbage Appended to SOAP Envelope (2008-12-24 - Bug - Ron Grimes) http://issues.apache.org/jira/browse/CXF-1956 [CXF-2093] CXF Compatiblity (2009-03-06 - Bug - Brian Relph) http://issues.apache.org/jira/browse/CXF-2093 [CXF-2199] NullPointerException from MapType (2009-04-30 - Bug - Valerio Schiavoni) http://issues.apache.org/jira/browse/CXF-2199 [CXF-2216] CXF Import-Package version specifiers causes 'uses' conflict (2009-05-14 - Bug - Hendy Irawan) http://issues.apache.org/jira/browse/CXF-2216 [CXF-2231] JaxWs client send null values resulting in empty body of soap message (2009-05-21 - Bug - Valerio Schiavoni) http://issues.apache.org/jira/browse/CXF-2231 [CXF-2257] Implement client side supporting SOAP over TCP (2009-06-07 - Sub-task - Krzysztof Wilkos) http://issues.apache.org/jira/browse/CXF-2257 [CXF-2265] JMS Test Suite. (2009-06-08 - Sub-task - Liu Cong) http://issues.apache.org/jira/browse/CXF-2265 [CXF-2286] CXF locking jars in Tomcat when undeployed preventing hot deployment / eating up permgen (2009-06-13 - Bug - Jerome Waibel) http://issues.apache.org/jira/browse/CXF-2286 [CXF-2340] Unmarshalling Error: UndeclaredPrefix: Cannot resolve 'ns0:Xxx' as a QName: the prefix 'ns0' is not declared (2009-07-14 - Bug - John Pfeifer IV) http://issues.apache.org/jira/browse/CXF-2340 [CXF-2372] Allow JMS XAResource to participate in J2EE transaction (2009-07-30 - Improvement - Seumas Soltysik) http://issues.apache.org/jira/browse/CXF-2372 [CXF-2374] Handle possible number format exception when reading primitive param (2009-07-31 - Bug - Jorge L. Williams) http://issues.apache.org/jira/browse/CXF-2374 From zcarey@example.org Mon Aug 03 08:37:32 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 36021 invoked from network); 3 Aug 2009 08:37:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Aug 2009 08:37:31 -0000 Received: (qmail 64276 invoked by uid 500); 3 Aug 2009 08:37:37 -0000 Delivered-To: zcarey@example.org Received: (qmail 64211 invoked by uid 500); 3 Aug 2009 08:37:36 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 64201 invoked by uid 99); 3 Aug 2009 08:37:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 08:37:36 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 08:37:34 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C8459234C046 for <zcarey@example.org>; Mon, 3 Aug 2009 01:37:14 -0700 (PDT) Message-ID: <86231625.1249288634807.JavaMail.jira@brutus> Date: Mon, 3 Aug 2009 01:37:14 -0700 (PDT) From: "Gyorgy Orban (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Created: (CXF-2375) CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes. -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: CXF-2375 URL: https://issues.apache.org/jira/browse/CXF-2375 Project: CXF Issue Type: Improvement Components: JAX-WS Runtime Reporter: Gyorgy Orban Attachments: JaxWsServiceConfiguration.java.patch AOP implementations and other frameworks that use bytecode modification may generate synthetic methods on the SEI that cannot be controlled or customized by the user (for example, AspecJ generates getters/setters for generated members, and these methods cannot be removed). These methods will show up as operations on the SEI, which is usually not the desired behaviour. We locally patched CXF to avoid this, please see the attached patch that worked for us. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Mon Aug 03 08:37:32 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 36031 invoked from network); 3 Aug 2009 08:37:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Aug 2009 08:37:32 -0000 Received: (qmail 64379 invoked by uid 500); 3 Aug 2009 08:37:37 -0000 Delivered-To: zcarey@example.org Received: (qmail 64335 invoked by uid 500); 3 Aug 2009 08:37:37 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 64224 invoked by uid 99); 3 Aug 2009 08:37:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 08:37:36 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 08:37:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id EBCBB234C1EB for <zcarey@example.org>; Mon, 3 Aug 2009 01:37:14 -0700 (PDT) Message-ID: <1750251426.1249288634965.JavaMail.jira@brutus> Date: Mon, 3 Aug 2009 01:37:14 -0700 (PDT) From: "Gyorgy Orban (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Updated: (CXF-2375) CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes. In-Reply-To: <86231625.1249288634807.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2375: ------------------------------ Attachment: JaxWsServiceConfiguration.java.patch > CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes. > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CXF-2375 > URL: https://issues.apache.org/jira/browse/CXF-2375 > Project: CXF > Issue Type: Improvement > Components: JAX-WS Runtime > Reporter: Gyorgy Orban > Attachments: JaxWsServiceConfiguration.java.patch > > > AOP implementations and other frameworks that use bytecode modification may generate synthetic methods on the SEI that cannot be controlled or customized by the user (for example, AspecJ generates getters/setters for generated members, and these methods cannot be removed). These methods will show up as operations on the SEI, which is usually not the desired behaviour. We locally patched CXF to avoid this, please see the attached patch that worked for us. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Mon Aug 03 17:59:34 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 18355 invoked from network); 3 Aug 2009 17:59:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Aug 2009 17:59:34 -0000 Received: (qmail 39418 invoked by uid 500); 3 Aug 2009 17:59:39 -0000 Delivered-To: zcarey@example.org Received: (qmail 39337 invoked by uid 500); 3 Aug 2009 17:59:39 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 39314 invoked by uid 99); 3 Aug 2009 17:59:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 17:59:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 17:59:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C4D94234C045 for <zcarey@example.org>; Mon, 3 Aug 2009 10:59:14 -0700 (PDT) Message-ID: <779935922.1249322354791.JavaMail.jira@brutus> Date: Mon, 3 Aug 2009 10:59:14 -0700 (PDT) From: "S Sebastian (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Created: (CXF-2376) CXF Maven Plugin fails to read WSDL file from classpath or jar file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org CXF Maven Plugin fails to read WSDL file from classpath or jar file ------------------------------------------------------------------- Key: CXF-2376 URL: https://issues.apache.org/jira/browse/CXF-2376 Project: CXF Issue Type: Bug Components: Tooling Affects Versions: 2.2.2 Reporter: S Sebastian The CXF maven plugin "cxf-codegen-plugin" fails to read WSDL files from a jar file deployed on a maven repository whic was declared as a dependency by the webservice client project While setting the following for wsdlOption <wsdlOption> <wsdl>classpath:/myfolder/myown.wsdl</wsdl> --- ---- </wsdlOption> the build fails with the following error org.apache.cxf.wsdl11.WSDLRuntimeException: Fail to create wsdl definition from : file:/classpath: /myfolder/myown.wsdl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Mon Aug 03 20:03:34 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 77284 invoked from network); 3 Aug 2009 20:03:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Aug 2009 20:03:34 -0000 Received: (qmail 95765 invoked by uid 500); 3 Aug 2009 20:03:39 -0000 Delivered-To: zcarey@example.org Received: (qmail 95717 invoked by uid 500); 3 Aug 2009 20:03:39 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 95707 invoked by uid 99); 3 Aug 2009 20:03:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 20:03:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 20:03:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id CC4A0234C045 for <zcarey@example.org>; Mon, 3 Aug 2009 13:03:14 -0700 (PDT) Message-ID: <218.435.3799.1249329794822.JavaMail.jira@brutus> Date: Mon, 3 Aug 2009 13:03:14 -0700 (PDT) From: "Daniel Kulp (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Resolved: (CXF-2374) Handle possible number format exception when reading primitive param In-Reply-To: <1428319547.1249074494799.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2374. ------------------------------ Resolution: Fixed Fix Version/s: 2.2.4 Assignee: Daniel Kulp > Handle possible number format exception when reading primitive param > -------------------------------------------------------------------- > > Key: CXF-2374 > URL: https://issues.apache.org/jira/browse/CXF-2374 > Project: CXF > Issue Type: Bug > Components: REST > Reporter: Jorge L. Williams > Assignee: Daniel Kulp > Priority: Minor > Fix For: 2.2.4 > > Attachments: 0001-Handle-possible-number-format-exception-when-reading.patch > > > We ran into this issue in JAX-RS: A request to something like /path/ > to/{id} where {id} is expected to be an integer would throw a > NumberFormatException in the case where we send something other than > an integer (/path/to/bla, for example). The NumberFormatException > didn't find its way to our ExceptionMapper and resulted in an XMLFault > being serialized which is wrong. > The attached patch fixes things for us. We simply capture the NFE and > resend it as a WebApplicationException -- we send a 404 when we're > dealing with path params and 400 otherwise. The patch is against the > current trunk but honestly we've really only tested against 2.2.2 -- > since that's what we're using :-) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Mon Aug 03 20:05:34 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 77648 invoked from network); 3 Aug 2009 20:05:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Aug 2009 20:05:34 -0000 Received: (qmail 96735 invoked by uid 500); 3 Aug 2009 20:05:39 -0000 Delivered-To: zcarey@example.org Received: (qmail 96669 invoked by uid 500); 3 Aug 2009 20:05:39 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 96658 invoked by uid 99); 3 Aug 2009 20:05:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 20:05:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Aug 2009 20:05:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C6FFC234C045 for <zcarey@example.org>; Mon, 3 Aug 2009 13:05:14 -0700 (PDT) Message-ID: <1830542890.1249329914800.JavaMail.jira@brutus> Date: Mon, 3 Aug 2009 13:05:14 -0700 (PDT) From: "Daniel Kulp (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Resolved: (CXF-2375) CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes. In-Reply-To: <86231625.1249288634807.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2375. ------------------------------ Resolution: Fixed Fix Version/s: 2.2.4 2.1.7 Assignee: Daniel Kulp > CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes. > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CXF-2375 > URL: https://issues.apache.org/jira/browse/CXF-2375 > Project: CXF > Issue Type: Improvement > Components: JAX-WS Runtime > Reporter: Gyorgy Orban > Assignee: Daniel Kulp > Fix For: 2.1.7, 2.2.4 > > Attachments: JaxWsServiceConfiguration.java.patch > > > AOP implementations and other frameworks that use bytecode modification may generate synthetic methods on the SEI that cannot be controlled or customized by the user (for example, AspecJ generates getters/setters for generated members, and these methods cannot be removed). These methods will show up as operations on the SEI, which is usually not the desired behaviour. We locally patched CXF to avoid this, please see the attached patch that worked for us. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 09:14:32 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 40832 invoked from network); 4 Aug 2009 09:14:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 09:14:32 -0000 Received: (qmail 18888 invoked by uid 500); 4 Aug 2009 09:14:37 -0000 Delivered-To: zcarey@example.org Received: (qmail 18858 invoked by uid 500); 4 Aug 2009 09:14:37 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 18848 invoked by uid 99); 4 Aug 2009 09:14:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 09:14:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 09:14:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C3E93234C045 for <zcarey@example.org>; Tue, 4 Aug 2009 02:14:14 -0700 (PDT) Message-ID: <1607837059.1249377254790.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 02:14:14 -0700 (PDT) From: "max laenzlinger (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Created: (CXF-2377) jaxrs Schemahandler inside tomcat lib folder - loading schema with classpath not working MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org jaxrs Schemahandler inside tomcat lib folder - loading schema with classpath not working ---------------------------------------------------------------------------------------- Key: CXF-2377 URL: https://issues.apache.org/jira/browse/CXF-2377 Project: CXF Issue Type: Bug Components: REST Affects Versions: 2.2.3 Reporter: max laenzlinger See summary. Using absolute path works, but using classpath cant find the schema file inside the webapplication-context. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 11:54:43 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 1894 invoked from network); 4 Aug 2009 11:54:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 11:54:43 -0000 Received: (qmail 90924 invoked by uid 500); 4 Aug 2009 11:54:48 -0000 Delivered-To: zcarey@example.org Received: (qmail 90879 invoked by uid 500); 4 Aug 2009 11:54:48 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 90869 invoked by uid 99); 4 Aug 2009 11:54:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 11:54:48 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED,FB_WORD1_END_DOLLAR X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 11:54:36 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 38D2A234C045 for <zcarey@example.org>; Tue, 4 Aug 2009 04:54:15 -0700 (PDT) Message-ID: <1272265537.1249386855221.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 04:54:15 -0700 (PDT) From: "Anders Storsveen (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Commented: (CXF-2338) Service created from WSDL doesn't deserialize correctly In-Reply-To: <1865228008.1247490795381.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738933#action_12738933 ] Anders Storsveen commented on CXF-2338: --------------------------------------- I tried changing all the elementFormDefault to unqualified with the same result.. > Service created from WSDL doesn't deserialize correctly > ------------------------------------------------------- > > Key: CXF-2338 > URL: https://issues.apache.org/jira/browse/CXF-2338 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding > Affects Versions: 2.2 > Environment: Darwin fou162.telenor.ntnu.no 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386 i386 > fou162:lib wakko$ mvn --version > Maven version: 2.0.9 > Java version: 1.6.0_13 > OS name: "mac os x" version: "10.5.7" arch: "x86_64" Family: "mac" > Reporter: Anders Storsveen > Fix For: Invalid > > > I'm trying to create a web service from a WSDL file and then run it embedded in my java application. I'm using maven to generate the classes and then create my own Impl and start it with Endpoint.publish(). This seems to work fine, however not all deserialize correctly. The method in question, takes two parameters, one String and one complex SmsMessage class. When I invoke the method the SOAP is fine (and there exists other services built on this wsdl that works) however the String in the method is set correctly, while the complex class is empty. > The wsdl file in question: http://px.pats.no/px/services/SmsNotification?WSDL > A web-based client that can be used to invoke the service: http://px.pats.no/px/4_short_messaging/index_notification_SMS.html > From my pom.xml file: > <plugin> > <groupId>org.apache.cxf</groupId> > <artifactId>cxf-codegen-plugin</artifactId> > <version>${cxf.version}</version> > <executions> > <execution> > <id>generate-sources</id> > <configuration> > <wsdlOptions> > <wsdlOption> > <!-- <wsdl>${basedir}/wsdl/SmsNotification.wsdl</wsdl> --> > <wsdl>http://px.pats.no/px/services/SmsNotification?WSDL</wsdl> > </wsdlOption> > </wsdlOptions> > </configuration> > <goals> > <goal>wsdl2java</goal> > </goals> > </execution> > </executions> > </plugin> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 14:35:34 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 577 invoked from network); 4 Aug 2009 14:35:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 14:35:34 -0000 Received: (qmail 54998 invoked by uid 500); 4 Aug 2009 14:35:39 -0000 Delivered-To: zcarey@example.org Received: (qmail 54979 invoked by uid 500); 4 Aug 2009 14:35:39 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 54969 invoked by uid 99); 4 Aug 2009 14:35:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 14:35:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 14:35:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id E7E31234C04B for <zcarey@example.org>; Tue, 4 Aug 2009 07:35:14 -0700 (PDT) Message-ID: <1444557787.1249396514948.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 07:35:14 -0700 (PDT) From: "Hemant Gakhar (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Created: (CXF-2378) Capturing SOAP body passed from SSRS in CXF method as a parameter MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Capturing SOAP body passed from SSRS in CXF method as a parameter ----------------------------------------------------------------- Key: CXF-2378 URL: https://issues.apache.org/jira/browse/CXF-2378 Project: CXF Issue Type: Task Components: Soap Binding Affects Versions: 2.1.2 Environment: Tomcat v 6 CXF 2.1.2 Windows XP Java 1.6.0_05 Reporter: Hemant Gakhar I am having problem recieving input from SSRS reporting services SOAP body as a parameter in the method defined under my CXF web service. I can see the SOAP header and body being passed but the parameter in the method is always null. Can someone suggest what is the best way to achieve this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 15:48:32 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 26692 invoked from network); 4 Aug 2009 15:48:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 15:48:32 -0000 Received: (qmail 89515 invoked by uid 500); 4 Aug 2009 15:48:37 -0000 Delivered-To: zcarey@example.org Received: (qmail 89492 invoked by uid 500); 4 Aug 2009 15:48:37 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 89482 invoked by uid 99); 4 Aug 2009 15:48:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 15:48:36 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 15:48:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id DB0CB234C044 for <zcarey@example.org>; Tue, 4 Aug 2009 08:48:14 -0700 (PDT) Message-ID: <1680084303.1249400894883.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 08:48:14 -0700 (PDT) From: "Alessio Soldano (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Assigned: (CXF-1514) Generated WSDL does not take 'transport-guarantee' in web.xml into account MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessio Soldano reassigned CXF-1514: ------------------------------------ Assignee: Alessio Soldano > Generated WSDL does not take 'transport-guarantee' in web.xml into account > -------------------------------------------------------------------------- > > Key: CXF-1514 > URL: https://issues.apache.org/jira/browse/CXF-1514 > Project: CXF > Issue Type: Sub-task > Components: Transports > Affects Versions: 2.0.5 > Reporter: Thomas Diesler > Assignee: Alessio Soldano > > [tdiesler@tddell trunk]$ ant -Dtest=jaxws/jbws1190 test > tests-run-internal: > [junit] Running org.jboss.test.ws.jaxws.jbws1190.JBWS1190TestCase > [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.989 sec > [junit] Test org.jboss.test.ws.jaxws.jbws1190.JBWS1190TestCase FAILED -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 15:50:32 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 26940 invoked from network); 4 Aug 2009 15:50:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 15:50:32 -0000 Received: (qmail 90744 invoked by uid 500); 4 Aug 2009 15:50:37 -0000 Delivered-To: zcarey@example.org Received: (qmail 90712 invoked by uid 500); 4 Aug 2009 15:50:37 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 90701 invoked by uid 99); 4 Aug 2009 15:50:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 15:50:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 15:50:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id CCC4F234C044 for <zcarey@example.org>; Tue, 4 Aug 2009 08:50:14 -0700 (PDT) Message-ID: <1911584846.1249401014837.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 08:50:14 -0700 (PDT) From: "Alessio Soldano (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Resolved: (CXF-1514) Generated WSDL does not take 'transport-guarantee' in web.xml into account MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessio Soldano resolved CXF-1514. ---------------------------------- Resolution: Invalid This was basically due to erroneously forcing the endpoint address in the cxf.xml to a wrong value. Solved on JBossWS side. > Generated WSDL does not take 'transport-guarantee' in web.xml into account > -------------------------------------------------------------------------- > > Key: CXF-1514 > URL: https://issues.apache.org/jira/browse/CXF-1514 > Project: CXF > Issue Type: Sub-task > Components: Transports > Affects Versions: 2.0.5 > Reporter: Thomas Diesler > Assignee: Alessio Soldano > > [tdiesler@tddell trunk]$ ant -Dtest=jaxws/jbws1190 test > tests-run-internal: > [junit] Running org.jboss.test.ws.jaxws.jbws1190.JBWS1190TestCase > [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.989 sec > [junit] Test org.jboss.test.ws.jaxws.jbws1190.JBWS1190TestCase FAILED -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 15:58:40 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 28425 invoked from network); 4 Aug 2009 15:58:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 15:58:40 -0000 Received: (qmail 98854 invoked by uid 500); 4 Aug 2009 15:58:44 -0000 Delivered-To: zcarey@example.org Received: (qmail 98745 invoked by uid 500); 4 Aug 2009 15:58:44 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 98708 invoked by uid 99); 4 Aug 2009 15:58:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 15:58:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 15:58:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id CF325234C044 for <zcarey@example.org>; Tue, 4 Aug 2009 08:58:14 -0700 (PDT) Message-ID: <657481937.1249401494834.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 08:58:14 -0700 (PDT) From: "Daniel Kulp (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Updated: (CXF-1514) Generated WSDL does not take 'transport-guarantee' in web.xml into account MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CXF-1514: ----------------------------- Fix Version/s: Invalid > Generated WSDL does not take 'transport-guarantee' in web.xml into account > -------------------------------------------------------------------------- > > Key: CXF-1514 > URL: https://issues.apache.org/jira/browse/CXF-1514 > Project: CXF > Issue Type: Sub-task > Components: Transports > Affects Versions: 2.0.5 > Reporter: Thomas Diesler > Assignee: Alessio Soldano > Fix For: Invalid > > > [tdiesler@tddell trunk]$ ant -Dtest=jaxws/jbws1190 test > tests-run-internal: > [junit] Running org.jboss.test.ws.jaxws.jbws1190.JBWS1190TestCase > [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.989 sec > [junit] Test org.jboss.test.ws.jaxws.jbws1190.JBWS1190TestCase FAILED -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 16:06:34 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 31845 invoked from network); 4 Aug 2009 16:06:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 16:06:34 -0000 Received: (qmail 12842 invoked by uid 500); 4 Aug 2009 16:06:39 -0000 Delivered-To: zcarey@example.org Received: (qmail 12801 invoked by uid 500); 4 Aug 2009 16:06:39 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 12790 invoked by uid 99); 4 Aug 2009 16:06:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 16:06:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 16:06:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D1DB5234C044 for <zcarey@example.org>; Tue, 4 Aug 2009 09:06:14 -0700 (PDT) Message-ID: <1548232131.1249401974844.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 09:06:14 -0700 (PDT) From: "Daniel Howard (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Commented: (CXF-1459) ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739016#action_12739016 ] Daniel Howard commented on CXF-1459: ------------------------------------ I am working with CXF 2.2.1 and WebLogic 10.3 on AIX using the IBM jvm and using -Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl system define. In org.apache.cxf.transport.https.HttpsURLConnectionFactory, I commented out handling the deprecated sun case in decorateWithTLS() method. Everything seems to be working. I am not able to set the hostname verifier nor the ssl socket factory with the cxf.xml, but it is using everything set by the WebLogic console and that is what I wanted. Am I missing something that is going to be a problem later for me? > ClassCastException occurs on HTTPS web service call made by app deployed to BEA WebLogic 9.2 > -------------------------------------------------------------------------------------------- > > Key: CXF-1459 > URL: https://issues.apache.org/jira/browse/CXF-1459 > Project: CXF > Issue Type: Improvement > Components: Integration > Affects Versions: 2.0.4 > Reporter: Tom Schroedl > Assignee: Benson Margulies > Attachments: HttpsURLConnectionFactory.patch > > > HTTPS web service call fails from webapp deployed in ear file to BEA 9.2 with following error: > java.lang.ClassCastException: weblogic.net.http.SOAPHttpsURLConnection > at org.apache.cxf.transport.https.HttpsURLConnectionFactory.createConnection(HttpsURLConnectionFactory.java:120) > My weblogic-application.xml contains: > <prefer-application-packages> > <package-name>javax.jws.*</package-name> > </prefer-application-packages> > The secure web service call works in Tomcat 5.5. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 16:15:36 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 33432 invoked from network); 4 Aug 2009 16:15:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 16:15:36 -0000 Received: (qmail 24381 invoked by uid 500); 4 Aug 2009 16:15:41 -0000 Delivered-To: zcarey@example.org Received: (qmail 24359 invoked by uid 500); 4 Aug 2009 16:15:41 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 24349 invoked by uid 99); 4 Aug 2009 16:15:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 16:15:41 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 16:15:38 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 2A613234C051 for <zcarey@example.org>; Tue, 4 Aug 2009 09:15:17 -0700 (PDT) Message-ID: <403495482.1249402517172.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 09:15:17 -0700 (PDT) From: "Daniel Kulp (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Created: (CXF-2379) mustUnderstand headers should be processed before endpoint dispatch MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org mustUnderstand headers should be processed before endpoint dispatch ------------------------------------------------------------------- Key: CXF-2379 URL: https://issues.apache.org/jira/browse/CXF-2379 Project: CXF Issue Type: Bug Reporter: Daniel Kulp Assignee: Daniel Kulp Fix For: 2.3 Per soap spec: The SOAP specification Part 1, section 2.4 (http://www.w3.org/TR/soap12-part1/#muprocessing) says: Mandatory SOAP header blocks are presumed to somehow modify the semantics of other SOAP header blocks or SOAP body elements. Therefore, for every mandatory SOAP header block targeted to a node, that node MUST either process the header block or not process the SOAP message at all, and instead generate a fault. Section 2.6 #3 (http://www.w3.org/TR/soap12-part1/#procsoapmsgs) says: If one or more of the SOAP header blocks identified in the preceding step are not understood by the node then generate a single SOAP fault with the Value of Code set to "env:MustUnderstand" (see 5.4.8 SOAP mustUnderstand Faults). If such a fault is generated, any further processing MUST NOT be done. Faults relating to the contents of the SOAP body MUST NOT be generated in this step. Thus, they should be faulted prior to endpoint being called. However, there needs to be a way for an endpoint to say "I'll handle this header" for compatibility and easy migration from prior versions of CXF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 17:34:32 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 61958 invoked from network); 4 Aug 2009 17:34:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 17:34:32 -0000 Received: (qmail 47859 invoked by uid 500); 4 Aug 2009 17:34:37 -0000 Delivered-To: zcarey@example.org Received: (qmail 47839 invoked by uid 500); 4 Aug 2009 17:34:37 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 47829 invoked by uid 99); 4 Aug 2009 17:34:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 17:34:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 17:34:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C2512234C045 for <zcarey@example.org>; Tue, 4 Aug 2009 10:34:14 -0700 (PDT) Message-ID: <867665996.1249407254782.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 10:34:14 -0700 (PDT) From: "Daniel Kulp (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Resolved: (CXF-2379) mustUnderstand headers should be processed before endpoint dispatch In-Reply-To: <403495482.1249402517172.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2379. ------------------------------ Resolution: Fixed > mustUnderstand headers should be processed before endpoint dispatch > ------------------------------------------------------------------- > > Key: CXF-2379 > URL: https://issues.apache.org/jira/browse/CXF-2379 > Project: CXF > Issue Type: Bug > Reporter: Daniel Kulp > Assignee: Daniel Kulp > Fix For: 2.3 > > > Per soap spec: > The SOAP specification Part 1, section 2.4 (http://www.w3.org/TR/soap12-part1/#muprocessing) says: > Mandatory SOAP header blocks are presumed to somehow modify the semantics of other SOAP header blocks or SOAP body elements. Therefore, for every mandatory SOAP header block targeted to a node, that node MUST either process the header block or not process the SOAP message at all, and instead generate a fault. > Section 2.6 #3 (http://www.w3.org/TR/soap12-part1/#procsoapmsgs) says: > If one or more of the SOAP header blocks identified in the preceding step are not understood by the node then generate a single SOAP fault with the Value of Code set to "env:MustUnderstand" (see 5.4.8 SOAP mustUnderstand Faults). If such a fault is generated, any further processing MUST NOT be done. Faults relating to the contents of the SOAP body MUST NOT be generated in this step. > Thus, they should be faulted prior to endpoint being called. However, there needs to be a way for an endpoint to say "I'll handle this header" for compatibility and easy migration from prior versions of CXF. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 17:50:44 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 69829 invoked from network); 4 Aug 2009 17:50:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 17:50:44 -0000 Received: (qmail 66231 invoked by uid 500); 4 Aug 2009 17:50:49 -0000 Delivered-To: zcarey@example.org Received: (qmail 66204 invoked by uid 500); 4 Aug 2009 17:50:49 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 66194 invoked by uid 99); 4 Aug 2009 17:50:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 17:50:49 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 17:50:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id B6F1E234C045 for <zcarey@example.org>; Tue, 4 Aug 2009 10:50:15 -0700 (PDT) Message-ID: <1525998166.1249408215741.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 10:50:15 -0700 (PDT) From: "Eugene Goldfarb (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Issue Comment Edited: (CXF-2113) http:client configuration with Spring PropertyPlaceholderConfigurer In-Reply-To: <83125563.1236953750606.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739060#action_12739060 ] Eugene Goldfarb edited comment on CXF-2113 at 8/4/09 10:48 AM: --------------------------------------------------------------- I submitted a similar issue earlier (CXF-1647), and showed how the developers at the Mule project were able to solve it (http://www.mulesource.org/jira/browse/MULE-1887?focusedCommentId=15746&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_15746). The solution requires modifications to the schema. was (Author: egoldfarb): I submitted a similar issue earlier (CXF-1647), and showed how the developers at the Mule project were able to solve it. The solution requires modifications to the schema. > http:client configuration with Spring PropertyPlaceholderConfigurer > ------------------------------------------------------------------- > > Key: CXF-2113 > URL: https://issues.apache.org/jira/browse/CXF-2113 > Project: CXF > Issue Type: Improvement > Components: Configuration > Affects Versions: 2.1.4 > Environment: any > Reporter: Sven Reinhardt > Assignee: Daniel Kulp > Priority: Minor > Fix For: 2.0.12, 2.1.6, 2.2.3 > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > -Problem: > changing configuration of proxy in conduit client with spring PropertyPlaceholderConfigurer > -Backgound: > to avoid rebuild of the application for differnt environments configurations are externalized in property files like this: > <bean > class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"> > <property name="locations" value="classpath:ws_client.properties" /> > </bean> > <http:conduit ... > > <http:client > ProxyServer="${ws.client.ProxyServer}" > ProxyServerPort="${ws.client.ProxyServer}" /> > </http:conduit> > ws_client.properties: > ws.client.ProxyServer=proxy > ws.client.ProxyServerPort=8080 > But this fails for two reasons: > 1. > org.apache.cxf.transports.http.configuration.HTTPClientPolicy getProxyServerPort() is an integer > ProxyServerPort="${ws.client.ProxyServer}" fails because the xml is validated in advance of the placeholder replacement (this might be a spring issue or else) > it could work if there would be a setProxyServerPortStr(String port) mehode > 2. > if there is no proxy it cant be "undone" because > org.apache.cxf.transport.http.HTTPConduit getProxy(HTTPClientPolicy) only cheks ProxyServer via HTTPClientPolicy.isSetProxyServer for null > if properties are set to: > ws.client.ProxyServer= > ws.client.ProxyServerPort=0 > it results in a connection refused, because the empty String proxy does not exist > if properties are commented out spring complains about it > - Proposed solution: > add methode setProxyServerPortStr(String port) > HTTPClientPolicy.isSetProxyServer also checks is proxyServer.length>0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 18:22:35 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 91242 invoked from network); 4 Aug 2009 18:22:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 18:22:35 -0000 Received: (qmail 16103 invoked by uid 500); 4 Aug 2009 18:22:40 -0000 Delivered-To: zcarey@example.org Received: (qmail 16086 invoked by uid 500); 4 Aug 2009 18:22:40 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 16076 invoked by uid 99); 4 Aug 2009 18:22:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 18:22:40 +0000 X-ASF-Spam-Status: No, hits=-1998.5 required=10.0 tests=ALL_TRUSTED,HS_INDEX_PARAM,WEIRD_PORT X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 18:22:36 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id E9EDD234C056 for <zcarey@example.org>; Tue, 4 Aug 2009 11:22:14 -0700 (PDT) Message-ID: <584791825.1249410134957.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 11:22:14 -0700 (PDT) From: "Fred Dushin (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Created: (CXF-2380) Cannot use custom client TLS settings when creating javax.xml.ws.Service from "https://...?wsdl" URL when WSDL contains https imports MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Cannot use custom client TLS settings when creating javax.xml.ws.Service from "https://...?wsdl" URL when WSDL contains https imports ------------------------------------------------------------------------------------------------------------------------------------- Key: CXF-2380 URL: https://issues.apache.org/jira/browse/CXF-2380 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Affects Versions: 2.2.3 Reporter: Fred Dushin (See enclosed test case, based on WSDL-first HTTPS sample) I have a CXF client and server. The server listens on https and publishes its WSDL at "https://...?wsdl". The scenario is also such that the WSDL published at this address has a wsdl:import, also with an https:// address, as in: <?xml version='1.0' encoding='UTF-8'?><wsdl:definitions ...> <wsdl:import location="https://localhost:9001/demo/secure?wsdl=Greeter.wsdl" namespace="http://apache.org/hello_world_soap_http"> </wsdl:import> ... </wsdl:definitions> The client is designed so that: 1. It bootstraps the client proxy using the live "https://...?wsdl" URL at the service endpoint 2. The bus is programatically configured to use a custom resource resolver (see client source code in enclosed test case), so that custom key material (trusted certificates, in this case) is used when resolving the resource. I.e., we are NOT relying on the JVM's trust-store to establish trust with the server (or so is our desire). The client will fail to download all of the WSDL during the call to Service.create. The stacktrace is: javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service. at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:149) at org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:65) at javax.xml.ws.Service.<init>(Service.java:36) at javax.xml.ws.Service.create(Service.java:116) at demo.hw_https.client.Client.call(Client.java:84) at demo.hw_https.client.Client.main(Client.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) at java.lang.Thread.run(Thread.java:613) Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service. at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:93) at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:204) at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:147) ... 11 more Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:import): faultCode=PARSER_ERROR: Problem parsing 'https://localhost:9001/demo/secure?wsdl=Greeter.wsdl'.: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested zcarey@example.org(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:210) at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:175) at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:91) ... 13 more Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested zcarey@example.org(Alerts.java:150) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1584) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:877) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1089) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1116) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1100) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:402) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:960) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) ... 24 more Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested zcarey@example.org(PKIXValidator.java:221) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:145) at sun.security.validator.Validator.validate(Validator.java:203) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172) at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java:320) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:841) ... 42 more Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested zcarey@example.org(SunCertPathBuilder.java:236) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216) ... 47 more Discussion: I believe what is happening here is that the com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL operation is not respecting the resource resolver that's been configured in CXF, when loading imported WSDLs, but that's just a guess. The reason I suspect this is that I have inserted printlns/breakpoints in the custom resource resolver, and we appear never to be calling resolve for the imported WSDL. Test Case: I'm submitting a test-case based on the wsdl-first https sample. To reproduce, use maven as per the usual instructions: mvn -Pserver mvn -Pclient Note that the client has been modified extensively in this sample. It will first make a plain http call to the service, to ensure that the server is at least running and nominally configured correctly. It will then attempt to connect over https, bootstrapping with the WSDL at the HTTPS service URL. It also has some code for adding a custom resource resolver, which is needed to set the TLS parameters on the client connection to the "https://...?wsdl" URL. (CXF is calling toString() the URL that's passed in to the Service.create operation, so that URL cannot carry the URLStreamHandler used to connect to the HTTPs URL. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 18:26:36 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 93279 invoked from network); 4 Aug 2009 18:26:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 18:26:36 -0000 Received: (qmail 26526 invoked by uid 500); 4 Aug 2009 18:26:41 -0000 Delivered-To: zcarey@example.org Received: (qmail 26506 invoked by uid 500); 4 Aug 2009 18:26:40 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 26496 invoked by uid 99); 4 Aug 2009 18:26:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 18:26:40 +0000 X-ASF-Spam-Status: No, hits=-1998.5 required=10.0 tests=ALL_TRUSTED,HS_INDEX_PARAM,WEIRD_PORT X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 18:26:36 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 70EA4234C046 for <zcarey@example.org>; Tue, 4 Aug 2009 11:26:15 -0700 (PDT) Message-ID: <179047592.1249410375461.JavaMail.jira@brutus> Date: Tue, 4 Aug 2009 11:26:15 -0700 (PDT) From: "Fred Dushin (JIRA)" <zcarey@example.org> To: zcarey@example.org Subject: [jira] Updated: (CXF-2380) Cannot use custom client TLS settings when creating javax.xml.ws.Service from "https://...?wsdl" URL when WSDL contains https imports In-Reply-To: <584791825.1249410134957.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Dushin updated CXF-2380: ----------------------------- Attachment: CXF-2380.tar.gz Test case for CXF-2380. Instructions: 1. Unpack, cd in CXF-2380 2. mvn -Pserver & 3. mvn -Pclient > Cannot use custom client TLS settings when creating javax.xml.ws.Service from "https://...?wsdl" URL when WSDL contains https imports > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: CXF-2380 > URL: https://issues.apache.org/jira/browse/CXF-2380 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime > Affects Versions: 2.2.3 > Reporter: Fred Dushin > Attachments: CXF-2380.tar.gz > > > (See enclosed test case, based on WSDL-first HTTPS sample) > I have a CXF client and server. The server listens on https and publishes its WSDL at "https://...?wsdl". > The scenario is also such that the WSDL published at this address has a wsdl:import, also with an https:// address, as in: > <?xml version='1.0' encoding='UTF-8'?><wsdl:definitions ...> > <wsdl:import location="https://localhost:9001/demo/secure?wsdl=Greeter.wsdl" namespace="http://apache.org/hello_world_soap_http"> > </wsdl:import> > ... > </wsdl:definitions> > The client is designed so that: > 1. It bootstraps the client proxy using the live "https://...?wsdl" URL at the service endpoint > 2. The bus is programatically configured to use a custom resource resolver (see client source code in enclosed test case), so that custom key material (trusted certificates, in this case) is used when resolving the resource. I.e., we are NOT relying on the JVM's trust-store to establish trust with the server (or so is our desire). > The client will fail to download all of the WSDL during the call to Service.create. The stacktrace is: > javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service. > at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:149) > at org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:65) > at javax.xml.ws.Service.<init>(Service.java:36) > at javax.xml.ws.Service.create(Service.java:116) > at demo.hw_https.client.Client.call(Client.java:84) > at demo.hw_https.client.Client.main(Client.java:76) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:592) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) > at java.lang.Thread.run(Thread.java:613) > Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service. > at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:93) > at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:204) > at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:147) > ... 11 more > Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:import): faultCode=PARSER_ERROR: Problem parsing 'https://localhost:9001/demo/secure?wsdl=Greeter.wsdl'.: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) > at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:210) > at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:175) > at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:91) > ... 13 more > Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1584) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) > at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848) > at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) > at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) > at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:877) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1089) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1116) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1100) > at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:402) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:960) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234) > at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) > at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) > ... 24 more > Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:221) > at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:145) > at sun.security.validator.Validator.validate(Validator.java:203) > at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172) > at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java:320) > at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:841) > ... 42 more > Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:236) > at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194) > at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216) > ... 47 more > Discussion: > I believe what is happening here is that the com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL operation is not respecting the resource resolver that's been configured in CXF, when loading imported WSDLs, but that's just a guess. The reason I suspect this is that I have inserted printlns/breakpoints in the custom resource resolver, and we appear never to be calling resolve for the imported WSDL. > Test Case: > I'm submitting a test-case based on the wsdl-first https sample. > To reproduce, use maven as per the usual instructions: > mvn -Pserver > mvn -Pclient > Note that the client has been modified extensively in this sample. It will first make a plain http call to the service, to ensure that the server is at least running and nominally configured correctly. It will then attempt to connect over https, bootstrapping with the WSDL at the HTTPS service URL. It also has some code for adding a custom resource resolver, which is needed to set the TLS parameters on the client connection to the "https://...?wsdl" URL. (CXF is calling toString() the URL that's passed in to the Service.create operation, so that URL cannot carry the URLStreamHandler used to connect to the HTTPs URL. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From zcarey@example.org Tue Aug 04 20:00:43 2009 Return-Path: <zcarey@example.org> Delivered-To: zcarey@example.org Received: (qmail 34122 invoked from network); 4 Aug 2009 20:00:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 4 Aug 2009 20:00:43 -0000 Received: (qmail 98226 invoked by uid 500); 4 Aug 2009 20:00:48 -0000 Delivered-To: zcarey@example.org Received: (qmail 98198 invoked by uid 500); 4 Aug 2009 20:00:48 -0000 Mailing-List: contact zcarey@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:zcarey@example.org> List-Unsubscribe: <mailto:zcarey@example.org> List-Post: <mailto:zcarey@example.org> List-Id: <issues.cxf.apache.org> Reply-To: zcarey@example.org Delivered-To: mailing list zcarey@example.org Received: (qmail 98188 invoked by uid 99); 4 Aug 2009 20:00:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 20:00:48 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from
{'source': 'Apache Software Foundation Public Mail Archives'}