• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Help with soapenc:string vs. xsd:string

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm using Axis 1.2 and am trying to change my Strings in my WSDL from "soapenc:string" to "xsd:string" and am having no luck. I'm deploying my complex types with beanMapping. Is there attribute to beanMapping where I can specify "xsd:string" rather than "soapenc:string"?
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I was able to get around this problem under Axis 1.2RC3 by adding the following type mapping under the <service> element of my wsdd config file.

<typeMapping
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
qname="ns1:string"
serializer="org.apache.axis.encoding.ser.SimpleSerializerFactory"
deserializer="org.apache.axis.encoding.ser.SimpleDeserializerFactory"
type="java:java.lang.String"
xmlns:ns1="http://www.w3.org/2001/XMLSchema"
/>

This may even work under the <globalConfiguration> element (and thus for all deployed services) but I haven't tried it yet.

Mark
 
reply
    Bookmark Topic Watch Topic
  • New Topic