Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <user@jmeter.apache.org>
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <3E23519F8AF24968BDD081ECFBB4FFFD@VAIO>
From: "esc" <esc@informatik.uni-kiel.de>
To: <user@jmeter.apache.org>
Subject: Testing Vaadin 7 applications with JMeter?
Date: Thu, 6 Feb 2014 10:54:43 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0070_01CF2329.D7C18910"
Importance: Normal

------=_NextPart_000_0070_01CF2329.D7C18910
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

I have a problem with JMeter targeting Vaadin 7 applications. In =
contrast to previous Vaadin versions, it seems that testing with JMeter =
is not possible anymore.

Previous versions of Vaadin included component IDs ("DebugIDs") in the =
request information. IDs are required by Vaadin for synchronizing a =
client with the server application. Hence, they are essential for =
related JMeter Test Plans, as they make it possible to target certain =
application components. In contrast to its previous versions, Vaadin 7 =
does not include component IDs, which could optionally be assigned =
manually for testing purposes, in the request information anymore. =
Instead, it now uses only "connector IDs" which are generated by the =
Vaadin framework. In particular, the connector IDs change dynamically =
each time a user starts a new session.

Therewith, it seems that Vaadin 7 applications cannot be tested with =
JMeter. For a JMeter Test Plan, the ID of a component must be static, =
since it must be known by the Test Plan. This is not possible with =
Vaadin 7, since the Vaadin framework assigns the IDs dynamically; =
requests sent by JMeter are evaluated as being sent successfully, but a =
Vaadin 7 server application cannot handle the received information, =
since the statically assigned connector IDs in the Test Plan are unknown =
or incorrect regarding to the new session.

I have posted a related question with a concrete example in the Vaadin =
forum:

  https://vaadin.com/forum#!/thread/4829754

Furthermore, similar questions can be found there:

  https://vaadin.com/forum#!/thread/4331869
  https://vaadin.com/forum#!/thread/3394012

However, there are no solutions given yet. Has anybody managed to test a =
Vaadin 7 application with JMeter? It there any hint?

Thank you in advance!
------=_NextPart_000_0070_01CF2329.D7C18910--