No documentation, yet. Basically, you instantiate an org.apache.axis.wsdl.toJava.Emitter, call the set methods you want to call, and then call emitter.run (or emitter.emit, depending on the version - emitter.run is newer). DO NOT call WSDL2Java. That is only a command-line tool that itself calls Emitter methods.
Russell Butek [EMAIL PROTECTED] "Gold, Laurence (MLIM)" <[EMAIL PROTECTED]> on 05/13/2002 09:58:15 AM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: RE: WSDL2Java programmatic errors Russell: Is there any documentation on how you call the WSDL2Java programmatically. I am trying to build a dynamic client that supports complex types. I have not been able to get the WSDLExplorer to work as of yet. I will post the errors after this next attempt. Larry -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Monday, May 13, 2002 9:21 AM To: [EMAIL PROTECTED] Subject: RE: WSDL2Java programmatic errors Our build process calls WSDL2Java programmatically so, in general, this works. Could you show us: 1. How you called it? 2. Your WSDL? >From your stack dump I can see you're not using the latest version of code. Which version ARE you using? Might it be possible for you to try a recent CVS version? Some of the file-finding code has changed recently. (The WSDL2Java framework has also changed recently, which SHOULDN'T affect your code, but it may, depending on how you call WSDL2Java/Emitter.) Russell Butek [EMAIL PROTECTED] "Provencher, Samuel" <[EMAIL PROTECTED]> on 05/10/2002 04:36:07 PM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: RE: WSDL2Java programmatic errors Oh, I forgot to mention that the same call works when called from a batch file... -----Original Message----- From: Provencher, Samuel [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 5:28 PM To: '[EMAIL PROTECTED]' Subject: WSDL2Java programmatic errors I've managed to drive Java2WSDL programmatically, but am having trouble doing the same thing with WSDL2Java and it appears to do some naming things in the parser as it tries to find the file. The file is there, but it's getting confused I guess... maybe I have the wrong version of xerces for Axis? - Exception: org.xml.sax.SAXException: Fatal Error: URI=null Line=0: File "file:///D:/WebServiceGenerator/portalservice.wsdl" not found. at org.apache.axis.utils.XMLUtils$ParserErrorHandler.fatalError(XMLUtils.java:4 72) at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1225) at org.apache.xerces.readers.DefaultEntityHandler.startReadingFromDocument(Defa ultEntityHandler.java:512) at org.apache.xerces.framework.XMLParser.parseSomeSetup(XMLParser.java:312) at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1080) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:19 5) at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:243) at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:256) at org.apache.axis.wsdl.toJava.Emitter.emit(Emitter.java:151) at org.apache.axis.wsdl.WSDL2Java$WSDLRunnable.run(WSDL2Java.java:725) at java.lang.Thread.run(Thread.java:484) java.io.IOException: Unable to retrieve WSDL document: D:\WebServiceGenerator\indirect_portalservice.wsdl at org.apache.axis.wsdl.toJava.Emitter.emit(Emitter.java:153) at org.apache.axis.wsdl.WSDL2Java$WSDLRunnable.run(WSDL2Java.java:725) at java.lang.Thread.run(Thread.java:484) ******************************************************* ******************************************************* "Imagination is more important than knowledge." - Albert Einstein Samuel Provencher voice: 781.663.9209 Senior Project Engineer email: [EMAIL PROTECTED] Telegea, Inc. ******************************************************* *******************************************************
