Hi Tony, First check this is not something wrong with your client program by using the DynamicInvoker sample, for example:
>java clients.DynamicInvoker http://www.xmethods.net/sd/2001/BabelFishService.wsdl BabelFish de_en "halt die ohren steif" Reading WSDL document from 'http://www.xmethods.net/sd/2001/BabelFishService.wsdl' Preparing WSIF dynamic invocation Executing operation BabelFish Result: return=stop the ears rigidly Done! > I've tried the code snippet you included and it works ok so this is probably something with your environment and I expect the DynamicInvoker will get the same problem. The WSIF0003W message is issued from the WSIFPluggableProviders class, see the source at: http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsif/java/src/org/apache/wsif/util/WSIFPluggableProviders.java Unfortunately its issued from two methods, findPlugableProviders, and readMETAINFClassNames, in a total of 6 different places. With the display insert being null in your case there's no easy way to tell which line has the problem, which is a bit of a design flaw. I think you'll have to use WSIF trace to identify the problem. All the exceptions are traced so the full stack trace should go to the WSIF trace file. There's a brief bit of doc on WSIF trace at: http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsif/java/doc/trace.htm What you need to do to activate trace is: - make sure your classpath includes the log4j jar and your current directory - in your current directory create a file named log4j.properties containing the following lines: log4j.rootCategory=INFO, LOGFILE log4j.logger.org.apache.wsif.*=DEBUG log4j.logger.com.ibm.wsif.*=DEBUG log4j.appender.LOGFILE=org.apache.log4j.FileAppender log4j.appender.LOGFILE.File=wsif.log log4j.appender.LOGFILE.Append=true log4j.appender.LOGFILE.Threshold=DEBUG log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout log4j.appender.LOGFILE.layout.ConversionPattern=%d [%c{1}] %-5p %m%n That's it. Now after you run WSIF, in your current directory there should be a file named wsif.log with a trace of what happened. If you can't get this to work, or it still doesn't show you what is going wrong, email me directly and I'll send you a new WSIFPluggableProviders class with extra debug output. Either way when you find out what the problem is could you let me know so I can look at changing WSIFPluggableProviders to give a more helpful error message? ...ant Anthony Elder [EMAIL PROTECTED] Web Services Development IBM UK Laboratories, Hursley Park (+44) 01962 818320, x248320, MP208. "Chen, Tony" <[EMAIL PROTECTED]> on 10/01/2003 22:33:31 Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: RE: [wsif] Help: error in getting the soap provider The port type I used is actually "BabelFishPortType". What I had in the previous message was a typo. Tony -----Original Message----- From: Chen, Tony Sent: Friday, January 10, 2003 3:31 PM To: [EMAIL PROTECTED] Subject: [wsif] Help: error in getting the soap provider Hi, I am trying to invoke the Babel Fish translation service at: http://www.xmethods.net/sd/2001/BabelFishService.wsdl This is an RPC style, Soap/HTTP binding service. My code looks something like this: WSIFServiceFactory factory = WSIFServiceFactory.newInstance(); WSIFService dpf = factory.getService( "http://www.xmethods.net/sd/2001/BabelFishService.wsdl ", "http://www.xmethods.net/sd/BabelFishService.wsdl";, "BabelFishService", "http://www.xmethods.net/sd/BabelFishService.wsdl";, "BabelFishService"); WSIFPort port = dpf.getPort(); The getPort call failed with this error message: 68422 [Thread-44] WARN wsif - WSIF0003W: An error occurred finding pluggable providers: <null> The wsif.jar comes with the Apache Soap provider, right? Why am I getting this error? Do I need to do anything for the META-INF\services\org.apache.wsif.spi.WSIFProvider file contained in the wsif.jar? It seems like the system can't find it. I appreciate your help. Tony
