After stepping through the Axis source, I found the solution to my problem.
And I think I found a bug. Or 3 bugs. I'm not sure which.
OperationDesc.getOutputParamByQName(QName) calls ParameterDesc.getQName().
But ParameterDesc.getQName() returns the variable "name". For my object,
"name" was "Cu
- Original Message -
From: "John Menke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
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 h
y your not using the
beanMappings and it's generating anyway... is beanMapping obsolete?
-Original Message-
From: Kevin Duling [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 13, 2004 2:20 PM
To: [EMAIL PROTECTED]
Subject: RE: typeMapping and Bad Types
I've tried both without any eff
vod.bps.billing.obi.TMetadata[]"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
From: "John Menke" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: typeMapping and Bad Types
Date: Sat, 13 Nov 2004 11:06:
Kevin,
are you using the beanMapping or typeMapping tags in your wsdd? I don't see
a reference to them in this email.
-jm
-Original Message-
From: Kevin J. Duling [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 13, 2004 1:24 AM
To: [EMAIL PROTECTED]
Subject: Re: typeMapping an
I'm a little closer; I've found another piece of the puzzle. I didn't
understand what "SAXException: Bad types (classA -> classB)" meant. While
working on the server-side of my app, I created this same problem by
returning the wrong object type. So I'm assuming this message is similar to
a Class
