You are viewing a plain text version of this content. The canonical link for it is here.

Posted to fx-dev@ws.apache.org by fx...@ws.apache.org on 2004/09/01 21:43:49 UTC

[jira] Updated: (WSFX-30) Added a few more test scenarios to TestJAX RPCHandler.java

The following issue has been updated:

    Updater: Venkat Reddy (mailto:vreddyp@gmail.com)
       Date: Wed, 1 Sep 2004 12:43 PM
    Comment:
Adding the recent updates to WSS4JHandler to make it aware of client-side and server-side context, and TestJAXRPCHandler with all the test scenarios and a few other files (keystores and property files) needed for interop tests with Sun's RI. The TestJAXRPCHandler is now an interop test for Sun's JWSDP. All the tests pass except for the failures in processing Timestamp token inside the response on client-side due to a possibly bug in the Timestamp class requiring <wsu:Expires> element as mandatory.
    Changes:
             Attachment changed to patch.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/WSFX-30?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-30

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-30
    Summary: Added a few more test scenarios to TestJAX RPCHandler.java
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Venkat Reddy

    Created: Wed, 18 Aug 2004 5:44 AM
    Updated: Wed, 1 Sep 2004 12:43 PM

Description:
Scenarios 3, 4 and 6 are working fine right now. The code for the remaining scenarios (1, 2, 5 and 7) also added but yet to be fixed, and is currently commented out. They fail because the same set of handler config parameters do not work for both request and response flows. I'm still thinking on how to fix this. Does anybody have suggestions on how to fix for this?

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