You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jervis Liu (JIRA)" <ji...@apache.org> on 2006/12/26 08:36:21 UTC

[jira] Created: (CXF-334) Logical handler's close() method is not properly called after completion

Logical handler's close() method is not properly called after completion
------------------------------------------------------------------------

                 Key: CXF-334
                 URL: http://issues.apache.org/jira/browse/CXF-334
             Project: CXF
          Issue Type: Sub-task
          Components: JAX-WS Runtime
            Reporter: Jervis Liu


Logical handler's close() method is not properly called after completion. A test case can be found from HandlerInvocationTest.testHandlersInvoked()
JAX-WS section 9.3.2.3:

A handler's close method is called at the conclusion of a message exchange pattern (MEP). It is called 
just prior to the binding dispatching the final message, fault or exception of the MEP and may be used to 
clean up per-MEP resources allocated by a handler. The close method is only called on handlers that were 
previously invoked via either handleMessage or handleFault 

Conformance (Invoking close): At the conclusion of an MEP, an implementation MUST call the close 
method of each handler that was previously invoked during that MEP via either handleMessage or handle- 
Fault.

Conformance (Order of close invocations): Handlers are invoked in the reverse order that they appear 
in the handler chain.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (CXF-334) Logical handler's close() method is not properly called after completion

Posted by "Jervis Liu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jervis Liu closed CXF-334.
--------------------------

    Resolution: Fixed

> Logical handler's close() method is not properly called after completion
> ------------------------------------------------------------------------
>
>                 Key: CXF-334
>                 URL: https://issues.apache.org/jira/browse/CXF-334
>             Project: CXF
>          Issue Type: Sub-task
>          Components: JAX-WS Runtime
>            Reporter: Jervis Liu
>         Attachments: cxf-334.patch
>
>
> Logical handler's close() method is not properly called after completion. A test case can be found from HandlerInvocationTest.testHandlersInvoked()
> JAX-WS section 9.3.2.3:
> A handler's close method is called at the conclusion of a message exchange pattern (MEP). It is called 
> just prior to the binding dispatching the final message, fault or exception of the MEP and may be used to 
> clean up per-MEP resources allocated by a handler. The close method is only called on handlers that were 
> previously invoked via either handleMessage or handleFault 
> Conformance (Invoking close): At the conclusion of an MEP, an implementation MUST call the close 
> method of each handler that was previously invoked during that MEP via either handleMessage or handle- 
> Fault.
> Conformance (Order of close invocations): Handlers are invoked in the reverse order that they appear 
> in the handler chain.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CXF-334) Logical handler's close() method is not properly called after completion

Posted by "Jervis Liu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464087 ] 

Jervis Liu commented on CXF-334:
--------------------------------

Hi Unreal, the patch loos good, just one comment. The test added only tests the out bound scenario (client side), can we also add some tests to test the in bound scenario please (server side in bound or client side in bound). Thanks.



> Logical handler's close() method is not properly called after completion
> ------------------------------------------------------------------------
>
>                 Key: CXF-334
>                 URL: https://issues.apache.org/jira/browse/CXF-334
>             Project: CXF
>          Issue Type: Sub-task
>          Components: JAX-WS Runtime
>            Reporter: Jervis Liu
>         Attachments: cxf-334.patch
>
>
> Logical handler's close() method is not properly called after completion. A test case can be found from HandlerInvocationTest.testHandlersInvoked()
> JAX-WS section 9.3.2.3:
> A handler's close method is called at the conclusion of a message exchange pattern (MEP). It is called 
> just prior to the binding dispatching the final message, fault or exception of the MEP and may be used to 
> clean up per-MEP resources allocated by a handler. The close method is only called on handlers that were 
> previously invoked via either handleMessage or handleFault 
> Conformance (Invoking close): At the conclusion of an MEP, an implementation MUST call the close 
> method of each handler that was previously invoked during that MEP via either handleMessage or handle- 
> Fault.
> Conformance (Order of close invocations): Handlers are invoked in the reverse order that they appear 
> in the handler chain.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (CXF-334) Logical handler's close() method is not properly called after completion

Posted by "unrealjiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

unrealjiang updated CXF-334:
----------------------------

    Attachment: cxf-334.patch

> Logical handler's close() method is not properly called after completion
> ------------------------------------------------------------------------
>
>                 Key: CXF-334
>                 URL: https://issues.apache.org/jira/browse/CXF-334
>             Project: CXF
>          Issue Type: Sub-task
>          Components: JAX-WS Runtime
>            Reporter: Jervis Liu
>         Attachments: cxf-334.patch
>
>
> Logical handler's close() method is not properly called after completion. A test case can be found from HandlerInvocationTest.testHandlersInvoked()
> JAX-WS section 9.3.2.3:
> A handler's close method is called at the conclusion of a message exchange pattern (MEP). It is called 
> just prior to the binding dispatching the final message, fault or exception of the MEP and may be used to 
> clean up per-MEP resources allocated by a handler. The close method is only called on handlers that were 
> previously invoked via either handleMessage or handleFault 
> Conformance (Invoking close): At the conclusion of an MEP, an implementation MUST call the close 
> method of each handler that was previously invoked during that MEP via either handleMessage or handle- 
> Fault.
> Conformance (Order of close invocations): Handlers are invoked in the reverse order that they appear 
> in the handler chain.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (CXF-334) Logical handler's close() method is not properly called after completion

Posted by "Jervis Liu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464088 ] 

Jervis Liu commented on CXF-334:
--------------------------------

I will apply this patch now and will apply a following patch which contains more test cases. 

> Logical handler's close() method is not properly called after completion
> ------------------------------------------------------------------------
>
>                 Key: CXF-334
>                 URL: https://issues.apache.org/jira/browse/CXF-334
>             Project: CXF
>          Issue Type: Sub-task
>          Components: JAX-WS Runtime
>            Reporter: Jervis Liu
>         Attachments: cxf-334.patch
>
>
> Logical handler's close() method is not properly called after completion. A test case can be found from HandlerInvocationTest.testHandlersInvoked()
> JAX-WS section 9.3.2.3:
> A handler's close method is called at the conclusion of a message exchange pattern (MEP). It is called 
> just prior to the binding dispatching the final message, fault or exception of the MEP and may be used to 
> clean up per-MEP resources allocated by a handler. The close method is only called on handlers that were 
> previously invoked via either handleMessage or handleFault 
> Conformance (Invoking close): At the conclusion of an MEP, an implementation MUST call the close 
> method of each handler that was previously invoked during that MEP via either handleMessage or handle- 
> Fault.
> Conformance (Order of close invocations): Handlers are invoked in the reverse order that they appear 
> in the handler chain.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira