Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 75160 invoked from network); 14 Jul 2009 19:52:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jul 2009 19:52:56 -0000 Received: (qmail 66951 invoked by uid 500); 14 Jul 2009 19:53:06 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 66878 invoked by uid 500); 14 Jul 2009 19:53:06 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 66868 invoked by uid 99); 14 Jul 2009 19:53:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 19:53:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [62.75.158.78] (HELO mail.liquid-reality.de) (62.75.158.78) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jul 2009 19:52:55 +0000 Received: from [10.0.0.102] (HSI-KBW-085-216-025-040.hsi.kabelbw.de [85.216.25.40]) by mail.liquid-reality.de (Postfix) with ESMTP id 19658B48002 for ; Tue, 14 Jul 2009 19:52:35 +0000 (UTC) Message-ID: <4A5CE21A.3060802@die-schneider.net> Date: Tue, 14 Jul 2009 21:52:58 +0200 From: Christian Schneider User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: how to design a systest framework for SOAP/JMS test suite References: <4A5B30D4.2060901@gmail.com> <4A5C3715.3090805@gmail.com> In-Reply-To: <4A5C3715.3090805@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Sounds good to me. The messages could be read from files on the classpath. In my company we do these tests with camel but I don´t think it would be good to have this dependency. Greetings Christian Willem Jiang schrieb: > Hi > > Since SOAP/JMS test suit could work with the other SOAP/JMS implementation, > I think we should not just write the test against CXF stack. > > We could leverage the spring template and listener to implement the > generation of > the test JMS message, check the response JMS message. > > In this way the test just check the JMS SOAP message as pure JMS > message, and > it can run with CXF soap/jms server and CXF soap/jms client. > > Thought ? > > Willem > > liucong wrote: > >> Hi, >> >> I'm working on SOAP/JMS test suite >> (http://dev.w3.org/2008/ws/soapjms/testcases/). >> >> For each test case, I need to check the JMS message properties. So I >> need to get the outgoing and incoming message of each mep. But I don't >> know how to get the JMS message from the JMS transport. >> >> If I store the JMS message in the request and responce context, I can >> get the JMS message easily. In the client, I think it is easy for me to >> store the response JMS message. But it is a little hard to store the >> request JMS message. Because I use spring-jms to send the JMS message. I >> don't know exactly what message is sent by the spring-jms. >> >> So my question is: Is there any way to get the outgoing and incoming JMS >> message easily? >> >> Thanks a lot. >> >> liu >> >> > > >