axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Daniels <gdani...@macromedia.com>
Subject RE: Urgent: Help needed with deployment of my own transport and d ynamic provider in the current build
Date Mon, 11 Feb 2002 16:00:53 GMT
 
The WSDD syntax for deploying a service with a particular Handler as the "pivot" is as follows:
 
<service name="P2plusService" provider="Handler">
  <parameter name="handlerClass" value="com.apag.p2plus.p2tools.P2plusServer$AxisDispatcher"/>
  etc...
</service>

-----Original Message-----
From: Thomas Börkel [mailto:tb@ap-ag.com]
Sent: Monday, February 11, 2002 9:09 AM
To: Axis Mailinglist
Subject: Urgent: Help needed with deployment of my own transport and dynamic provider in the
current build



HI! 

For Axis alpha-3, I had the following deployment XML: 

<m:deploy xmlns:m="AdminService"> 
  <handler name="P2plusDispatcher" class="com.apag.p2plus.p2tools.P2plusServer$AxisDispatcher"/>

  <transport name="P2plus" pivot="P2plusDispatcher"/> 
  <service name="P2plusService" pivot="P2plusDispatcher" > 
    <option name="className" value="com.apag.p2plus.p2core.NullObject" /> 
    <option name="methodName" value="toString" /> 
  </service> 
</m:deploy> 


This resulted in a server-config.wsdd like this (some things might be redundant here): 

 <handler name="P2plusDispatcher" type="java:com.apag.p2plus.p2tools.P2plusServer$AxisDispatcher"/>

 <service name="P2plusService" provider="Handler"> 
  <parameter name="methodName" value="toString"/> 
  <parameter name="className" value="com.apag.p2plus.p2core.NullObject"/> 
  <parameter name="handlerClass" value="com.apag.p2plus.p2tools.P2plusServer$AxisDispatcher"/>

 </service> 
 <transport name="P2plus"/> 


With the current build, the deployment seems to have changed. .wsdd files are now needed.
So I changed my deployment file into a .wsdd file like this:

<deployment name="test" xmlns=" http://xml.apache.org/axis/wsdd/ <http://xml.apache.org/axis/wsdd/>
" 
    xmlns:java=" http://xml.apache.org/axis/wsdd/providers/java <http://xml.apache.org/axis/wsdd/providers/java>
"> 
 <handler name="P2plusDispatcher" type="java:com.apag.p2plus.p2tools.P2plusServer$AxisDispatcher"/>

 <transport name="P2plus" pivot="P2plusDispatcher"/> 
 <service name="P2plusService" pivot="P2plusDispatcher" > 
   <parameter name="className" value="com.apag.p2plus.p2core.NullObject" /> 
   <parameter name="methodName" value="toString" /> 
 </service> 
/deployment> 


This results in a server-config.wsdd like this: 

 <handler name="P2plusDispatcher" type="java:com.apag.p2plus.p2tools.P2plusServer$AxisDispatcher"/>

 <service name="P2plusService"> 
  <parameter name="methodName" value="toString"/> 
  <parameter name="className" value="com.apag.p2plus.p2core.NullObject"/> 
 </service> 
 <transport name="P2plus" pivot="P2plusDispatcher"/> 


As you can see, the service has no handler anymore. 

And even if I modify the server-config.wsdd manually and provide the line with the handler,
I still get NULL back from msgContext.getResponseMessage() after axisServer.invoke(msgContext).

The filetransport sample works though. 

Any ideas? 

Thanks! 

Regards, 
Thomas 


Mime
View raw message