[jira] Closed: (WSFX-26) Created a JAX-RPC handler which doesn't have Axis dependencies.

[fx...@ws.apache.org]

Message:

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Thu, 12 Aug 2004 11:09 AM

Venkat,

Thanks for the hard work...I've added the code, refactored existing classes a bit to remove dependencies on org.apache.ws.axis package, and added Scenrio3 test case in test.interop.TestJAXRPCHandler. Can you please submit another patch with the rest of the scenario's when you get a chance? Am closing this bug.

thanks,
dims
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-26

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-26
    Summary: Created a JAX-RPC handler which doesn't have Axis dependencies.
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: WSFX
 Components: 
             WSS4J

   Assignee: Davanum Srinivas
   Reporter: Venkat Reddy

    Created: Thu, 12 Aug 2004 12:57 AM
    Updated: Thu, 12 Aug 2004 11:09 AM

Description:
Almost entire code for this new JAXRPC Handler comes from the existing Axis handlers - WSDoAllReceiver and WsDoAllSender. Removed all the axis dependencies in the code and merged both axis handlers into a single JAX-RPC handler.

This handler is tested for Axis deployment for both client-side and server-side, and for both request flow and response flow, and for Scenario3 test case using Ping3 service. The handler uses a new deployment config parameter called "deployment", which indicates whether it is being deployed on client-side or server-side.

To use the handler, modify the the deployment descriptors as shown below:

server-side (deploy.wsdd):
------------
  <requestFlow>
   <handler type="java:org.apache.axis.handlers.JAXRPCHandler">
    <parameter name="className" value="org.apache.ws.axis.security.WSS4JHandler"/>
    <parameter name="deployment" value="server"/>
. . . . . . . . . . 

  <responseFlow>
   <handler type="java:org.apache.axis.handlers.JAXRPCHandler">
    <parameter name="className" value="org.apache.ws.axis.security.WSS4JHandler"/>
    <parameter name="deployment" value="server"/>
    <parameter name="action" value="Signature Encrypt Timestamp"/>


client-side (Client-deploy.wsdd)
-----------
  <requestFlow>
   <handler type="java:org.apache.axis.handlers.JAXRPCHandler">
    <parameter name="className" value="org.apache.ws.axis.security.WSS4JHandler"/>
    <parameter name="deployment" value="client"/>
    <parameter name="action" value="Signature Encrypt Timestamp"/>
. . . . . . . . 

  <responseFlow>
   <handler type="java:org.apache.axis.handlers.JAXRPCHandler">
    <parameter name="className" value="org.apache.ws.axis.security.WSS4JHandler"/>
    <parameter name="deployment" value="client"/>

Everything else is same as for WSDoAllReceiver and WSDoAllSender handlers.

Thanks
Venkat



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira