cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liu Cong (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CXF-2265) JMS Test Suite.
Date Thu, 30 Jul 2009 09:01:14 GMT

    [ https://issues.apache.org/jira/browse/CXF-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737030#action_12737030
] 

Liu Cong edited comment on CXF-2265 at 7/30/09 2:00 AM:
--------------------------------------------------------

A new test patch according to Willem's advice. 

I use JMSTemplate.receive to replace the MessageListenerContainer. 
This will create less threads.
https://issues.apache.org/jira/secure/attachment/12415002/test-patch3.txt

The list of changes is as follows:
    (1) Some SOAPFault processing int cxf-rt-bindings-soap subproject.
    (2) To generate the CorrelationID in the client of jms transport according to the following
rules. And I change the systest for the correlationid according to this.
        userCID -> userCID
        userCID + conduitSelectorPrefix -> userCID
        userCID + conduitSelectorPrefix + useConduitIdSelector(true) -> userCID
        userCID + conduitSelectorPrefix + useConduitIdSelector(false) -> userCID
        conduitSelectorPrefix + useConduitIdSelector(true) ->
        conduitSelectorPrefix + conduitId + index
        conduitSelectorPrefix + useConduitIdSelector(false) ->
        conduitSelectorPrefix + index
        useConduitIdSelector(true) -> conduitId + index
        useConduitIdSelector(false) -> the request message's messageID

        ->'s left side is the condition.
        ->'s right side is rule for generation of CorrelationID.
        userCID means that the client gives a CorrelationID.
        conduitSelectorPrefix means that the client configures in the wsdl.
        useConduitIdSelector means that the client configures in the wsdl.
        conduitId means that the string generated by the jms-tranport's JMSConduit.
        index is a autoincreasing number which indicates the uniqueness of the
        CorrelationID.

    (3) Remove JMSListener, and use JMSTemplate.receive method to deal with the response message.
    (4) Some small changes about JMSMessage's properties which is not right for specification.
    (5) Add test suite tests(http://dev.w3.org/2008/ws/soapjms/testcases/)(0001-1001). And
build the framework for test suite tests. 

      was (Author: liucong):
    A new test patch according to Willem's advice. 

I use JMSTemplate.receive to replace the MessageListenerContainer. 
This will create less threads.
https://issues.apache.org/jira/secure/attachment/12415002/test-patch3.txt
  
> JMS Test Suite.
> ---------------
>
>                 Key: CXF-2265
>                 URL: https://issues.apache.org/jira/browse/CXF-2265
>             Project: CXF
>          Issue Type: Sub-task
>          Components: Soap Binding
>            Reporter: Liu Cong
>         Attachments: test-patch.txt, test-patch2.txt, test-patch3.txt
>
>
> JMS Test suite ([WWW] http://dev.w3.org/2008/ws/soapjms/testcases/) . 
> We will finish an integration test for SOAP over JMS in this sub-task and make it pass
the JMS Test Suite.

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


Mime
View raw message