axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glenn Mi" <>
Subject RE: How to plug in a differen RPCProvider ?
Date Thu, 09 May 2002 23:30:47 GMT
Thank you for the response. I tried to add the handler in the response flow
and it is called. But it seems that it's still handled by the provider first
and then reprocessed again by the new handler. And then I tried the provider
option and it doesn't work, no matter if I put it in deploy.wsdd or

I need a way to default the RPC handler to my own RPCHandler without setting
it in every service's deploy.wsdd.


-----Original Message-----
From: Jason Zheng []
Sent: Thursday, May 09, 2002 3:06 PM
To: ''
Subject: RE: How to plug in a differen RPCProvider ?

You might have to take care of it from deploy.wsdd.
I had written a provider for Aixs to expose Structs to soap service.  In the
   	<handler name="name of handler" type="java:handlerClassName ">
  		<parameter ....
  	<service name="service namespace"  >
			<java:provider className="handlerClassName"
isStatic="false" />
			<handler type="name of handler"/>
	    	<parameter ...

Good luck.

-----Original Message-----
From: Glenn Mi []
Sent: Thursday, May 09, 2002 5:57 PM
To: axis-dev
Subject: How to plug in a differen RPCProvider ?

Hi !

I am migrating our Collaxa's WebService Orchestration Server from SOAP2.2 to
I need to plug in a different RPCProvider to take care of the SOAP calls. I
saw an
option in server-config.wsdd:
<handler name="RPCDispatcher"
but it doesn't seem to make any difference.

Is that an outdated option that needs to be removed ? Or is it in the plan
to be implemented ?
And, what is the best way to plug in a different PRCProvider ?

Thanks !

Glenn Mi

View raw message