did you try "ref" instead of "type"? On 12/21/05, Clarence Dahlin <[EMAIL PROTECTED]> wrote: > WSDL style is document/literal wrapped by the way. > > > On 12/21/05, Clarence Dahlin <[EMAIL PROTECTED] > wrote: > > I've come across a somewhat puzzling problem. Could this be a bug or what > am I doing wrong? > > I'm using Axis 1.3 final and generated the client stubs with the WSDL2Java > tool. > > > > I'm using a modular WSDL, like this: > > > > myWSDL.wsdl imports abstractwsdl.wsdl > > abstractwsdl.wsdl imports calls.xsd > > calls.xsd imports types.xsd > > > > I have a simple type in types.xsd as base64Binary: > > <xsd:simpleType name="sessionID"> > > <xsd:restriction base="xsd:base64Binary"/> > > </xsd:simpleType> > > > > It is refered to in calls.xsd: > > <xsd:element name="createFederationExecution"> > > <xsd:complexType> > > <xsd:sequence> > > <xsd:element name="federationExecutionName" > type="types:federationExecutionName"/> > > <xsd:element name="fomDocumentDesignator" > type="types:fomDocumentDesignator"/> > > <xsd:element name="sessionID" type="types:sessionID"/> > > </xsd:sequence> > > </xsd:complexType> > > </xsd:element> > > > > If I do like that I end up sending this on the wire, using the stubs: > > > <sessionID>-17</sessionID><sessionID>78</sessionID><sessionID>93</sessionID><sessionID>-37</sessionID> > (and so on) > > > > If I refer to base64Binary instead: > > <xsd:element name="sessionID" type="xsd:base64Binary"/> > > it works and I send this: > > <sessionID xmlns="">705d28/1084c52a6e9//7ffe</sessionID> > > > > Any thoughts on this? > > > > regards, > > Clarence > > > >
-- Davanum Srinivas : http://wso2.com/blogs/
