Wed, 29 May 2002
Apache Axis looks promising, but not quite ready for prime time
I finally got a chance today to begin playing with Apache Axis today. I used the version that is included in the JBoss 3.0 RC3 distribution. I was able to create a simple test.jws web service and deploy it by dropping it in the axis directory. I was able to hit the web service with an HTTP GET from the browser and axis gave it's default message. However, the instructions for getting WSDL generated, specifically adding ?wsdl or ?WSDL to the end of the URL doesn't work. It returns a standard error, something like resource not found. I guess I could use java2wsdl but it'd be cool if I could get the on-the-fly generation to work as well as GLUE. I'm looking forward to working with this more as it matures. I'd like to convert the stuff that I have implemented here to it and do some more SOAP development using it but it does not appear to be far enough along to compete with GLUE. I also would like to see axis do for the client side of SOAP what they did for the server side with the jws auto-deployment. An automatic client boilerplate generation something along the lines of what GLUE does in it's console:
Java Interface
// generated by GLUE/wsdl2java on Wed May 29 23:58:39 EDT 2002
public interface IRcsProxy
{
String getRanking();
String getReferers( String site, String group );
String getReferersBySite( String site, String group, int width );
String getReferersByPage( String site, String group, String url, int width );
}
Helper Class
// generated by GLUE/wsdl2java on Wed May 29 23:58:39 EDT 2002
import electric.registry.Registry;
import electric.registry.RegistryException;
public class RcsProxyHelper
{
public static IRcsProxy bind() throws RegistryException
{
return bind( "http://www.watsondesign.com/soap/urn:rcsproxy.wsdl" );
}
public static IRcsProxy bind( String url ) throws RegistryException
{
return (IRcsProxy) Registry.bind( url, IRcsProxy.class );
}
}
Posted at: 22:22 | permalink
