Suzanne Byington

Greenhorn
+ Follow
since Jun 24, 2005
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Suzanne Byington

I failed to mention that adding the bean mapping to the deploy.wsdd file as I described above will fix the issue originally reported in this topic.
14 years ago
I agree that whenever possible, use the axis standard supported object types for objects returned from public methods in the web service. For those who are interested. I have experience returning custom objects to a C++ client.

Netbeans automatically added the definitions for the custom types into the wsdl file; however, I had to manually add the line to export/register the custom type as available by adding the following to my myWS.deploy.wsdd file:
<beanMapping qname="myNS:InformationCorrection" xmlns:myNS="urn:myWS" languageSpecificType="java:myservice.model.InformationCorrection"/>

InformationCorrection is my custom object and is located in myservice/model/InformationCorrection.java in my web service project.

Here is the entire contents of my myWS.deploy.wsdd file:
<deployment xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
<service name="myWS" provider="java:RPC">
<parameter name="className" value="myservice.myWS"/>
<parameter name="allowedMethods" value="*"/>
<beanMapping qname="myNS:InformationCorrection" xmlns:myNS="urn:myWS" languageSpecificType="java:myservice.model.InformationCorrection"/>
</service>
</deployment>
14 years ago