Kevin_Slade
Contributor
Joined 18 years ago
User Profile
User Widgets
Contributions
Re: How can I clone a project?
One way I have used is to take a copy of the project file and to simply rename the copy to whatever you want the new project to be called. This preserves all of the settings and any stored values such as usernames and passwords. Hope this helps Kevin1.2KViews0likes0CommentsRe: The generated XML is out of order after project update
Hi Dain I will check using "Refactor Definition", BUT the main issue is that when some of the operations, especially PipeCreate are edited, by the deletion and later addition of one of the array elements, the XML that is generated, is out of order. This may be due to the complexity of the definition for this operation. Regards Kevin2KViews0likes0CommentsRe: The generated XML is out of order after project update
Hi Dain Attached is a copy of the SoapUI test suite prior to the 4.2.1 update. I use "Update Definition" to move forward from one WSDL revision to a later version. The second posting is taken from a soap call PipeCreate that was generated from the 4.2.1 WSDL as a new SoapUI project and the Soap request for PipeCreate had values entered, and the some of the array elements added, deleted and then added again. It is the subsequent additions that cause the data elements to placed out of order. This is the crux of the problem. As can be seen from the attached project the test cases can be complex. Please let me know if you need more information Thanks Kevin2KViews0likes0CommentsRe: The generated XML is out of order after project update
Further to above information, when array elements are deleted and then later recreated (eg DelayDataSource) the DelayDataSource section of the XML is generated immediately below the <Config> rather than below the <nin:DataSource> elements where it is expected. The result of this is that the XML ordering is lost and the Axis2C soap server refuses to process the generated XML. Manually moving the out of order XML elements to to appropraite place allows the Axis2C server to process the request. <Config> <nin:DelayDataSource> <nin:DataObject> <nin:Type>ROTFILE</nin:Type> <nin:Name>rot_col3</nin:Name> </nin:DataObject> <nin:Delay>15</nin:Delay> </nin:DelayDataSource> <nin:DelayDataSource> <nin:DataObject> <nin:Type>ROTFILE</nin:Type> <nin:Name>rot_col4</nin:Name> </nin:DataObject> <nin:Delay>20</nin:Delay> </nin:DelayDataSource> <nin:Enabled>false</nin:Enabled> <!--0 or more repetitions:--> <nin:DataSource> <nin:Type>ROTFILE</nin:Type> <nin:Name>rot_col1</nin:Name> </nin:DataSource> <!--Optional:--> <nin:DataSource> <nin:Type>ROTFILE</nin:Type> <nin:Name>rot_col2</nin:Name> </nin:DataSource> <!-- The <nin:DelayDataSource> elements need to be inserted here --> <nin:MergeSources>CONCURRENT</nin:MergeSources>2KViews0likes0CommentsThe generated XML is out of order after project update
Attached are 2 sets of WSDL & XSD files for sequential versions of one of our projects. When the 4.2.1 set is loaded into SoapUI Pro Snapshot soapui-pro-3.6.2-SNAPSHOT-linux-bin.zip 11-May-2011 or older the generated XML for the PipeCreate request maintains the expected XML structure order. However if the 4.2.0 set is loaded and then the definitions are updated using the 4.2.1 set, generated xml is not ordered as expected. The result is that the SOAP server that has been created using Axis2C complains and fails to parse the XML. A sample from the request after the upgrade is below. Note that the extra DelayDataSource and MapInterface sections occur earlier in the XML than expected. <soapenv:Body> <nin:PipeCreate> <Name>test</Name> <Config> <nin:DelayDataSource> <nin:DataObject> <nin:Type>ROTFILE</nin:Type> <nin:Name>r3</nin:Name> </nin:DataObject> <nin:Delay>12</nin:Delay> </nin:DelayDataSource> <nin:MapInterface> <nin:In>B</nin:In> <nin:Out>A</nin:Out> </nin:MapInterface> <nin:MapInterface> <nin:In>C</nin:In> <nin:Out>A</nin:Out> </nin:MapInterface> <nin:MapInterface> <nin:In>D</nin:In> <nin:Out>A</nin:Out> </nin:MapInterface> <nin:Enabled>false</nin:Enabled> <!--1 or more repetitions:--> <nin:DataSource> <nin:Type>ROTFILE</nin:Type> <nin:Name>R1</nin:Name> </nin:DataSource> <!--Zero or more repetitions:--> <nin:DelayDataSource> <nin:DataObject> <nin:Type>ROTFILE</nin:Type> <nin:Name>r2</nin:Name> </nin:DataObject> <nin:Delay>12</nin:Delay> </nin:DelayDataSource> <!--Optional:--> <nin:MergeSources>?</nin:MergeSources> <!--Optional:--> <nin:DataSink> <nin:Type>DAG</nin:Type> <nin:Name>dagmod.3</nin:Name> </nin:DataSink> <!--Optional:--> <!--Optional:--> <!--0 to 4 repetitions:--> <nin:MapInterface> <nin:In>A</nin:In> <nin:Out>A</nin:Out> </nin:MapInterface> <nin:OutputDataType>ERF</nin:OutputDataType> <!--Optional:--> <!--Optional:--> <!--Optional:--> <!--Optional:--> <!--Optional:--> <!--Optional:--> <nin:PilotEnabled>false</nin:PilotEnabled> <!--Optional:--> <nin:Replay> <nin:Enabled>true</nin:Enabled> <!--Optional:--> <nin:Rate> <nin:Mode>RELATIVE</nin:Mode> <!--Optional:--> <!--Optional:--> <nin:ScaleFactor>1</nin:ScaleFactor> <nin:BitRate>123</nin:BitRate> </nin:Rate> <!--Optional:--> <!--Optional:--> <nin:Count>13</nin:Count> <!--Optional:--> </nin:Replay> <!--Optional:--> <nin:FastFilterEnabled>?</nin:FastFilterEnabled> <!--Optional:--> </Config> </nin:PipeCreate> </soapenv:Body> </soapenv:Envelope>4.4KViews0likes5CommentsRe: How can I test for a Connection refused error
Hello I have finally had a chance to get back to this. The problem with the suggestion is that because the connection is refused, an exception is thrown and no MessageExchange object is available to be queried. I have looked at trying a groovy script following the failing step, but because of the exception, there again is no MessageExchange object to be used. A second issue is that because of the exception, the script is shown to have failed, even though this is the correct expected result. Cheers Kevin2KViews0likes1CommentHow can I test for a Connection refused error
I have a test case where the expected action is that the server should not be accessable and therefore a Connection refused return is expected. The Java system reports an error as below: Thu Jan 28 09:57:47 NZDT 2010:ERROR:Exception in request: java.net.ConnectException: Connection refused Is there any thing I can do to trap this error or to allow the error to occur and still have the tests validate that nothing was returned, in response to the call. Thanks Kevin2.8KViews1like3CommentsRe: [SOLVED]Performance
I have had similar issues. It is usually related to the amount of memeory that is allocated to the Java VM. I run SoapUI under a 64 bit Linux with 8Gb ram and use -Xmx3500m (up from -Xmx384m). This causes the java vm to allocate sufficent memory to allow us to run some very large (8Mb +) soapUI projects without issues. On 32 bit systems increase the size intil java just refuses to start and then use the largest working size. On linux the command to start SoapUI pro is in the soap/bin directory and is called soapui-pro.sh. Hope this helps Kevin883Views0likes0CommentsRe: How do I over-ride Definition Url when using testrunner
After looking at the problem and the above solution carefully, this is not actually addressing my original problem. That is that I simply wish to force the WSDL definition to either use the cached value or to reload it from the specified target, not the original target that was used to create the test suite, or last used to update the WSDL definitions. Make no mistake, the above discussion has been very useful as it has exposed another bug in the WSDL definition, where every response should have the option of returning a fault message as well as a valid response. A second downside of using this assertion in each test step is that it also causes the axis2c server to crash when the WDL is reloaded for each test step. This also has a maked impact on the performance of each teststep regardless of whether the server was crashing, due to the extra data to be retrieved from the server to support this test assertion. Regards Kevin2.1KViews0likes0Comments