AXIS Version Issue

[Amit G Piplani]

Hi,
I have recieved a WSDL for a deployed service.
When i used AXIS version 1.1, i get the files and operation name along with "_"(for ex, if entry is like this in xsd file , <xs:element ref="ResponseContext"/>, then _RequestContext.java file is created)
When i am hitting webService with this client jars, i get error saying " No such operation RequestContext".

And when i used Axis Version 1.2, i get the file name and operation name as given in WSDL.

Any help on this will be highly appreciated.

Thanks
Amit

[Balaji Loganathan]

Originally posted by Amit G Piplani:
i get error saying " No such operation RequestContext".

IMHO, i never had this problem. the simple solution could be to change remove the _ and recompile the java files it.
Also please post this as a bug in Axis website.

[Amit G Piplani]

Hi Balaji,

Changing the file name will also not help, as i have to change my Stub and calling application also for this(Which is huge).

Amit

[Rr Kumaran]

Give some more inputs like pasting your WSDL here. Any special reason for sticking to AXIS 1.1 ?

[Amit G Piplani]

Reasons for going towards Axis 1.1 is stable. Will i be able to paste 10,000 lines of WSDL here?

[Ashutosh Shahi]

This I think has been a known issue and has been fixed in Axis 1.2. You can check out: http://issues.apache.org/jira/browse/AXIS-1598
The 1.2 release should be final anytime now so you can move to 1.2 I guess.

Ashutosh

[Amit G Piplani]

But the mappings between _Java object and XMl was correct and i was able to resolve the issue using both Axis 1.1 and Axis 1.2, since issue was at the Deployed Service end.