dims fixed my problem (thanks, dims!). My comments are still mostly legitimate (I'll fix them momentarily), that the user still has to fill in a lot of the info himself, but the TCK DOES do that, so we should let him. Now 23 out of the 29 Call tests pass!

(and there was much rejoicing...)

Russell Butek
[EMAIL PROTECTED]

Please respond to [EMAIL PROTECTED]

To: [EMAIL PROTECTED]
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
[EMAIL PROTECTED]

Reply via email to