Proxy client won't work in this case?

Question

I have not made my client side work for a single device yet but I want to make sure I'm spending time on the right track:
My code will be running on the application server side, there will be hundreds of devices each has its own IP address, but runs exactly the same web services, and my code will need to talk to each of the selected ones using its IP address. I see that some generated proxy class contain the particular IP of the device where the web service is running on? If so, then it won't be possible for me to use a client proxy class to talk to all the devices.
I'm currently trying something like this:
URL url = new URL("http://172.21.159.52:80/cmi?wsdl");
QName serviceName = new QName("urn:Genus", "genusService");
Service service = Service.create(url, serviceName);
//These are for testing purpose
System.out.println ("List of QNames of service endpoints:");
Iterator it = service.getPorts();
*while (it.hasNext ()) {*
System.out.println (" " + it.next());
I can see the single service named 'genusPortType' in the output, however when the following code is reached:
QName portName = new QName("urn:Genus", "genusPortType");
Dispatch<SOAPMessage> dispatch = service.createDispatch(portName, SOAPMessage.class,Service.Mode.MESSAGE);
I got an error 'javax.xml.ws.WebServiceException: Illegal argument combination [type=javax.xml.soap.SOAPMessage,mode=MESSAGE]'. I'm confused because I see the same usage in lots of sample codes. Is it because the 'portName' part decides that these two parameters are not fit based upon the definition of 'genusPortType'? If the operation is defined like this in the wsdl file, wht values should I use?
*<wsdl:binding name="genusBinding" type="cmi:genusPortType">*
*     <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />*
*     <!-- login operation -->*
*     <wsdl:operation name="login" >*
*          <wsdlsoap:operation soapAction="com.controlmod.terminal.services.web.services.Login#Login" />*
*          <wsdl:input name="loginRequest" >*
*          <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />*
*          </wsdl:input>*
*          <wsdl:output name="loginResponse" >*
*          <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" />*
*          </wsdl:output>*
*     </wsdl:operation>*
*.............*

Answer 1

Sorry for really slow response on this - are you still here/still
having the issue?
Fillattr runs two migrations - one for access rules, and another for
proxy settings. I've seen cases where one works and the other fails.
But eventually you can get it going if you find the hangup.
Craig Johnson
Novell Knowledge Partner
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***