Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 90B8C200C1D for ; Thu, 16 Feb 2017 13:12:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8F63F160B61; Thu, 16 Feb 2017 12:12:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DBC4E160B57 for ; Thu, 16 Feb 2017 13:12:47 +0100 (CET) Received: (qmail 94628 invoked by uid 500); 16 Feb 2017 12:12:46 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 94617 invoked by uid 99); 16 Feb 2017 12:12:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Feb 2017 12:12:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 52A901A03AA for ; Thu, 16 Feb 2017 12:12:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JHttpxoKwvYt for ; Thu, 16 Feb 2017 12:12:45 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id E4E7A5F36C for ; Thu, 16 Feb 2017 12:12:44 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 19C35E02FD for ; Thu, 16 Feb 2017 12:12:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9F3912411D for ; Thu, 16 Feb 2017 12:12:41 +0000 (UTC) Date: Thu, 16 Feb 2017 12:12:41 +0000 (UTC) From: "Freeman Fang (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CXF-7240) JAX-WS Dispatch incorrectly asserts that Message mode with XML/HTTP binding is invalid when using instances of DataSource MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 16 Feb 2017 12:12:48 -0000 [ https://issues.apache.org/jira/browse/CXF-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-7240: --------------------------------- Assignee: Freeman Fang > JAX-WS Dispatch incorrectly asserts that Message mode with XML/HTTP binding is invalid when using instances of DataSource > ------------------------------------------------------------------------------------------------------------------------- > > Key: CXF-7240 > URL: https://issues.apache.org/jira/browse/CXF-7240 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime > Affects Versions: 3.1.7, 3.1.10 > Reporter: Liam H > Assignee: Freeman Fang > > If a instance of dispatch is created in the following way: > {code:java} > QName serviceName = new QName("http://org.apache.cxf", "stockQuoteReporter"); > Service s = Service.create(serviceName); > > QName portName = new QName("http://org.apache.cxf", "stockQuoteReporterPort"); > Dispatch dispatch = s.createDispatch(portName, > ByteDataSource.class, > Service.Mode.MESSAGE);}} > {code} > then invoking the created Dispatch instance like so: > {code:java} > dispatch.invoke(new ByteDataSource("".getBytes())); > {code} > results in an exception with the message "DataSource is not valid in MESSAGE mode with XML/HTTP binding." > This contradicts your own documentation(and I believe the JAX-WS spec) in that these are this the only binding and mode you can use in combination with a DataSource : > {quote} > Dispatch objects can use objects that implement the javax.activation.DataSource interface when the following conditions are true: > the Dispatch object is using the HTTP binding. > the Dispatch object is using message mode. > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)