Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 68101 invoked from network); 14 Nov 2004 18:06:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 Nov 2004 18:06:31 -0000 Received: (qmail 83860 invoked by uid 500); 14 Nov 2004 18:06:09 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 83849 invoked by uid 500); 14 Nov 2004 18:06:08 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 83839 invoked by uid 99); 14 Nov 2004 18:06:08 -0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=DNS_FROM_RFC_POST,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jattier@hotmail.com designates 64.4.56.78 as permitted sender) Received: from [64.4.56.78] (HELO hotmail.com) (64.4.56.78) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 14 Nov 2004 10:06:04 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Nov 2004 10:06:00 -0800 Received: from 134.242.21.23 by BAY101-DAV6.phx.gbl with DAV; Sun, 14 Nov 2004 18:05:42 +0000 X-Originating-IP: [134.242.21.23] X-Originating-Email: [jattier@hotmail.com] X-Sender: jattier@hotmail.com From: "Kevin J. Duling" To: References: Subject: Re: typeMapping and Bad Types Date: Sun, 14 Nov 2004 10:05:36 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Message-ID: X-OriginalArrivalTime: 14 Nov 2004 18:06:00.0577 (UTC) FILETIME=[99097F10:01C4CA74] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I'm saying I can process single complex types in the response without my client-config.wsdd being configured. I believe this is because of the code in the Stub class. My next step is to try (again) to put something in the client-config.wsdd that will understand this response. However, when I get back two objects, serialization fails. Here are two snippets of my log4j logs. The first is when just a TResult object is returned and successfully deserialized. The second is when both a TResult and a TCustomerFinancials object returns. Finally, the SOAP XML that fails is included at the bottom. This current run is without anything of interest in my client-config.wsdd. Just a TResult: 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializerImpl - Set value com.ncube.vod.bps.billing.obi.TResult@9dd in target org.apache.axis.encoding.MethodTarget@12ef4c6 100695 [ ft2-7 ] DEBUG org.apache.axis.utils.NSStack - NSPush (32) 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::startElement() 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Enter: DeserializationContext::endElement(, return) 100695 [ ft2-7 ] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(popHandler00) 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Popping handler org.apache.axis.encoding.ser.BeanDeserializer@177060f 100695 [ ft2-7 ] DEBUG org.apache.axis.utils.NSStack - NSPop (32) 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Popped element stack to org.apache.axis.message.RPCElement:PurchaseRecurringCreateResponse 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::endElement() 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Enter: DeserializationContext::endElement(urn:uOBI_Intf-IOBISMSClient, PurchaseRecurringCreateResponse) 100695 [ ft2-7 ] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(popHandler00) 100695 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Popping handler org.apache.axis.message.RPCHandler@17b79a6 100705 [ ft2-7 ] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(setProp00) 100705 [ ft2-7 ] DEBUG org.apache.axis.message.RPCHandler - Setting MessageContext property in RPCHandler.endElement(). 100705 [ ft2-7 ] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(empty00) 100705 [ ft2-7 ] DEBUG org.apache.axis.utils.NSStack - NSPop (empty) 100705 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Popped element stack to org.apache.axis.message.SOAPBody:Body 100705 [ ft2-7 ] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::endElement() 100705 [ ft2-7 ] DEBUG org.apache.axis.client.Call - Exit: Call::invoke(RPCElement) 100705 [ ft2-7 ] DEBUG org.apache.axis.client.Call - Exit: Call::invoke(ns, meth, args) 100705 [ ft2-7 ] DEBUG org.apache.axis.TIME - axis.Call.invoke: 6219 {urn:uOBI_Intf-IOBISMSClient}PurchaseRecurringCreate TResult and TCustomerFinancials: 6349 [main] DEBUG org.apache.axis.encoding.DeserializerImpl - Set value com.ncube.vod.bps.billing.obi.TResult@9dd in target org.apache.axis.encoding.MethodTarget@873723 6349 [main] DEBUG org.apache.axis.utils.NSStack - NSPush (32) 6349 [main] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::startElement() 6349 [main] DEBUG org.apache.axis.encoding.DeserializationContext - Enter: DeserializationContext::endElement(, return) 6349 [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(popHandler00) 6349 [main] DEBUG org.apache.axis.encoding.DeserializationContext - Popping handler org.apache.axis.encoding.ser.BeanDeserializer@17c96a9 6349 [main] DEBUG org.apache.axis.utils.NSStack - NSPop (32) 6349 [main] DEBUG org.apache.axis.encoding.DeserializationContext - Popped element stack to org.apache.axis.message.RPCElement:CustomerFinancialGetResponse 6349 [main] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::endElement() 6349 [main] DEBUG org.apache.axis.encoding.DeserializationContext - Enter: DeserializationContext::startElement(urn:uOBI_Intf, TCustomerFinancial) 6349 [main] DEBUG org.apache.axis.message.RPCHandler - Enter: RPCHandler.onStartChild() 6349 [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(typeFromAttr00) 6349 [main] DEBUG org.apache.axis.message.RPCHandler - Type from attributes is: {urn:uOBI_Intf}TCustomerFinancial 6349 [main] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(exception00) 6349 [main] ERROR org.apache.axis.client.Call - Exception: org.xml.sax.SAXException: Bad types (class com.ncube.vod.bps.billing.obi.TCustomerFinancial -> class com.ncube.vod.bps.billing.obi.TResult) at org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:282) at org.apache.axis.encoding.DeserializationContext.startElement(Deserialization Context.java:1025) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:159) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java: 1138) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:308) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:342) at org.apache.axis.client.Call.invoke(Call.java:2420) at org.apache.axis.client.Call.invoke(Call.java:2319) at org.apache.axis.client.Call.invoke(Call.java:1776) at com.ncube.vod.bps.billing.obi.IOBISMSClientbindingStub.customerFinancialGet( IOBISMSClientbindingStub.java:524) at Deserialize.main(Deserialize.java:51) SOAP XML: HTTP/1.1 200 OK Connection: keep-alive Content-Type: text/xml Content-Length: 1543 Server: Indy/9.0.11 0 OK 199.99 0 0 0 0 0 0 0 0 0 ----- Original Message ----- From: "John Menke" To: Sent: Saturday, November 13, 2004 6:38 PM Subject: RE: typeMapping and Bad Types > I have not been able to debug the parsing process. Do you have log4j > configured so you can see what's going on during the parsing of the wsdd > file? If so can you tell me how you configured this? Also, the names you > use in the beanMapping look like the names i'm getting in my .wsdl file when > i deploy my service through a wsdd file that doesn't have beanMappings. Is > this because you deployed first and then customized the names to match the > wsdl or is there a way to figure out how to name the items so that they > match the wsdl... i'm thoroughly confused...you say your not using the > beanMappings and it's generating anyway... is beanMapping obsolete? >