[resolved] tWebServiceInput WSDL2Java not generation ServiceLocator for EWS

[Anonymous]

Working with the Exchange 2010 EWS wsdl in tWebServiceInput, after adding the two referred-to xsd files to the services directory, was able to successfully (i.e. no reported errors) run WSDL2Java. It generated dozens of routines for the operations and as well the PortType and BindingStub routines. However it did not create the ServiceLocator routine.
1) Wondering if anyone has any guidance on why a ServiceLocator routine would not get generated by WSDL2Java in general for a wsdl and specifically for EWS... and if there is a way to get it to pop out?
2) Alternatively, while the tWebServiceInput tutorial utilizes ServiceLocator to help create the new instance. does anyone know if it would be possible to skip using it and just refer directly to an operator routine? And what the correct syntax would be?
Thanks for any advice you can give!

[Anonymous · Accepted solution]

Re-running WSDL2Java and now it is creating the ServiceLocator routine. Trick was to addend the wsdl file with:
<wsdl:service name="ExchangeServices">
<wsdl ort name="ExchangeServicePort" binding="tns:ExchangeServiceBinding">
<soap:address location="https://my.exchange.com/EWS/Exchange.asmx"/>
</wsdl ort>
</wsdl:service>
Credit to http://code.google.com/p/imap2exchange/wiki/ExchangeWebServices
Will see if it works tomorrow

[Anonymous]

Hi, jds
Thanks for your sharing, and we are all interested in your case. Waiting for your good news.
Best regards
Sabrina