RE: Session Bean Sampler
Hi, Same question again. I noticed that a new release of JMeter is now out and does not include this contribution. Seb do you have any idea if you plan to integrate it and when? Regards Guillaume Lasnier * Software Engineer * SunGard * Decalog * 147 Bureaux de la Colline, Bâtiment E * 92213 Saint-Cloud CEDEX * France * Phone: +33 1 55 39 18 74 * Fax: +33 1 55 39 18 01 * www.sungard.com www.sungard.com _ From: Guillaume Lasnier [EMAIL PROTECTED]@SUNGARD Sent: Monday, August 28, 2006 10:00 AM To: JMeter Developers List (E-mail) Subject: Session Bean Sampler Hi all, As anyone tried the Session Bean Sampler submitted here http://issues.apache.org/bugzilla/show_bug.cgi?id=40181 http://issues.apache.org/bugzilla/show_bug.cgi?id=40181 ? I would appreciate feed backs. -- Guillaume Lasnier Technical RD Phone : +33 1 55 39 18 74 Confidentiality Notice: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Message confidentiel : Les informations contenues dans ce message sont destinées à un usage personnel et confidentiel du destinataire indiqué ci-dessus. Si le lecteur de ce message n'est pas le destinataire prévu, ou n'est pas une personne en charge de le délivrer au destinataire voulu, vous êtes par la présente informé que vous avez reçu ce document par erreur, et que tout examen, transmission, distribution ou copie de ce message est totalement interdit. Si vous avez reçu cette communication par erreur, nous vous remercions de bien vouloir nous avertir immédiatement par e-mail et de détruire le message d'origine. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Confidentiality Notice: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Message confidentiel : Les informations contenues dans ce message sont destinées à un usage personnel et confidentiel du destinataire indiqué ci-dessus. Si le lecteur de ce message n'est pas le destinataire prévu, ou n'est pas une personne en charge de le délivrer au destinataire voulu, vous êtes par la présente informé que vous avez reçu ce document par erreur, et que tout examen, transmission, distribution ou copie de ce message est totalement interdit. Si vous avez reçu cette communication par erreur, nous vous remercions de bien vouloir nous avertir immédiatement par e-mail et de détruire le message d'origine.
Re: Session Bean Sampler
I have just had a very quick look at the patch. It's not immediately clear if it can be added to the JMeter code-base, as there seem to be changes to quite a few utility classes. The changes may be upwards-compatible, but I cannot tell at present. There seem to be several irrelevant changes (e.g. to formatting) which make the review quite time-consuming. I'll try and have a more detailed look later. S On 26/02/07, Guillaume Lasnier [EMAIL PROTECTED] wrote: Hi, Same question again. I noticed that a new release of JMeter is now out and does not include this contribution. Seb do you have any idea if you plan to integrate it and when? Regards Guillaume Lasnier * Software Engineer * SunGard * Decalog * 147 Bureaux de la Colline, Bâtiment E * 92213 Saint-Cloud CEDEX * France * Phone: +33 1 55 39 18 74 * Fax: +33 1 55 39 18 01 * www.sungard.com www.sungard.com _ From: Guillaume Lasnier [EMAIL PROTECTED]@SUNGARD Sent: Monday, August 28, 2006 10:00 AM To: JMeter Developers List (E-mail) Subject: Session Bean Sampler Hi all, As anyone tried the Session Bean Sampler submitted here http://issues.apache.org/bugzilla/show_bug.cgi?id=40181 http://issues.apache.org/bugzilla/show_bug.cgi?id=40181 ? I would appreciate feed backs. -- Guillaume Lasnier Technical RD Phone : +33 1 55 39 18 74 Confidentiality Notice: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Message confidentiel : Les informations contenues dans ce message sont destinées à un usage personnel et confidentiel du destinataire indiqué ci-dessus. Si le lecteur de ce message n'est pas le destinataire prévu, ou n'est pas une personne en charge de le délivrer au destinataire voulu, vous êtes par la présente informé que vous avez reçu ce document par erreur, et que tout examen, transmission, distribution ou copie de ce message est totalement interdit. Si vous avez reçu cette communication par erreur, nous vous remercions de bien vouloir nous avertir immédiatement par e-mail et de détruire le message d'origine. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Confidentiality Notice: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Message confidentiel : Les informations contenues dans ce message sont destinées à un usage personnel et confidentiel du destinataire indiqué ci-dessus. Si le lecteur de ce message n'est pas le destinataire prévu, ou n'est pas une personne en charge de le délivrer au destinataire voulu, vous êtes par la présente informé que vous avez reçu ce document par erreur, et que tout examen, transmission, distribution ou copie de ce message est totalement interdit. Si vous avez reçu cette communication par erreur, nous vous remercions de bien vouloir nous avertir immédiatement par e-mail et de détruire le message d'origine. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41704] New: - Make CSV Data Set Config use specified encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41704. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41704 Summary: Make CSV Data Set Config use specified encoding Product: JMeter Version: 2.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: HTTP AssignedTo: jmeter-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Currently, the CSV Data Set Config does not allow the user to specify what character set encoding is used in the csv file which contains the test data to use in a Jmeter test. Therefore, the csv data files must have the default system character set encoding. Currently, it is the java class FileReader which is used to read the file, and that assumes the default platform character set encoding for the file. It would be useful to be able to specify the character set encoding used in a csv data file, so that you can use different encodings. That will also allow you to use the same data files on different operating systems, which can have different default character set encodings. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41704] - Make CSV Data Set Config use specified encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41704. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41704 --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 05:52 --- Created an attachment (id=19637) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=19637action=view) Suggested patch to add encoding to CSV data set This is a patch agaist SVN svn.apache.org/repos/asf/jakarta/jmeter/branches/rel-2-2 as of today. Comments / suggestions to the patch are welcomed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41705] New: - Make HTTP Sampler POST using specified encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41705. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41705 Summary: Make HTTP Sampler POST using specified encoding Product: JMeter Version: 2.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: HTTP AssignedTo: jmeter-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Currently, both variants of the HTTP Request (the normal and the one using HTTP Client) is using default encoding when submitt a POST request. It ought to be possible to specify what encoding should be used when posting the data to the web server. The Http Request (class name HttpSampler / PostWriter) is currently using the default platform character encoding when doing a POST request. The Http Request HTTPClient (class name HttpSampler2) is currently using ISO-8859-1 as the character encoding when doing a POST request. It would be nice if it was possible to specify the encoding to use for the POST in the HTTP Request parameters section. As the situation is today, if you have som values which are encoded as UTF-8, they are not properly transmitted to the web server. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41705] - Make HTTP Sampler POST using specified encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41705. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41705 --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 06:15 --- I think this bug is related, but I'm not exactly sure, to the following existing bugs : 41305, 33435. It also seems to be somewhat related to 38287, 25753, 30823, both they seem to talk about http get requests, and not http post requests, like I do. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41705] - Make HTTP Sampler POST using specified encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41705. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41705 --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 06:20 --- Created an attachment (id=19638) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=19638action=view) Patch for allowing http post with specified encoding Attached is a patch for allow HTTP POST requests to be sent with user specified encoding. The patch is against the svn.apache.org/repos/asf/jakarta/jmeter/branches/rel-2-2 as of today. Comment / suggestions to the patch are welcomed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41705] - Make HTTP Sampler POST using specified encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41705. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41705 --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 06:37 --- Note that the patch above does not change the POSTing of multiform/files, handled in the same sendPostData method in the HTTPSampler2 class. Currently, UTF-8 is hardcoded for multiform/files in that method, it would be trivial to change that code to use the user specified encoding, as is now done for normal POST request. I haven't changed the posting of files in the HTTPSampler class neither. I think that the org.apache.jmeter.protocol.http.sampler.HTTPSampleResult, which I think is the class which writes the output that is shown in the View results tree-Request pane, incorrectly displays what is sent to the web server. The reason why I think so, is that it displays the same data before and after I apply the patch above. The HTTPSampleResult seems to just be using Strings, and not actually displaying the content as written to the output stream to the web server, so that explains, I think, why it displays different from what is being sent to the web server. I was thinking about patching the HTTPSampleResult, so that it would print the name of the encoding used, but I will wait for feedback on the patch above before doing more work. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41707] New: - HTTP Proxy XML-RPC support
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41707 Summary: HTTP Proxy XML-RPC support Product: JMeter Version: 2.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: HTTP AssignedTo: jmeter-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] JMeters http proxy does not record xml-rpc calls correctly. An xml-rpc call is not posted in the usual name=value structure, but simply as one big chunk of xml. I have made a patch which first of all check if the postdata is xml, by using some very simple string comparison on the query string. If the postdata seems to be xml, it is parsed as xml and checked against an un-official xml-rpc xsd schema taken from ibiblio.org. If any error occurs or the xml-rpc cannot be validated against the schema, the request is recorded the usual way. This is my first patch for the jmeter project, so please bear with me. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41707] - HTTP Proxy XML-RPC support
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41707 --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 09:39 --- Created an attachment (id=19639) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=19639action=view) HTTPSamplerBase supporting xml-rpc recording. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41707] - HTTP Proxy XML-RPC support
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41707 --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 09:40 --- Created an attachment (id=19640) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=19640action=view) XmlRpcErrorHandler used for xsd schema checking of xml-rpc call -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41707] - HTTP Proxy XML-RPC support
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41707. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41707 --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 09:40 --- Created an attachment (id=19641) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=19641action=view) XML-RPC xsd schema (un-official) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP Proxy with XML-RPC
Hi My code is now submitted to bugzilla as #41707. Looking forward to hear your reactions/comments ... /Jesper From: sebb [EMAIL PROTECTED] Reply-To: JMeter Developers List jmeter-dev@jakarta.apache.org To: JMeter Developers List jmeter-dev@jakarta.apache.org Subject: Re: HTTP Proxy with XML-RPC Date: Sun, 25 Feb 2007 18:36:14 + Thanks! Sounds useful. Please create a Bugzilla enhancement issue describing the code. You can then add any patches or new code as attachments to the issue. Please ensure that any patches are in unified diff format (as generated by Eclipse), and are generated against branches/rel-2-2, not the trunk, which is very out of date. On 24/02/07, Two Hawk [EMAIL PROTECTED] wrote: Hi I have added some code to allow xml-rpc communication to be recorded correctly when using the http proxy. Would anyone be interested in adding this to the codebase? If yes, how do i proceed from here? Best regards, Jesper _ Download din yndlingsmusik på MSN Music: http://www.msn.dk/music - det er nemt og billigt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Ta' på udsalg året rundt på MSN Shopping: http://shopping.msn.dk - her finder du altid de bedste priser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP Proxy with XML-RPC
Thanks. Just wondering why the query string needs to be compared against a schema? If the content starts with ?xml surely this means that the string should not be parsed into name/value pairs? Or am I missing something here? Unless the DOM parsing is needed, it would obviously be a lot cheaper to omit it. Some minor issues: - unless the DOMParser is thread-safe, one cannot use a static copy. - catch Exception is not a good idea; one should only catch expected errors - should probably use log.warn rather than log.debug for logging the exception. S. On 26/02/07, Two Hawk [EMAIL PROTECTED] wrote: Hi My code is now submitted to bugzilla as #41707. Looking forward to hear your reactions/comments ... /Jesper From: sebb [EMAIL PROTECTED] Reply-To: JMeter Developers List jmeter-dev@jakarta.apache.org To: JMeter Developers List jmeter-dev@jakarta.apache.org Subject: Re: HTTP Proxy with XML-RPC Date: Sun, 25 Feb 2007 18:36:14 + Thanks! Sounds useful. Please create a Bugzilla enhancement issue describing the code. You can then add any patches or new code as attachments to the issue. Please ensure that any patches are in unified diff format (as generated by Eclipse), and are generated against branches/rel-2-2, not the trunk, which is very out of date. On 24/02/07, Two Hawk [EMAIL PROTECTED] wrote: Hi I have added some code to allow xml-rpc communication to be recorded correctly when using the http proxy. Would anyone be interested in adding this to the codebase? If yes, how do i proceed from here? Best regards, Jesper _ Download din yndlingsmusik på MSN Music: http://www.msn.dk/music - det er nemt og billigt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Ta' på udsalg året rundt på MSN Shopping: http://shopping.msn.dk - her finder du altid de bedste priser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41704] - Make CSV Data Set Config use specified encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=41704. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41704 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2007-02-26 11:38 --- Thanks for the contribution. Looks mostly OK. However, it changes the public API of the FileServer class, as the reserveFile method now has an extra parameter. This could cause 3rd party applications to fail. Easy enough to resolve by overloading the method. Also, the encoding could perhaps be added to the FileEntry class instead of using a separate HashMap. I'll see about adding this - no need to recreate the patch at present. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session Bean Sampler
I've just had a more detailed look at the patch file, and it contains lots of irrelevant/unnecessary changes. I'm afraid the patches cannot be applied as they stand - there's far too much work involved. I suggest you attach the new files as files, rather than patches (zip them up as there are quite a few). Any _essential_ changes to existing files should be attached as one or more patch files. These should be in unified diff against the branch/rel-2-2 code. S On 26/02/07, sebb [EMAIL PROTECTED] wrote: I have just had a very quick look at the patch. It's not immediately clear if it can be added to the JMeter code-base, as there seem to be changes to quite a few utility classes. The changes may be upwards-compatible, but I cannot tell at present. There seem to be several irrelevant changes (e.g. to formatting) which make the review quite time-consuming. I'll try and have a more detailed look later. S On 26/02/07, Guillaume Lasnier [EMAIL PROTECTED] wrote: Hi, Same question again. I noticed that a new release of JMeter is now out and does not include this contribution. Seb do you have any idea if you plan to integrate it and when? Regards Guillaume Lasnier * Software Engineer * SunGard * Decalog * 147 Bureaux de la Colline, Bâtiment E * 92213 Saint-Cloud CEDEX * France * Phone: +33 1 55 39 18 74 * Fax: +33 1 55 39 18 01 * www.sungard.com www.sungard.com _ From: Guillaume Lasnier [EMAIL PROTECTED]@SUNGARD Sent: Monday, August 28, 2006 10:00 AM To: JMeter Developers List (E-mail) Subject: Session Bean Sampler Hi all, As anyone tried the Session Bean Sampler submitted here http://issues.apache.org/bugzilla/show_bug.cgi?id=40181 http://issues.apache.org/bugzilla/show_bug.cgi?id=40181 ? I would appreciate feed backs. -- Guillaume Lasnier Technical RD Phone : +33 1 55 39 18 74 Confidentiality Notice: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Message confidentiel : Les informations contenues dans ce message sont destinées à un usage personnel et confidentiel du destinataire indiqué ci-dessus. Si le lecteur de ce message n'est pas le destinataire prévu, ou n'est pas une personne en charge de le délivrer au destinataire voulu, vous êtes par la présente informé que vous avez reçu ce document par erreur, et que tout examen, transmission, distribution ou copie de ce message est totalement interdit. Si vous avez reçu cette communication par erreur, nous vous remercions de bien vouloir nous avertir immédiatement par e-mail et de détruire le message d'origine. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Confidentiality Notice: The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Message confidentiel : Les informations contenues dans ce message sont destinées à un usage personnel et confidentiel du destinataire indiqué ci-dessus. Si le lecteur de ce message n'est pas le destinataire prévu, ou n'est pas une personne en charge de le délivrer au destinataire voulu, vous êtes par la présente informé que vous avez reçu ce document par erreur, et que tout examen, transmission, distribution ou copie de ce message est totalement interdit. Si vous avez reçu cette communication par erreur, nous vous remercions de bien vouloir nous avertir immédiatement par e-mail et de détruire le message d'origine. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r512075 - in /jakarta/jmeter/branches/rel-2-2: ./ lib/ src/htmlparser16/org/apache/jmeter/protocol/http/parser/ src/protocol/http/org/apache/jmeter/protocol/http/parser/ test/src/org/apach
Author: sebb Date: Mon Feb 26 15:28:57 2007 New Revision: 512075 URL: http://svn.apache.org/viewvc?view=revrev=512075 Log: Update to htmlparser 2.0 Added: jakarta/jmeter/branches/rel-2-2/LICENSE(htmlparser).txt jakarta/jmeter/branches/rel-2-2/lib/htmllexer-2.0-20060923.jar (with props) jakarta/jmeter/branches/rel-2-2/lib/htmlparser-2.0-20060923.jar (with props) jakarta/jmeter/branches/rel-2-2/src/protocol/http/org/apache/jmeter/protocol/http/parser/HtmlParserHTMLParser.java Removed: jakarta/jmeter/branches/rel-2-2/src/htmlparser16/org/apache/jmeter/protocol/http/parser/HtmlParserHTMLParser16.java jakarta/jmeter/branches/rel-2-2/test/src/org/apache/jmeter/protocol/http/parser/TestHTMLParser16.java Modified: jakarta/jmeter/branches/rel-2-2/NOTICE jakarta/jmeter/branches/rel-2-2/build.xml jakarta/jmeter/branches/rel-2-2/xdocs/changes.xml Added: jakarta/jmeter/branches/rel-2-2/LICENSE(htmlparser).txt URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/LICENSE%28htmlparser%29.txt?view=autorev=512075 == --- jakarta/jmeter/branches/rel-2-2/LICENSE(htmlparser).txt (added) +++ jakarta/jmeter/branches/rel-2-2/LICENSE(htmlparser).txt Mon Feb 26 15:28:57 2007 @@ -0,0 +1,213 @@ +Common Public License Version 1.0 + +THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC +LICENSE (AGREEMENT). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM +CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. + +1. DEFINITIONS + +Contribution means: + +a) in the case of the initial Contributor, the initial code and +documentation distributed under this Agreement, and + +b) in the case of each subsequent Contributor: + +i) changes to the Program, and + +ii) additions to the Program; + +where such changes and/or additions to the Program originate from and are +distributed by that particular Contributor. A Contribution 'originates' from a +Contributor if it was added to the Program by such Contributor itself or anyone +acting on such Contributor's behalf. Contributions do not include additions to +the Program which: (i) are separate modules of software distributed in +conjunction with the Program under their own license agreement, and (ii) are not +derivative works of the Program. + +Contributor means any person or entity that distributes the Program. + +Licensed Patents mean patent claims licensable by a Contributor which are +necessarily infringed by the use or sale of its Contribution alone or when +combined with the Program. + +Program means the Contributions distributed in accordance with this Agreement. + +Recipient means anyone who receives the Program under this Agreement, +including all Contributors. + +2. GRANT OF RIGHTS + +a) Subject to the terms of this Agreement, each Contributor hereby grants +Recipient a non-exclusive, worldwide, royalty-free copyright license to +reproduce, prepare derivative works of, publicly display, publicly perform, +distribute and sublicense the Contribution of such Contributor, if any, and such +derivative works, in source code and object code form. + +b) Subject to the terms of this Agreement, each Contributor hereby grants +Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed +Patents to make, use, sell, offer to sell, import and otherwise transfer the +Contribution of such Contributor, if any, in source code and object code form. +This patent license shall apply to the combination of the Contribution and the +Program if, at the time the Contribution is added by the Contributor, such +addition of the Contribution causes such combination to be covered by the +Licensed Patents. The patent license shall not apply to any other combinations +which include the Contribution. No hardware per se is licensed hereunder. + +c) Recipient understands that although each Contributor grants the licenses +to its Contributions set forth herein, no assurances are provided by any +Contributor that the Program does not infringe the patent or other intellectual +property rights of any other entity. Each Contributor disclaims any liability to +Recipient for claims brought by any other entity based on infringement of +intellectual property rights or otherwise. As a condition to exercising the +rights and licenses granted hereunder, each Recipient hereby assumes sole +responsibility to secure any other intellectual property rights needed, if any. +For example, if a third party patent license is required to allow Recipient to +distribute the Program, it is Recipient's responsibility to acquire that license +before distributing the Program. + +d) Each Contributor represents that to its knowledge it has sufficient +copyright rights in its Contribution, if any, to grant the copyright license set +forth in this Agreement. + +3. REQUIREMENTS + +A Contributor may choose to distribute the Program
svn commit: r512080 - /jakarta/jmeter/branches/rel-2-2/src/htmlparser16/
Author: sebb Date: Mon Feb 26 15:47:20 2007 New Revision: 512080 URL: http://svn.apache.org/viewvc?view=revrev=512080 Log: Update to htmlparser 2.0 Removed: jakarta/jmeter/branches/rel-2-2/src/htmlparser16/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r512081 - /jakarta/jmeter/branches/rel-2-2/lib/
Author: sebb Date: Mon Feb 26 15:48:09 2007 New Revision: 512081 URL: http://svn.apache.org/viewvc?view=revrev=512081 Log: Update to htmlparser 2.0 Modified: jakarta/jmeter/branches/rel-2-2/lib/ (props changed) Propchange: jakarta/jmeter/branches/rel-2-2/lib/ -- --- svn:ignore (original) +++ svn:ignore Mon Feb 26 15:48:09 2007 @@ -1,6 +1,5 @@ ext opt -htmlparser*.jar jorphan.jar activation.jar iaik_jce.jar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP Proxy with XML-RPC
Hi Thanks for your comments. My reason for validating the xml against the schema is only to be sure that it is an xml-rpc call and not just some xml being posted. The alternative is to call the feature isXmlData, not isXmlRpc, and then skip the parsing and schema checking? Also, i will fix my code according to your comments asap, and repost my files on bugzilla. A quick question regarding my bugzilla post; should new files (xml-rpc.xsd and XmlRpcErrorHandler.java) go as patches or ...? /Jesper From: sebb [EMAIL PROTECTED] Reply-To: JMeter Developers List jmeter-dev@jakarta.apache.org To: JMeter Developers List jmeter-dev@jakarta.apache.org Subject: Re: HTTP Proxy with XML-RPC Date: Mon, 26 Feb 2007 18:26:40 + Thanks. Just wondering why the query string needs to be compared against a schema? If the content starts with ?xml surely this means that the string should not be parsed into name/value pairs? Or am I missing something here? Unless the DOM parsing is needed, it would obviously be a lot cheaper to omit it. Some minor issues: - unless the DOMParser is thread-safe, one cannot use a static copy. - catch Exception is not a good idea; one should only catch expected errors - should probably use log.warn rather than log.debug for logging the exception. S. On 26/02/07, Two Hawk [EMAIL PROTECTED] wrote: Hi My code is now submitted to bugzilla as #41707. Looking forward to hear your reactions/comments ... /Jesper From: sebb [EMAIL PROTECTED] Reply-To: JMeter Developers List jmeter-dev@jakarta.apache.org To: JMeter Developers List jmeter-dev@jakarta.apache.org Subject: Re: HTTP Proxy with XML-RPC Date: Sun, 25 Feb 2007 18:36:14 + Thanks! Sounds useful. Please create a Bugzilla enhancement issue describing the code. You can then add any patches or new code as attachments to the issue. Please ensure that any patches are in unified diff format (as generated by Eclipse), and are generated against branches/rel-2-2, not the trunk, which is very out of date. On 24/02/07, Two Hawk [EMAIL PROTECTED] wrote: Hi I have added some code to allow xml-rpc communication to be recorded correctly when using the http proxy. Would anyone be interested in adding this to the codebase? If yes, how do i proceed from here? Best regards, Jesper _ Download din yndlingsmusik på MSN Music: http://www.msn.dk/music - det er nemt og billigt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Ta' på udsalg året rundt på MSN Shopping: http://shopping.msn.dk - her finder du altid de bedste priser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Del dine store filer uden problemer på MSN Messenger: http://messenger.msn.dk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
