Hello Philippe,
I was following another thread on this topic too. It seems that the
discussion on that thread, as well as what you said, indicate that
one has to __manually__ edit the wsdl file generated by Java2WSDL.
Could you confirm the following:
1. Run Java2WSDL to generate WSDL file.
2. Edit the WDSL file to add the fault information like the following:
In portType statement:
<wsdl:operation name="testException">
<wsdl:input message="tns:testExceptionRequest"/>
<wsdl:output message="tns:testExceptionResult"/>
<wsdl:fault name="myFault" message="tns:Exception"/>
</wsdl:operation>
In portBinding statement:
<wsdl:binding>
<fault name="soapapiFault">
<soap:fault name='myFault' use='literal' />
</fault>
</wsdl:binding>
3. Run WSDL2Java to generate the stubs.
4. Compile my implementation class along with the generated files.
So I would have to do this hand edit of the WSDL each time I
modified my interface?
I think someone in the other thread mentioned that this was caused
by a bug in AXIS? Is this true?
Is there no work-around for this (other than the hand editing)?
Many thanks.
V
--- philippe ventrillon <[EMAIL PROTECTED]> wrote:
> Hi
>
> I think if you are going from wsdl file you are supposed to
> Declare a message for the fault
> put somehting like that in your porttype
> <operation name='getCurrentLanguageCursorPage'>
> <input message='tns:getCurrentLanguageCursorPageIn'/>
> <output message='tns:getCurrentLanguageCursorPageOut'/>
> <fault name='soapapiFault' message='tns:soapapiFault'/>
> </operation>
>
> Put something like that in the portBinding
> <fault name="soapapiFault">
> <soap:fault name='soapapiFault' use='literal' />
> </fault>
>
> I imagine that when you invoke wsdl2Java it regenerates the service
> (with no
> throws clause) but not the impl class
>
>
> ---
> Philippe
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
