RE: RPCDispatcher

[Peter Haensgen]

Hi,
 
yes, you can implement your own provider. I have done it this way (my
provider is called "enfinity:Pipeline"):
 

*       register a provider factory: 
org.apache.axis.deployment.wsdd.WSDDProvider.registerProvider(new QName("
http://www.intershop.com/enfinity <http://www.intershop.com/enfinity> ",
"Pipeline"), new EnfinityPipelineWSDDProvider());

*       implement the provider factory:

public class EnfinityPipelineWSDDProvider extends WSDDProvider
{
    public Handler newProviderInstance(WSDDService service,
EngineConfiguration registry)
        throws Exception
    {
        return new PipelineProvider();
    }
}

*       implement the actual provider:

public class PipelineProvider extends JavaProvider {...}

*       use the provider in the WSDD files:
<deployment name="enfinity" xmlns="  <http://xml.apache.org/axis/wsdd/>
http://xml.apache.org/axis/wsdd/";
    xmlns:enfinity="  <http://www.intershop.com/enfinity>
http://www.intershop.com/enfinity";
    <service name="ProductWebService" provider="enfinity:Pipeline">

(make sure that the namespace URI in the WSDD matches the URI that was used
in the QName for the factory registration).


good luck,
Peter
 

-----Original Message-----
From: BOURLON Agnès [mailto:agnes_bourlon@;yahoo.fr]
Sent: 05 November 2002 14:07
To: [EMAIL PROTECTED]
Subject: RPCDispatcher


Hello,
 
I would like to know if it is possible to switch the Axis RPCProvider class
into a custom extended class ?
I found in server-config.wsdd a tag :
 <handler name="RPCDispatcher"
type="java:org.apache.axis.providers.java.RPCProvider"/>
and replace like that : 
 <handler name="RPCDispatcher" type="java:com.xxx.MyRPCProvider"/>
 
But it doesn't have any effect....
Is it possible?
 
Thanks,
Agnes