|
If you’ve got Ant then its very
easy: <?xml version="1.0" ?> <project name="axis"
default="axis" basedir="."> <target
name="axis-cvs">
<cvs
cvsRoot=":pserver:[EMAIL PROTECTED]:/home/cvspublic"
package="ws-axis"
dest="."
/> </target> <target
name="axis" depends="axis-cvs">
<ant antfile="build.xml"
target="compile"
inheritAll="true"
dir="ws-axis/java/" /> </target> </project> This will download axis to ./ws-axis and
then build it. The resultant axis.jar should be found in ./ws-axis/java/build/lib/axis.jar Haven’t tried this version – I
ripped up an ant build I’ve already got, but it should work. Regards, Richard From: Heitzeg,
Bill [mailto:[EMAIL PROTECTED] Just to follow up on this. I tried this with 1.1 and it worked
fine. For the following type:
<complexType name="SetOfPrimitives">
<sequence> <element
name="doubleValue" nillable="true"
type="xsd:double"/>
<element
name="integerValue" nillable="true"
type="xsd:int"/>
</sequence>
</complexType> 1.2 Alpha generated an int and a double, where 1.1
generated a java.lang.double and a java.lang.integer. I suppose that I should log this as a
bug, but first I would have to try it with the nightly build. Unfortunately, I have never downloaded
or built Axis source. How hard is
this to do? Bill
Heitzeg -----Original Message----- Sekhar, I’m
using 1.2 alpha, so maybe I need to try this with 1.1 as well. I think what I’ll do is to create
a test case using multiple primitives, try it out with 1.1, 1.2 alpha, and the
nightly builds. If it is indeed a
bug, I’ll then add it to BugZilla along with my test case. Thanks for your help on this. Bill -----Original Message----- Bill, I am using axis 1.1 and it does work
for me but for a slightly different case. The case I have is <element name="totalCost"
nillable="true" type="xsd:double"/> and it maps to a
Double. I do not have a specific case for Integer but was assuming it would
work if it came up. I also had a case where I was creating a custom type
(since axis did not crate it when using jav2wsdl ) and by mistake I set
nillable to true when it should be mapped it primitive int. But it
did not seem to make a difference and was was working fine with nillable true
or false. Hope this helps Sekhar -----Original
Message----- Sekhar, Based
on the documentation, it looks like there is a bug in wsdl2java. Have you been able to map a nillable
xsd:int to a Java Integer? Has
anyone else? Bill Bill
Heitzeg 1-734-995-9131 -----Original Message----- Here is
the documentation on this from user guide If the
WSDL says that an object can be nillable, that is the caller may choose to
return a value of nil, then the primitive data types are replaced by their
wrapper classes, such as Byte, Double, Boolean, etc. ----------------------------------------------- This
means that the your wsdl is saying that it is actually mapped to Integer. Sekhar -----Original
Message----- Thanks
Matt, Unfortunately,
the WSDL does specify that the element is nillable, but it is still being
mapped to an int. In the wsdl the element looks like: <element
name="sailMinLenDays" nillable="true"
type="xsd:int" /> Bill Bill
Heitzeg -----Original
Message----- I
believe that if the WSDL specifies that the field is nillable, then Matt Hi, Thanks, Bill Bill
Heitzeg
|
Title: RE: wsdl2java mapping primitives to objects
- wsdl2java mapping primitives to objects Heitzeg, Bill
- Re: wsdl2java mapping primitives to objects Matthew Sgarlata
- RE: wsdl2java mapping primitives to objects Heitzeg, Bill
- RE: wsdl2java mapping primitives to objects Mallipeddi, Sekhar
- RE: wsdl2java mapping primitives to objects Heitzeg, Bill
- Re: wsdl2java mapping primitives to objects Matthew Sgarlata
- RE: wsdl2java mapping primitives to objects Mallipeddi, Sekhar
- RE: wsdl2java mapping primitives to objects Heitzeg, Bill
- RE: wsdl2java mapping primitives to objects Heitzeg, Bill
- Richard Martin
