Forum Discussion

Raju_Vusirikala's avatar
Raju_Vusirikala
Contributor
16 years ago

composite project - Issues with File Saving

Hi

We are using SoapUI-Pro 2.5 beta1

We are importing the project into new workspace from composite project on the file system. And all the artifacts on the file system are readonly. In the workspace it is allowing to modify the artifacts(like say xxxtestcase.xml), but modified information is not saved to file sytem. Even we are not getting any error/warning messages about this.

if the artifacts are with read/write permission modified information in workspace is successfully persisted to file system, but it is saving as one big line, by this It is very hard to compare the orignal file content with modified content in version controling system.

Could you please help us by addressing above issues.

Thanks
Raju.

2 Replies

  • omatzura's avatar
    omatzura
    Super Contributor
    Hi Raju,

    these should be fixed in the latest nightly build; the global pretty-print now also applies to composite projects and the error handling should be better for read-only files.. Please try it out (http://www.eviware.com/nightly-builds) and let us know how it works for you.

    regards!

    /Ole
    eviware.com
  • Thanks Ole,

    I have tested the functionality with 11-03-2008 nightly build, And we are very thank full to you on providing support on requested feature.

    FYI save option is working as
    1. When we invoke the "Save" on TestCase Irrespective of content modified or not if the filesytem file is read-only it is showing Error Dialog with Access denied.
    2. When we invoke the "Save" on Project, No Error Dialog is shown. And nothing is got saved if the respective file is read-only.

    It will be greate help if you consider above scenarios and provide the fix on project level save option, so that we won't miss any modified changes in the workspace if we igore to save on test case level.


    Thanks
    Raju