facebook

No complex types in XFire WSDL

  1. MyEclipse Archived
  2.  > 
  3. Web Services
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #284598 Reply

    frankhammen
    Member

    I created a Web Service project using MyEclipse 6.0. The Web Services is working, only the return object (complex type) is not returned in the returning SOAP message. When I look at the WSDL file (generated at runtime?) I see that my return object in not specified:

    <xsd:complexType name=”outDocuments”/>

    Is it possible to ‘overrule’ the generated WSDL by a fixed WSDL file ? Is so, where do I put this fixed WSDL file ? Or do I need to create a <class>.aegis.xml file which describes from which simple types these complex types exist ?

    Thanks…

    #284610 Reply

    frankhammen
    Member

    I’ve red a little more. As I understand I can either use annotation (but since I’m using java 1.4 I cannot use this) or a aegis.xml file. I tried to create such a file, but saw no difference in my WSDL.

    Also pointing the services.xml to another WSDL file doesn’t work (I only get it to work when using something like “file://c:\temp\wsdl.wsdl” as value and I don’t want a absolute path).

    Does anyone has an example of a java source file with a corresponding aegis.xml file ???

    #284613 Reply

    Ton Huisman
    Member

    you did put public getters/setters in your class, I presume? (the attributes can (should) be private), and the runtime should be able to comprehend that.
    This is how Axis2 finally understood my complex types (or I finally understood the way Axis works…)

    HTH
    Ton

    #284614 Reply

    frankhammen
    Member

    @huisma13: thanks a million… I just started testing with this, when I received your email. Indeed adding getters/setter in the class solved the problem. Now I can see my complex types in my WSDL. Thanks again….. 🙂

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: No complex types in XFire WSDL

You must be logged in to post in the forum log in