On 11/10/2007, b4d93r <[EMAIL PROTECTED]> wrote: > > Well it turns out I really wasn't done with this! %-| > > We were able to get our xml files formated correctly for SOAP use and were > able to get the test to run and return the desired results using the > WebServive(SOAP) Request. Now (after manually setting up 1000+ requests in a > test I discover a way to call those files using a csv file. :confused: > > I'm now trying to figure this out. How can I set up my test to do a SOAP > request using the CSV Data Set Config option to randomly send the 5998 xml > files we have?
Are you going to use the data to name the file then? > Would this be the design format? > > Test Plan > +Thread Group > ++CSV Data Set Config > ++WebService(SOAP) Request > +View Tree Results > Workbench OK > I understand that the .csv file needs to be in the same directory as the > .jmx (Jmeter) test file correct? Does the XML files need to be there too? >From the CSV documentation: "Relative file names are resolved with respect to the current test plan. Absolute file names are also supported," XML files are relative to the current working directory; again absolute names are allowed. You should be able to confirm these with a simple test. > We will start there as I have other questions on setting up the CSV Data Set > Config option. The current documentation is at: http://jakarta.apache.org/jmeter/usermanual/component_reference.html#CSV_Data_Set_Config > I'm hating JMeter but yet I'm also loving it! :-U > > b4d93r wrote: > > > > Ok, I think I have this figured out. For our needs, we are trying to post > > data from an XML file to the server. However the SOAP request is probably > > not going to do what we need here. Also the XML file we are sending has > > proprietary header information and must be sent. I discovered that if I > > remove that header info and replace it with SOAP formatting I get a passed > > status. However it doesn't return the expected result. This is either due > > to the proprietary data being gone or the server isn't configured > > properly. > > > > I then tried a regular HTTP Request sending the xml file in both the post > > and get methods. It liked the get (because it was getting data from the > > server) but didn't like the post method. Again, the data recieved in the > > get method wasn't what the expected result should be but it did give what > > it should for a "get" command. > > > > So at this point i believe that I can't send an xml file as a post. I will > > research this option but for all intensive purposes, I was barking up the > > wrong tree! thank you guys and I do apologize for all the confusion. > > > > Steve > > > > > > > > sebb-2 wrote: > >> > >> On 03/10/2007, b4d93r <[EMAIL PROTECTED]> wrote: > >>> > >>> The " -" are in there. (mind you I didn't create this script so any info > >>> here > >>> would be of great value.) > >> > >> They are not valid XML, so need to be removed. > >> > >> If you display XML in Internet Explorer, then it shows "-" and "+" as > >> handles to allow the XML to be contracted and expanded, but they are > >> not (should not be) present in the original. > >> > >>> As for the line break, I'm not sure. I'll see what we can find out. > >>> > >>> (Dumb question but I have to ask.) Should I have the Soap header and > >>> envelope in that code? I've been wondering about this but haven't tried > >>> it. > >> > >> The Soap header is an HTTP header, like User-Agent or Host, and should > >> not be in the data. > >> > >> AFAIK, SOAP handlers need a SOAP envelope. > >> > >> Ask the server admin people if necessary. > >> > >> > >>> Thanks! > >>> Steve > >>> > >>> > >>> > >>> sebb-2 wrote: > >>> > > >>> > I assume the " - " at the beginning of some lines are not in the real > >>> > data? > >>> > > >>> > There's also a line-break in the xsi:schemaLocation attribute which I > >>> > assume has been added by the mail transport. > >>> > > >>> > Apart from these, the data seems to be valid XML, but has no SOAP > >>> > header or envelope. > >>> > > >>> > S. > >>> > On 03/10/2007, b4d93r <[EMAIL PROTECTED]> wrote: > >>> >> > >>> >> You know what, I didn't post it like I thought I did. My fault I do > >>> >> apologize! > >>> >> (NOTE: I did change specific info to something more generic, again > >>> due to > >>> >> confidentiality reasons.) > >>> >> > >>> >> Here it is... > >>> >> > >>> >> <?xml version="1.0" encoding="UTF-8" ?> > >>> >> - <VertexEnvelope xmlns="urn:companyainc:o-series:tps:4:0" > >>> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >>> >> xsi:schemaLocation="urn:companyainc:o-series:tps:4:0 > >>> >> CompanyAInc_Envelope.xsd"> > >>> >> - <Login> > >>> >> <UserName>anyusername</UserName> > >>> >> <Password>anypassword</Password> > >>> >> </Login> > >>> >> - <QuotationRequest documentDate="2007-10-01" > >>> >> returnAssistedParamaterIndicator="TRUE" transactionType="SALE"> > >>> >> - <Seller> > >>> >> - <Company> > >>> >> 001 > >>> >> - <Division> > >>> >> 009 > >>> >> <Department /> > >>> >> </Division> > >>> >> </Company> > >>> >> </Seller> > >>> >> - <Customer> > >>> >> <CustomerCode classCode="Number">00000000</CustomerCode> > >>> >> - <Destination> > >>> >> <StreetAddress>1234 CARESWELL ST</StreetAddress> > >>> >> <City>Denver</City> > >>> >> <MainDivision>CO</MainDivision> > >>> >> <PostalCode>80202</PostalCode> > >>> >> <Country>United States</Country> > >>> >> </Destination> > >>> >> </Customer> > >>> >> - <LineItem taxDate="2007-08-16" lineItemId="1" lineItemNumber="1"> > >>> >> <Quantity>5</Quantity> > >>> >> <UnitPrice>1.00</UnitPrice> > >>> >> - <FlexibleFields> > >>> >> <FlexibleCodeField fieldId="1">060036084</FlexibleCodeField> > >>> >> </FlexibleFields> > >>> >> </LineItem> > >>> >> - <LineItem taxDate="2007-08-16" lineItemId="1" lineItemNumber="2"> > >>> >> <Quantity>3</Quantity> > >>> >> <UnitPrice>10.00</UnitPrice> > >>> >> - <FlexibleFields> > >>> >> <FlexibleCodeField fieldId="1">090294518</FlexibleCodeField> > >>> >> </FlexibleFields> > >>> >> </LineItem> > >>> >> - <LineItem taxDate="2007-08-16" lineItemId="1" lineItemNumber="3"> > >>> >> <Quantity>1</Quantity> > >>> >> <UnitPrice>200.00</UnitPrice> > >>> >> - <FlexibleFields> > >>> >> <FlexibleCodeField fieldId="1">080111798</FlexibleCodeField> > >>> >> </FlexibleFields> > >>> >> </LineItem> > >>> >> - <LineItem taxDate="2007-08-16" lineItemId="1" lineItemNumber="4"> > >>> >> <Quantity>1</Quantity> > >>> >> <UnitPrice>250.00</UnitPrice> > >>> >> - <FlexibleFields> > >>> >> <FlexibleCodeField fieldId="1">000048969</FlexibleCodeField> > >>> >> </FlexibleFields> > >>> >> </LineItem> > >>> >> </QuotationRequest> > >>> >> </VertexEnvelope> > >>> >> -- > >>> >> View this message in context: > >>> >> > >>> http://www.nabble.com/Default-header-%28Still-playing-with-the-SOAP-stuff%29-tf4557859.html#a13023245 > >>> >> Sent from the JMeter - User mailing list archive at Nabble.com. > >>> >> > >>> >> > >>> >> --------------------------------------------------------------------- > >>> >> 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] > >>> > > >>> > > >>> > > >>> > >>> -- > >>> View this message in context: > >>> http://www.nabble.com/Default-header-%28Still-playing-with-the-SOAP-stuff%29-tf4557859.html#a13023816 > >>> Sent from the JMeter - User mailing list archive at Nabble.com. > >>> > >>> > >>> --------------------------------------------------------------------- > >>> 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] > >> > >> > >> > > > > > > -- > View this message in context: > http://www.nabble.com/Default-header-%28Still-playing-with-the-SOAP-stuff%29-tf4557859.html#a13146468 > Sent from the JMeter - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
