https://issues.apache.org/bugzilla/show_bug.cgi?id=52054
Sebb <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Sebb <[email protected]> 2011-10-20 08:10:14 UTC --- (In reply to comment #5) > JMS is an asynchronous protocol so doing this seems to me weird. However, the id is set on return from the send message call; as such this part is synchronous. > Furthermore, JMSMessageId is in Request Headers not response headers. > > So if we decide to implement it it is more an enhancement than a bug. The Regex Extractor was written assuming that the request details are already known, so it was not felt necessary to allow access to the request headers, only the response headers. However, there are probably other samplers where not all of the request details are known in advance - or easy to access - so it probably would be worthwile enhancing some of the PostProcessors accordingly. See Bug 52061. As a workround in the meantime, you can use the BSH or BSF postprocessor to access the response request headers. Resolving this issue, as the work is now to be done as part of Bug 52061. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
