We have it working fine. With that new webservice.htc and some important guidelines 
(I'll post them below just for the benefit of the group), we're able to use it with a 
complex object and Axis autogenerating the WSDL (we were maintaining by hand 
previously). It's very convenient now. The only thing required to get things working 
is entries in the server-config.wsdd for the actual services and the doAutoTyping (if 
it works--still testing it) has made it extremely easy to deploy.

Joel Shellman


1) All classes used in your service API (excluding the service classes themselves) 
must conform to standard JavaBean? guidelines. This includes having a default 
constructor. Also, the superclass must also have a default constructor. If it doesn't, 
it will generate a WSDL type that extends anyType and webservice.htc will choke on 
that. There may be a way around this, but it's not that hard to ensure a default 
constructor for supertype so I didn't bother looking any further into it. 

2) You must use typed collections in the service interface--that means arrays or your 
own objects. You cannot use the Java Collections because they are not typed. This is 
because with non-typed collections, Axis has no way of knowing which type to map the 
entries to.

3) Do not use fields (class names might fail, too, didn't test) with the names 
"length" or "function". This is because in javascript those are special words and so 
webservice.htc crashed when I used them as field names. We could probably modify 
webservice.htc to deal with this, but it was easier to just change my names in the 
test. 


> -----Original Message-----
> From: David Teare 
> Sent: Tuesday, February 04, 2003 7:08 AM
> To: [EMAIL PROTECTED]
> Subject: webservice.htc and complex objects
> 
> 
> Hi all,
> 
> Has anyone had any success retrieving a complex object
> (i.e. a bean) from an Axis service using MS's
> webservice.htc?
> 
> I have downloaded the new webservice.htc as posted on
> this form and have successfully invoked simple Axis
> services from a browser.  However, once I call a
> service that returns a bean (instead of a simple
> string), the result.value field is empty.  What's
> worst, the result.error == false!
> 
> Any insights would be greatly appreciated.  Thanks!
> 
> --Dave.
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now. 
http://mailplus.yahoo.com


Reply via email to