You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Robert A. (Bob) Morris" <ra...@cs.umb.edu> on 2003/04/17 06:42:37 UTC

dynamic Service construction in client

Although I think it has been asked, I can't find an answer to this in
the archives; apologies if there is, and thanks for the pointer:

I installed the axis-10 addr example and applied the axis tools to
deploy the AddressBook service and clients constructed by the
framework (but see the minor(?) things at end). The Main.java client
provided works as expected.

Now I am trying to make the dynamic Service constructor 
   Service(java.lang.String wsdlLocation, QName serviceName) 
work in a jsp client.


The String wsdlLocation is verfied to be
    http://myHost:myIPPort/axis/services/AddressBook?wsdl
and that address in a browser returns the correct wsdl, as does the
Axis adminstrative service onece the service is deployed.

The QName serviceName, when output as a String is verified to be
{urn:AddressFetcher2}AddressBook 

urn:AddressFetcher2 is the Schema target namespace in the wsdl

Nevertheless, the Service constructor fails to find the service and
throws

javax.xml.rpc.ServiceException: Error processing WSDL document:
javax.xml.rpc.ServiceException: Cannot find service:
{urn:AddressFetcher2}AddressBook


I suppose I might have a related problem with the soap operation
GetAddressFromName if I ever get far enough to construct a Call...


Am I unclear on the concept?

TIA
Bob Morris

OS is Solaris SunOS5.8
server is Tomcat/4.1.10-LE-jdk14
jdk is 1.4.1_01


Here are the minor(?) things

0. In the distributed AddressBook.wsdl, before applying the tools I
   changed the soap address location to be the one on which I am
   deploying.

1. The distributed AddressBook.wsdl seems to refer to
   http://www.w3.org/1999/XMLSchema and this doesn't play nice
   with something on my classpath. I changed it to 2001/XMLSchema
   before applying the framework tools.

2. Although commandline deployment works
java org.apache.axis.client.AdminClient undeploy.wsdd
reliably throws
  - Processing file undeploy.wsdd
  - Exception:
  AxisFault
  faultCode: {http://xml.apache.org/axis/}Server.userException
  faultString: java.net.ConnectException: Connection refused
  faultActor: null
  ...