WSDL2Java--->java.io.IOException: ERROR: Fault is missing a name= attribute in operation

[Niket Anand <ni...@noida.manystreams.com>]

Hello all,
I have wsdl file and trying to convert java files using WSDL2java tool, but
it is causing some problem as
java.io.IOException: ERROR: Fault is missing a name= attribute in operation
"destroyNotification", i
n binding {http://www.csapi.org/fw_if_app/wsdl}IpEventNotificationBinding.
        at
org.apache.axis.wsdl.symbolTable.SymbolTable.faultsFromSOAPFault(SymbolTable
.java:1975)
        at
org.apache.axis.wsdl.symbolTable.SymbolTable.populateBindings(SymbolTable.ja
va:1790)
        at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:577)
        at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:421)
        at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:408)
        at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:393)
        at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:245)
        at java.lang.Thread.run(Unknown Source)

DOES IT REALLY NEED a name attrubute for fault element? But most of the
standard wsdl provided by OSA/Parley API doesnot have fault element
attribute.

Please suggest anyone.....I am waiting for that.
Thanks,
Niket

Re: WSDL2Java--->java.io.IOException: ERROR: Fault is missing a name= attribute in operation

[Anne Thomas Manes <an...@manes.net>]

name is a required attribute.

----- Original Message -----
From: "Niket Anand" <ni...@noida.manystreams.com>
To: <ax...@ws.apache.org>; <ax...@xml.apache.org>;
<ax...@ws.apache.org>
Sent: Wednesday, June 11, 2003 3:23 PM
Subject: WSDL2Java--->java.io.IOException: ERROR: Fault is missing a name=
attribute in operation


> Hello all,
> I have wsdl file and trying to convert java files using WSDL2java tool,
but
> it is causing some problem as
> java.io.IOException: ERROR: Fault is missing a name= attribute in
operation
> "destroyNotification", i
> n binding {http://www.csapi.org/fw_if_app/wsdl}IpEventNotificationBinding.
>         at
>
org.apache.axis.wsdl.symbolTable.SymbolTable.faultsFromSOAPFault(SymbolTable
> .java:1975)
>         at
>
org.apache.axis.wsdl.symbolTable.SymbolTable.populateBindings(SymbolTable.ja
> va:1790)
>         at
>
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:577)
>         at
> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:421)
>         at
>
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:408)
>         at
>
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:393)
>         at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:245)
>         at java.lang.Thread.run(Unknown Source)
>
> DOES IT REALLY NEED a name attrubute for fault element? But most of the
> standard wsdl provided by OSA/Parley API doesnot have fault element
> attribute.
>
> Please suggest anyone.....I am waiting for that.
> Thanks,
> Niket
>

Provider with no impl Class

[Chris Haddad <ha...@apache.org>]

Hey All -

i've been working on a custom provider that hands off to a Java class that
doesn't have the same method signature as the SOAP parts.   Got it all
working, but the trick was that Axis requires a concrete implementation
class containing correlating method signatures.

I've made a few modifications to the codebase in order to support the
deployment of a web service without an impl class.  The operations and parts are
defined solely in WSDD, and the provider will generate a WSDL service description
file.

The mods will be checked in after 1.1 ships, but in the meantime, i was
wondering if anyone else out there has had a similar requirement?

/Chris