Return-Path: Delivered-To: apmail-incubator-beehive-dev-archive@www.apache.org Received: (qmail 81759 invoked from network); 7 Jun 2005 01:27:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jun 2005 01:27:40 -0000 Received: (qmail 10409 invoked by uid 500); 7 Jun 2005 01:27:39 -0000 Delivered-To: apmail-incubator-beehive-dev-archive@incubator.apache.org Received: (qmail 10364 invoked by uid 500); 7 Jun 2005 01:27:38 -0000 Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Beehive Developers" Delivered-To: mailing list beehive-dev@incubator.apache.org Received: (qmail 10309 invoked by uid 99); 7 Jun 2005 01:27:38 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 06 Jun 2005 18:27:33 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 2741918B for ; Tue, 7 Jun 2005 03:01:42 +0200 (CEST) Message-ID: <1211034866.1118106102159.JavaMail.jira@ajax.apache.org> Date: Tue, 7 Jun 2005 03:01:42 +0200 (CEST) From: "daryoush mehrtash (JIRA)" To: beehive-dev@incubator.apache.org Subject: [jira] Commented: (BEEHIVE-717) minor non-conformance of exceptions to JSR-181 / JAX-RPC 1.1 In-Reply-To: <1935887044.1115943452536.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/BEEHIVE-717?page=comments#action_12312819 ] daryoush mehrtash commented on BEEHIVE-717: ------------------------------------------- There are two problems with Faults. If the JWS is called from the URL, Axis would not serialize the fault properly and you get a bogus message. I have send a patch for axis to fix this problem. The other issue is when you send a soap request (e.g. via application) to the JWS, JWS was not sending the correct infomration in the detail. I fixed the JWS based on this exchange. http://marc.theaimsgroup.com/?t=111775697800004&r=1&w=2 The fixes are attached shortly. > minor non-conformance of exceptions to JSR-181 / JAX-RPC 1.1 > ------------------------------------------------------------ > > Key: BEEHIVE-717 > URL: http://issues.apache.org/jira/browse/BEEHIVE-717 > Project: Beehive > Type: Bug > Components: Web Services (181) > Versions: V1Beta > Environment: Beehive SVN 169852 > Reporter: Jeremiah Johnson > Assignee: daryoush mehrtash > Priority: Minor > Fix For: TBD > Attachments: BEEHIVE-133.tar.gz, BEEHIVE-133.wsdl, faultpatch.txt > > While testing BEEHIVE-133, we ran into an issue with user-defined Exceptions. The example provided in the JAX-RPC v1.1 spec shows the problem, so I will attach that as the repro. The WSDL looks accurate according to the JAX-RPC spec (which is referenced by JSR 181), but the response message looks incorrect. > I will attach the WSDL; the incorrect looking response is below: > > > > soapenv:Server.userException > web.InvalidTickerException > > localhost.localdomain > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira