I checked it with the wsdl generated by Axis 1.3. It's attached and it
seems to work. So the problem is not with the wsdl2java but with the
java2wsdl process.
On 5/5/06, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
> If I start with the wsdl from the working service, I get the same error.
> The
On 5/5/06, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
> If I start with the wsdl from the working service, I get the same error.
> The two classes (FTAction and FaultToleranceService interface) are
> written by me, although they were writter for the Axis1 service, they
> are not generated at a
If I start with the wsdl from the working service, I get the same error.
The two classes (FTAction and FaultToleranceService interface) are
written by me, although they were writter for the Axis1 service, they
are not generated at all and so, they should generate a good WSDL file
with Axis2.
On 5/5
Jose,The schema has two identical definitions of the FTAction type. Which is obviously an error. The WSDL also imports another schema with a namespace of "http://ft.tomas.org/xsd
", which also defines the FTAction type, and your elements reference this imported type rather than one from the "http:/
I have a working web service deployed in Axis 1.3 so I tested if I can
port it to Axis2.
I downloaded the Axis2 binary distribution and ecipse plugin. First I
created the FaultToleranceService interface and the FTAction class
that were the starting point of my old service. They are attached.
Using
