Hi,
You should jus have to map the complex type to a corresponding bean class, then WSIF will automatically use the bean serializer with the Axis provider and do everything. The address book test case (see xml-axis-wsif/java/test/addressbook/AddressBookTest) is an example of invocation of a service that expects complex types in the input, but again there is nothing special you have to do - even the type mapping can in fact be automatically done if the java type you use follows the expected naming convention.
Thanks,
Nirmal.
| [EMAIL PROTECTED]
06/06/2003 12:21 PM
|
To: [EMAIL PROTECTED] cc: Subject: No Mapping found.. |
Hi all,
A better way to phrase this question would be:
How can we use WSIF to invoke a web service which expects a complex type
mapping
as an input parameter?
Somewhat akin to:
public ComplexStateOut Function( ComplexStateIn ) {.....}
There are samples which demonstrate return of a complex type
but none that take IN a complex type which is when I am having a "No
mapping found exception.....".
I would appreciate any response.
Thanks
Riz
Research & Innovative Solutions,
Indus International Inc.
Columbia, South Carolina
[EMAIL PROTECTED]
----- Forwarded by Rizwan Ahmed/SC/Indus/US on 06/06/2003 11:58 AM -----
Rizwan Ahmed
Sent by: Rizwan To: [EMAIL PROTECTED]
Ahmed cc:
Subject: No Mapping found..
06/05/2003 09:12
PM
Hello,
Does anyone have experience with processes that use more than one complex
type?
I wrote a simple web service that takes in a complex schema type and
returns a complex schema type.
The web service is deployed as a stateless session bean. The WSDL file is
attached.
When I try to dynamically invoke using WSIF, it gives me (the log is
attached for your reference)
" No mapping found for
'http://output.cdyne.components.banner.indus.com:LatLongReturn' using
encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
[java.lang.IllegalArgumentException]"
The bean classes LatLongReturn and ZipState are in their correct places and
the service seems to
be deployed correct.
(See attached file: ZipLookupManager.wsdl) (See attached file: wsif.log)
Anybody come across this problem before? What was your
resolution/workaround?
Thanks in advance!
Riz
****************************************
This email message and all attachments transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and
privileged information. Please DO NOT forward this email outside of the recipient's Company unless expressly authorized to do so herein. Any
unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email
and destroy all copies of the original message.
Any views expressed in this email message are those of the individual sender except where the sender specifically states them to be the views of Indus
International, Inc.
****************************************
#### ZipLookupManager.wsdl has been removed from this note on June 06, 2003 by Nirmal Mukhi
#### wsif.log has been removed from this note on June 06, 2003 by Nirmal Mukhi
