[jira] Created: (AXIS-1613) Call.setClientHandlers(...) - not distinguishing between req/resp handlers

[ax...@ws.apache.org]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1613

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1613
    Summary: Call.setClientHandlers(...) - not distinguishing between req/resp handlers
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Peter Smith

    Created: Sun, 17 Oct 2004 5:12 PM
    Updated: Sun, 17 Oct 2004 5:12 PM
Environment: Win2000 svr
axis-1_2beta3

Description:
[I previously wrote to the axis-user@ list with this issue but got no response so I am entering it into JIRA. I think it is a bug]

Background: 

I used Call.setClientHandlers() to programatically configure SOAP log handlers. For example, 

org.apache.axis.client.Call _call = createCall();
org.apache.axis.Handler reqHandler = new org.apache.axis.handlers.LogHandler();
org.apache.axis.Handler respHandler = new
org.apache.axis.handlers.LogHandler();
_call.setClientHandlers(reqHandler, respHandler);

Problem:

I stepped in the debugger to see how request/response handlers were treated internally but it didn't seem to make sense.

I noticed the implementation of Call.setClientHandlers makes a SOAPService with a null pivot Handler [Call.java].  I don't understand how the request and response log handlers are actually identified as really being "request" or "response" handlers when there is no "PivotIndicator" in the handler chain sitting between them.

I was wondering if something is not quite right here [possibly in the
SimpleTargetedChain.init method]

More evidence that something maybe is amiss can be seen when I used the setClientHandlers code as described above (passing both request & response LogHandlers) because although I see the SOAP logging I don't see any "Elapsed" timing information in the log. According to the LogHandler javadoc/implementation the timing information only appears when the handler is deployed in *both* request and response flows. But it is. 





---------------------------------------------------------------------
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