JAX-RPC handler chain

2006-09-28 Thread Oliver Wulff
Hi all I've implemented my custom handler but noticed that the handler chain is built up each time I make a call on my proxy class. Is there are reason that the handler chain is not re-used for the proxy instance (see HandlerChainImpl.newHandler)? Thanks Oliver *** BITTE

Antwort: Support of other protocols

2005-08-26 Thread Oliver Wulff
Scott, take a look to Celtix ESB (open source) or Artix (commercial) from IONA Technologies. It does support different bindings and transports (SOAP, IIOP, Websphere MQ, JMS, Tuxedo,...). Celtix: http://celtix.objectweb.org/ Artix: http://www.iona.com/products/artix/welcome.htm Oliver

Antwort: RE: Difference between rpc and doc literal

2005-08-10 Thread Oliver Wulff
The following documentation is also very helpful: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/html/rpc_literal.asp Oliver Johan Kumps

Antwort: Re: Blockers for Axis 1.2 Final

2005-04-28 Thread Oliver Wulff
What about http://issues.apache.org/jira/browse/AXIS-1947? This bug prevents us from using Axis in client applications. There is no workaround. Tim K. (Gmane)

getHandlerChain(), port name

2005-04-15 Thread Oliver Wulff
I've created a custom JAX-RPC handler and had some problem to register it. QName portName = new QName(, BerechtigungBerechtigung_1_0SOAPPort); List chain = service.getHandlerRegistry().getHandlerChain(portName); The reason of the problem was the different port name that is used internally by