Thanks, Paul. It's easier than I had thought. Kevin Hammond
----- Original Message ----- From: "Paul Glezen" <[EMAIL PROTECTED]> To: "JMeter Developers List" <[EMAIL PROTECTED]> Sent: Saturday, November 17, 2001 8:30 AM Subject: Re: Q: Logic for creating Generative Controller sub-menus? > Kevin, > > I believe this information comes from the getAddList() method. If you > check this out on the > org.apache.jmeter.protocol.http.control.HttpTestSample class, you'll see > the items that are reflected in the add menu. > > - Paul > > Paul Glezen > Consulting IT Specialist > IBM Software Services for WebSphere > 818 539 3321 > > > "Kevin Hammond" <[EMAIL PROTECTED]> on 11/17/2001 06:40:45 AM > > Please respond to "JMeter Developers List" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > cc: > Subject: Q: Logic for creating Generative Controller sub-menus? > > > > Hi, > > For a Generative Controller (for example, HTTP Request), how does JMeter > decide which config elements will be displayed in the Add menu? > > Currently, for HTTP Request, the following config elements are in the Add > menu: > * HTTP Cookie Manager > * HTTP Header Manager > * HTTP Authorization Manager > * Assertions > > These config elements are NOT in the Add menu: > * HTTP Request Defaults > * HTTP HTML Link Parser > * HTTP Proxy Server > > The JDBC Request and FTP Request Generative Controllers also contain a > subset of config elements in the Add menu. > > Why? This sounds like a bug to me (or an "undocumented feature"). > > Thanks, > Kevin Hammond > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED] > > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED] > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
