Are you using Axis 1.0 or 1.1?
Balaji D L
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
om> cc:
Subject: Re: [axis] Serializing
embedded complex types
06/26/2003 09:36
AM
Please respond to
axis-user
hi Rhett,
Try to run this attached example that I had
modified to return a object(Order_) containing
object(ship).Its working fine for me under java and
axis. Then tell us whether you are able to consume it
using stimulators like WSInvoker,WebserviceStudio
etc.,
the wsdd setting is
<service name="OrderProcessors" provider="java:RPC">
<parameter name="className"
value="samples.userguide.example5.BeanServices"/>
<parameter name="allowedMethods" value="*"/>
<beanMapping qname="myNS:Order_"
xmlns:myNS="urn:BeanServices"
languageSpecificType="java:samples.userguide.example5.Order_"/>
<beanMapping qname="myNS:Ship"
xmlns:myNS="urn:BeanServices"
languageSpecificType="java:samples.userguide.example5.Ship"/>
</service>
Regards
Balaji
--- [EMAIL PROTECTED] wrote: >
> (See attached file: deploy.wsdd)
>
> "Sameer
>
>
> Bombatkar" To:
> [EMAIL PROTECTED]
>
> <[EMAIL PROTECTED] cc:
>
>
> il.com>
> Subject: Re: [axis] Serializing embedded complex
> types
>
>
>
> 06/26/2003 02:57
>
>
> AM
>
>
> Please respond to
>
>
> axis-user
>
>
>
>
>
>
>
>
>
>
>
> Could you also post your deploy.wsdd and the class
> which all the
> operations
> for youre web-service??
>
>
>
> Sameer.
>
.....................................................
> "If a server crashes in a server farm and no one
> pings it, does it still
> cost four figures to fix?"
>
>
>
>
>
>
> >From: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >To: <[EMAIL PROTECTED]>
> >Subject: [axis] Serializing embedded complex types
> >Date: Wed, 25 Jun 2003 15:51:18 -0600
> >MIME-Version: 1.0
> >Received: from apache.org ([208.185.179.12]) by
> mc7-f15.law1.hotmail.com
> >with Microsoft SMTPSVC(5.0.2195.5600); Wed, 25 Jun
> 2003 14:51:42 -0700
> >Received: (qmail 78050 invoked by uid 500); 25 Jun
> 2003 21:51:16 -0000
> >Received: (qmail 77992 invoked by uid 500); 25 Jun
> 2003 21:51:16 -0000
> >X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
> >Mailing-List: contact [EMAIL PROTECTED];
> run by ezmlm
> >Precedence: bulk
> >list-help: <mailto:[EMAIL PROTECTED]>
> >list-unsubscribe:
> <mailto:[EMAIL PROTECTED]>
> >list-post: <mailto:[EMAIL PROTECTED]>
> >Delivered-To: mailing list [EMAIL PROTECTED]
> >Delivered-To: [EMAIL PROTECTED]
> >X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001
> >Message-ID:
> <[EMAIL PROTECTED]>
> >X-MIMETrack: Serialize by Router on
> BoulderNotes2/SYBASE(Release 5.0.12
> >|February 13, 2003) at 06/25/2003 03:51:18 PM
> >X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
> >Return-Path:
>
[EMAIL PROTECTED]
> >X-OriginalArrivalTime: 25 Jun 2003 21:51:43.0343
> (UTC)
> >FILETIME=[F74E97F0:01C33B63]
> >
> >Has anyone had luck with embedded complex types
> with Axis. Taking the
> >Address example one step further, I have WSDL
> describes an address to have
> >a phone that is a complex type, such as:
> >
> > <EmployeeVO>
> > <firstName>John</firstName>
> > <lastName>Doe</lastName>
> > <phone>
> > <area>999</area>
> > <location>9999</location>
> > <prefix>999</prefix>
> > </phone>
> > </EmployeeVO>
> >
> >The WSDL, SOAP request, SOAP response and Java code
> follow. Basically,
> >AXIS cannot serialize the response because it
> interprets "EmployeeVO" as
> >containing "area"...
> >
> >============= WSDL ==============
> ><?xml version="1.0" encoding="UTF-8"?>
> ><wsdl:definitions
> targetNamespace="urn:OtherTestEJB"
>
>xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
>
>xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> >xmlns:apachesoap="http://xml.apache.org/xml-soap";
> >xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> >xmlns:tns1="http://util.test.sybase.com";
> xmlns:intf="urn:OtherTestEJB"
> >xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:impl="urn:OtherTestEJB"
> >xmlns="http://schemas.xmlsoap.org/wsdl/";>
> > <wsdl:types>
> > <schema xmlns="http://www.w3.org/2001/XMLSchema";
> >targetNamespace="http://util.test.sybase.com";>
> > <import
>
namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
> > <complexType name="EmployeeVO">
> > <sequence>
> > <element name="firstName" nillable="true"
> type="xsd:string"/>
> > <element name="lastName" nillable="true"
> type="xsd:string"/>
> > <element name="phone" nillable="true"
> type="tns1:PhoneVO"/>
> > </sequence>
> > </complexType>
> > <complexType name="PhoneVO">
> > <sequence>
> > <element name="area" nillable="true"
> type="xsd:string"/>
> > <element name="location" nillable="true"
> type="xsd:string"/>
> > <element name="prefix" nillable="true"
> type="xsd:string"/>
> > </sequence>
> > </complexType>
> > <element name="EmployeeVO" nillable="true"
> type="tns1:EmployeeVO"/>
> > </schema>
> > </wsdl:types>
> >
> > <wsdl:message name="noParmsOrReturnResponse">
> >
> > </wsdl:message>
> >
> > <wsdl:message name="getEmployeeInfoRequest">
> >
> > <wsdl:part name="employeeVO"
> type="tns1:EmployeeVO"/>
> >
> > </wsdl:message>
> >
> > <wsdl:message name="OverloadedTestRequest1">
> >
> > <wsdl:part name="value" type="xsd:string"/>
> >
> > </wsdl:message>
> >
> > <wsdl:message name="OverloadedTestResponse">
> >
> > <wsdl:part name="OverloadedTestReturn"
> type="xsd:string"/>
> >
> > </wsdl:message>
> >
> > <wsdl:message name="getEmployeeInfoResponse">
> >
> > <wsdl:part name="getEmployeeInfoReturn"
> type="tns1:EmployeeVO"/>
> >
> > </wsdl:message>
> >
> > <wsdl:message name="twoParameterTestResponse">
> >
> > <wsdl:part name="twoParameterTestReturn"
> type="xsd:string"/>
> >
>
=== message truncated ===
> ATTACHMENT part 2 application/octet-stream
name=deploy.wsdd
http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.
(See attached file: source files with wsdl.zip)
source files with wsdl.zip
Description: Zip archive
