Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 13304 invoked from network); 11 May 2004 17:19:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 May 2004 17:19:19 -0000 Received: (qmail 59413 invoked by uid 500); 11 May 2004 17:19:48 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 59358 invoked by uid 500); 11 May 2004 17:19:48 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 59271 invoked by uid 98); 11 May 2004 17:19:47 -0000 Received: from Jiri.Urbanec@logicacmg.com by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(193.109.254.211):. Processed in 0.057505 secs); 11 May 2004 17:19:47 -0000 X-Qmail-Scanner-Mail-From: Jiri.Urbanec@logicacmg.com via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(193.109.254.211):. Processed in 0.057505 secs) Received: from unknown (HELO mail36.messagelabs.com) (193.109.254.211) by hermes.apache.org with SMTP; 11 May 2004 17:19:47 -0000 X-VirusChecked: Checked X-Env-Sender: Jiri.Urbanec@logicacmg.com X-Msg-Ref: server-15.tower-36.messagelabs.com!1084295897!6152280 X-StarScan-Version: 5.2.11; banners=logicacmg.com,-,- X-Originating-IP: [158.234.9.163] Received: (qmail 10338 invoked from network); 11 May 2004 17:18:17 -0000 Received: from iris.logica.co.uk (158.234.9.163) by server-15.tower-36.messagelabs.com with SMTP; 11 May 2004 17:18:17 -0000 Received: from cimrman.cz.logica.com (cimrman.cz.logica.com [158.234.170.121]) by iris.logica.co.uk (8.12.3/8.12.3/Debian -4) with ESMTP id i4BHIHOb018494 for ; Tue, 11 May 2004 18:18:17 +0100 Received: by cimrman.cz.logica.com with Internet Mail Service (5.5.2657.72) id ; Tue, 11 May 2004 19:18:15 +0200 Message-ID: <911724B092FBD511B55400D0B7B90B670232D1FD@ressel.cz.logica.com> From: Jiri.Urbanec@logicacmg.com To: axis-dev@ws.apache.org Subject: Bad types (int -> class[B) Date: Tue, 11 May 2004 19:18:08 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-2" X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello, Axis (version see lower) works fine with WSDL2Java clients, .NET clients made from wsdl. But there is client - EAI framework - which can cause strange Axis faults. In my request there are transferred binary blocks (byte[] - base64Binary). As said before, java clients and .NET clients are OK, but the third client's request (implementation unknown) causes Axis to fault with Exception: soapenv:Server.userException org.xml.sax.SAXException: Bad types (int -> class[B) while receiving and parsing the request with binary blocks -- OR -- while generating reply with such binary block (in this case, bussiness logic is performed and finished well) - it looks like upon the request format the Axis goes to the mode that causes the exception during response generation. Can it be connected with WS-I conformance ? Problematic are only requests/responses with binary blocks. I did not watch the Axis development for a while, so it can be a fixed bug in later builds. Did someone met (and better fixed) this problem ? Thanks in advance. J.U. Axis version: Name: org/apache/axis Implementation-Title: Apache Axis Implementation-Version: 1.1 1021 June 13 2003 Implementation-Vendor: Apache Web Services Unix, JDK 1.3. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.