Hi, Here is an explanation :) In Codegen what happens is that the WSDL file is read and converted into the equivalent Axis* object tree (AxisService,AxisOperation and so on). The subsequent parts of the codegen relies on this representation of the WSDL and what you get inside the resources directory is the serilization of this object tree! It is not just a copy of the original WSDL since we cannot leave certain things unchnaged when the code is generated, say relative references of XSD files.
So the error may be in the serialization part of the WSDL writing. We'll look into the issue and thanks for reporting it. Ajith On 5/11/06, Sebastian J. Schultheiss <[EMAIL PROTECTED]> wrote:
Hi Anne, thanks for your response. We re-run the WSDL2Java Tool after removing the namespace attribute from the <soap:body> tags. However, the WSDL that is "generated" by the WSDL2Java tool (the one you find in the specified -o directory/resources) is not formatted like that, I've attached it. Why does the WSDL2Java Tool not just use the WSDL file given to it by the -uri switch and instead creates its own? Can you please check and see if it is valid? If not, maybe that is the source of the problem: even if you give the WSDL2Java a valid WSDL file, it creates one itself that has errors. Thanks, -- Sebastian Anne Thomas Manes wrote: > > Sebastian, > > > There are errors in your WSDL. You must remove the namespace attributes > from the <soap:body> binding descriptions. (The namespace attribute must > be use only with RPC style.) > > > Anne
-- Ajith Ranabahu
