Yes, Axis tries to process all the Messages. You probably should report a bugzilla bug on this with a WSDL that shows the problem. I am not sure what the right fix for this, as the processor works in a way that skipping unreferenced messages might be a bit tricky.
-- Tom Jordahl Macromedia Server Development -----Original Message----- From: [EMAIL PROTECTED] [mailto:k15a-list-axis@;mail.theotherbell.com] Sent: Wednesday, October 23, 2002 6:22 PM To: [EMAIL PROTECTED] Subject: RE: WSDLParser Rumor has it that Tom Jordahl said: > > Axis WSDL2Java ignores everything but SOAP bindings. > Perhaps it's an order problem? One of the WSDL's that's causing a problem is http://www.framewerks.com/webservices/fwarticleservice/fwarticles.asmx?wsdl (just had to be a .NET thing, didn't it :) If you look at the WSDL, you'll find three sets of messages, one set for each of the SOAP, HTTP/Get and HTTP/Post bindings. The message part "Body" for the HTTP/Get binding does not have a type. Based on what I've seen so far, this is common practice. When I try to parse this WSDL with Axis, I get the following error: Message part Body of operation or fault GetArticles has no element or type attribute. at org.apache.axis.wsdl.symbolTable.SymbolTable.getParametersFromParts(SymbolTable.java:1322) at org.apache.axis.wsdl.symbolTable.SymbolTable.getOperationParameters(SymbolTable.java:1053) at org.apache.axis.wsdl.symbolTable.SymbolTable.populateParameters(SymbolTable.java:987) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:385) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:371) at org.apache.axis.wsdl.gen.Parser.run(Parser.java:269) >From what you're telling me, Axis may be ignoring the bindings; but it appears it is trying to consume all of the messages, regardless of whether they are referenced by a SOAP binding. This is the scenario I'd like to avoid if possible since I really don't care about the parts used solely by the HTTP bindings. Any ideas? -- Cheers, Brenda
