The handler of the client doesn't work

Question

the client is a java application, and I have add the handler to de handlerchain of the client's registry, but it just doesn't work. What's the matter?
This is my code:
String url = "http://127.0.0.1:8080/HelloWorld/HelloWorld?wsdl";
String namespace = "urn:HelloWorld/wsdl";
String portName = "HelloWorldSEIPort";
String serviceName = "HelloWorld";
QName serviceQN = new QName(namespace, serviceName);
ServiceFactory serviceFactory = ServiceFactory.newInstance();
Service service = serviceFactory.createService(new URL(url), serviceQN);
QName servicePort = new QName(namespace, portName);
HandlerRegistry registry = service.getHandlerRegistry();
List handlerChain = new ArrayList();
HandlerInfo handlerInfo = new HandlerInfo(ClientHandler.class, null, null);
handlerChain.add(handlerInfo);
registry.setHandlerChain(servicePort, handlerChain);
Stub stub = createProxy();
stub._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, url);
hello.HelloWorldSEI hello = (hello.HelloWorldSEI)stub;
System.out.println(hello.sayHello(args[0]));
I use the static stub method and generate the web service client with wscompile of the jwsdp. My web service's name is HelloWorld, but it generates several class such as HelloWorld, HelloWorld_Impl, HelloWorldSEIPort, HelloWorldSEI. What's the differences between them. And I want to know what's the type QName is, it's one of the parameters of the registry.setHandlerChain method. Why I have to use QName? And what my service's portName should be. Anyone who can help me? Thanks!
I use the NetBeans 4.1 beta IDE.

Answer 1

the client is a java application, and I have add the
handler to de handlerchain of the client's registry,
but it just doesn't work. What's the matter? For anyone following the forum who doesn't receive [email protected] email:
The question was also sent to the users@jwsdp email list and I responded there. Basically, I think the port qnames don't match, so maybe the one passed to the handler registry isn't correct. Without all the code and the wsdl, it's hard to tell. (One note: in jaxrpc 2.0, getting/setting a handler chain for a port that doesn't exist will result in an exception, which may help cut down on problems like this).
My suggestion was to add the handler to the config.xml file since it is a static stub. This is just a simpler way to do it.
Cheers,
Bobby