Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 34483 invoked by uid 500); 13 Jun 2002 16:41:57 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 34474 invoked from network); 13 Jun 2002 16:41:57 -0000 Importance: Normal Sensitivity: Subject: Re: JAX-RPC TCK - problem with ServiceFactory.createService To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: butek@us.ibm.com Date: Thu, 13 Jun 2002 10:56:33 -0500 X-MIMETrack: Serialize by Router on D04NM203/04/M/IBM(Build M13TT_05222002 Pre-release 2|May 22, 2002) at 06/13/2002 12:41:57 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=09BBE144DFC4B6438f9e8a93df938690918c09BBE144DFC4B643" Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --0__=09BBE144DFC4B6438f9e8a93df938690918c09BBE144DFC4B643 Content-type: text/plain; charset=US-ASCII 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 butek@us.ibm.com Russell Butek/Austin/IBM@IBMUS on 06/13/2002 09:41:12 AM Please respond to axis-dev@xml.apache.org To: axis-dev@xml.apache.org cc: 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 service */ 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 butek@us.ibm.com --0__=09BBE144DFC4B6438f9e8a93df938690918c09BBE144DFC4B643 Content-type: text/html; charset=US-ASCII Content-Disposition: inline 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
butek@us.ibm.com

Please respond to axis-dev@xml.apache.org

To: axis-dev@xml.apache.org
cc:
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 service
*/
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
butek@us.ibm.com
--0__=09BBE144DFC4B6438f9e8a93df938690918c09BBE144DFC4B643--