Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 15782 invoked from network); 19 Dec 2005 12:48:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Dec 2005 12:48:39 -0000 Received: (qmail 5838 invoked by uid 500); 19 Dec 2005 12:48:38 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 5819 invoked by uid 500); 19 Dec 2005 12:48:38 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 5808 invoked by uid 99); 19 Dec 2005 12:48:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Dec 2005 04:48:38 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [199.244.214.30] (HELO iron04.kdc.capitalone.com) (199.244.214.30) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Dec 2005 04:48:37 -0800 Received: from unknown (HELO KDCP4PIMS01.cof.ds.capitalone.com) ([10.4.100.52]) by iron04.kdc.capitalone.com with ESMTP; 19 Dec 2005 07:48:16 -0500 X-IronPort-AV: i="3.99,267,1131339600"; d="scan'208"; a="19772467:sNHT23977232" Received: from KDCP4PBHD02.cof.ds.capitalone.com ([10.4.100.51]) by KDCP4PIMS01.cof.ds.capitalone.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Dec 2005 07:48:15 -0500 Received: from KDCP4PMBX03.cof.ds.capitalone.com ([10.4.100.42]) by KDCP4PBHD02.cof.ds.capitalone.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Dec 2005 07:48:15 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: stub transport Date: Mon, 19 Dec 2005 07:48:15 -0500 Message-ID: <45E26618E6D0D74CA16839B00E0C981402C01193@KDCP4PMBX03.cof.ds.capitalone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: stub transport Thread-Index: AcYEiXPvMGZGl/AES2SU8txC1eXzCgAEPgVA From: "Stettler, Robert" To: "Apache AXIS C User List" X-OriginalArrivalTime: 19 Dec 2005 12:48:15.0665 (UTC) FILETIME=[7AB2CA10:01C6049A] Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Sweet! Exactly what I was looking for. -----Original Message----- From: Adrian Dick [mailto:adrian.dick@uk.ibm.com] Sent: Monday, December 19, 2005 5:45 AM To: Apache AXIS C User List Subject: RE: stub transport Hi, Here are some simple instruction on using the MockServer utility we use for testing Axis c++ client without a server. Compile mock server java code (found within /tests/utils/monitor ) Run the mock server: java org.apache.test.MockServer -p -r The server response file is a text file containing the full HTTP response, it will look something like this: HTTP/1.1 200 OK Server: WebSphere Application Server/5.1 Content-Type: text/xml; charset=utf-8 Content-Language: en-GB Transfer-Encoding: chunked 1ad < soapenv:Body>5 0 The easiest way to generate this file is to capture the communication from a real server but if that isn't possible you will need to generate by hand (plenty of examples within /test/auto_build/testcases/output ) Rather than providing the specific chunk size (1ad, on the line ahead of the payload) you can provide ### and the MockServer will calculate the correct size. If your testcase makes multiple calls to the web service, you can simply append all the requests (in the correct order!) within the server response file. Once the test has been completed you need to run the following: java org.apache.test.StopTCPMonitor -p -h I hope that is of help Adrian _______________________________________ Adrian Dick (adrian.dick@uk.ibm.com) "Stettler, Robert" wrote on 16/12/2005 14:00:42: > I have 1.5 Final source. > > -----Original Message----- > From: John Hawkins [mailto:HAWKINSJ@uk.ibm.com] > Sent: Friday, December 16, 2005 5:09 AM > To: Apache AXIS C User List > Subject: RE: stub transport > > > hi Robert, > > no docs as it's an internal tool used within the test framework. Do > you use the source or binaries? It's not shipped with the binaries.. > > > > "Stettler, Robert" > 14/12/2005 16:51 > > Please respond to > "Apache AXIS C User List" > > To > > "Apache AXIS C User List" > > cc > > > > Subject > > RE: stub transport > > > > > > > > > > > I am looking for a simple solution to simulate the server side, so > that I can test my client code completely. I know I can create > apache stubs and I have generated stubs in WebLogic, but I am > looking for something simpler. > > > You meantioned a unit test system? Can you point me to some doc? > > -----Original Message----- > From: John Hawkins [mailto:HAWKINSJ@uk.ibm.com] > Sent: Wednesday, December 14, 2005 11:40 AM > To: Apache AXIS C User List > Subject: Re: stub transport > > > hi Robert, > sorry unit testing of what - the service? So you want to emulate a > client? We currently have a "unit test" system where we can emulate > the service. > > "Stettler, Robert" > 14/12/2005 14:37 > > > Please respond to > "Apache AXIS C User List" > > > > To > > > > cc > > > > Subject > > stub transport > > > > > > > > > > > > > > Is there any sort of stub http transport? Maybe something file > driven? I would like to use something like that for unit testing? > > > > > > The information contained in this e-mail is confidential and/or proprietary > to Capital One and/or its affiliates. The information transmitted herewith > is intended only for use by the individual or entity to which it is > addressed. If the reader of this message is not the intended recipient, > you are hereby notified that any review, retransmission, dissemination, > distribution, copying or other use of, or taking of any action in reliance > upon this information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the material > from your computer. > > > > The information contained in this e-mail is confidential and/or proprietary > to Capital One and/or its affiliates. The information transmitted herewith > is intended only for use by the individual or entity to which it is > addressed. If the reader of this message is not the intended recipient, > you are hereby notified that any review, retransmission, dissemination, > distribution, copying or other use of, or taking of any action in reliance > upon this information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the material > from your computer. > > > > The information contained in this e-mail is confidential and/or proprietary > to Capital One and/or its affiliates. The information transmitted herewith > is intended only for use by the individual or entity to which it is > addressed. If the reader of this message is not the intended recipient, > you are hereby notified that any review, retransmission, dissemination, > distribution, copying or other use of, or taking of any action in reliance > upon this information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the material > from your computer. > The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.