axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: JAX-RPC TCK - problem with ServiceFactory.createService
Date Thu, 13 Jun 2002 15:56:33 GMT
dims, here's the extra info you asked for.  Pretty basic.

The client code is calling:

          service = JAXRPC_Util.getService(SERVICE_QNAME);
          call = service.createCall(PORT_QNAME);

JAXRPC_Util.getService looks like:

      if(sfactory == null)
          sfactory = ServiceFactory.newInstance();
      Service service = sfactory.createService(sname);
      return service;

Russell Butek

Russell Butek/Austin/IBM@IBMUS on 06/13/2002 09:41:12 AM

Please respond to

Subject:    JAX-RPC TCK - problem with ServiceFactory.createService

The TCK depends on ServiceFactory.createService(QName serviceName).  I've
included our implementation below.  Notice 2 things:
- The javadoc comment says "Not yet implemented".  There IS an
implementation, but it's not much more than a placeholder.
- My comments inline ("RJB" is me) say I don't know how we're supposed to
implement this.

After calling createService, the TCK calls createCall.  That throws a
ServiceException:  "Missing WSDL document".  We were never handed a wsdl
document so we can't proceed.  Clearly the JAX-RPC RI handles this.  Any
notions how it does?  or how we should?

*  Create a Service instance.
*  Not yet implemented.
*  @param   serviceName QName for the service
*  @return  Service.
*  @throws  ServiceException If any error in creation of the specified
public javax.xml.rpc.Service createService(QName serviceName)
throws ServiceException {

// RJB - this isn't quite proper - I'm dropping the serviceName,
// but I don't rightly know what use the service name is without
// WSDL.  So I'll just create a default (empty) Service with the
// assumption that callers of this method are going to do all
// the work themselves.
return new Service();
} // createService

Russell Butek

View raw message