Return-Path: 
 <jmeter-dev-return-8850-apmail-jakarta-jmeter-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-jmeter-dev-archive@www.apache.org
Received: (qmail 92181 invoked from network); 7 Oct 2004 00:51:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 7 Oct 2004 00:51:33 -0000
Received: (qmail 22131 invoked by uid 500); 7 Oct 2004 00:51:32 -0000
Delivered-To: apmail-jakarta-jmeter-dev-archive@jakarta.apache.org
Received: (qmail 22105 invoked by uid 500); 7 Oct 2004 00:51:32 -0000
Mailing-List: contact jmeter-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:jmeter-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:jmeter-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:jmeter-dev-help@jakarta.apache.org>
List-Post: <mailto:jmeter-dev@jakarta.apache.org>
List-Id: "JMeter Developers List" <jmeter-dev.jakarta.apache.org>
Reply-To: "JMeter Developers List" <jmeter-dev@jakarta.apache.org>
Delivered-To: mailing list jmeter-dev@jakarta.apache.org
Received: (qmail 22091 invoked by uid 500); 7 Oct 2004 00:51:32 -0000
Received: (qmail 22088 invoked by uid 99); 7 Oct 2004 00:51:32 -0000
X-ASF-Spam-Status: No, hits=-10.0 required=10.0
	tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194)
  by apache.org (qpsmtpd/0.28) with SMTP; Wed, 06 Oct 2004 17:51:31 -0700
Received: (qmail 92178 invoked by uid 1721); 7 Oct 2004 00:51:30 -0000
Date: 7 Oct 2004 00:51:30 -0000
Message-ID: <20041007005130.92177.qmail@minotaur.apache.org>
From: sebb@apache.org
To: jakarta-jmeter-cvs@apache.org
Subject: cvs commit: jakarta-jmeter/xdocs/usermanual build-test-plan.xml
 component_reference.xml
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

sebb        2004/10/06 17:51:30

  Modified:    xdocs/usermanual Tag: rel-2_0 build-test-plan.xml
                        component_reference.xml
  Log:
  Clarify scope of Config Managers
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.13.2.2  +10 -2     jakarta-jmeter/xdocs/usermanual/build-test-plan.xml
  
  Index: build-test-plan.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-test-plan.xml,v
  retrieving revision 1.13.2.1
  retrieving revision 1.13.2.2
  diff -u -r1.13.2.1 -r1.13.2.2
  --- build-test-plan.xml	12 Jun 2004 12:11:24 -0000	1.13.2.1
  +++ build-test-plan.xml	7 Oct 2004 00:51:30 -0000	1.13.2.2
  @@ -83,6 +83,14 @@
   <figure image="scoping3.png">complex example</figure>
   <p>In this example, the requests are named to reflect the order in which they will be executed.  Timer #1 will apply to Requests Two, Three, and Four (notice how order is irrelevant for hierarchical elements).  Assertion #1 will apply only to Request Three.  Timer #2 will affect all the requests.</p>
   <p>Hopefully these examples make it clear how configuration (hierarchical) elements are applied.  If you imagine each Request being passed up the tree branches, to its parent, then to its parent's parent, etc, and each time collecting all the configuration elements of that parent, then you will see how it works.  </p>
  +<b>
  +The Configuration elements Header Manager, Cookie Manager and Authorization manager are
  +treated differently from the Configuration Default elements.
  +The settings from the Configuration Default elements are merged into a set of values that the Sampler has access to.
  +However, the settings from the Managers are not merged.
  +If more than one Manager is in the scope of a Sampler, 
  +only one Manager is used, but there is currently no way to specify <b>which</b> is used.
  +</b>
   </subsection>
   
   </section>
  
  
  
  1.87.2.8  +11 -3     jakarta-jmeter/xdocs/usermanual/component_reference.xml
  
  Index: component_reference.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v
  retrieving revision 1.87.2.7
  retrieving revision 1.87.2.8
  diff -u -r1.87.2.7 -r1.87.2.8
  --- component_reference.xml	25 Sep 2004 20:59:50 -0000	1.87.2.7
  +++ component_reference.xml	7 Oct 2004 00:51:30 -0000	1.87.2.8
  @@ -1029,6 +1029,9 @@
   
   <component index="15.4.1" name="HTTP Authorization Manager" screenshot="http-config/http-auth-manager.gif">
   
  +<note>If there is more than one Authorization Manager in the scope of a Sampler,
  +there is currently no way to sepcify which one is to be used.</note>
  +
   <description>
   <p>The Authorization Manager lets you specify one or more user logins for web pages that are
   restricted using Basic HTTP Authentication.  You see this type of authentication when you use
  @@ -1088,6 +1091,9 @@
   
   <component index="15.4.2" name="HTTP Cookie Manager" screenshot="http-config/http-cookie-manager.gif">
   
  +<note>If there is more than one Cookie Manager in the scope of a Sampler,
  +there is currently no way to sepcify which one is to be used.</note>
  +
   <description><p>The Cookie Manager element has two functions:<br></br>
   First, it stores and sends cookies just like a web browser. If you have an HTTP Request and
   the response contains a cookie, the Cookie Manager automatically stores that cookie and will
  @@ -1259,6 +1265,8 @@
   
   
   <component index="15.4.9" name="HTTP Header Manager" screenshot="http-config/http-header-manager.gif">
  +<note>If there is more than one Header Manager in the scope of a Sampler,
  +there is currently no way to sepcify which one is to be used.</note>
   <description><p>The Header Manager lets you add or override HTTP request headers.</p>
   </description>
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org