Contributions
Re: [Resolved] NPE in 5.1.2 trying to load existing 4.6 project
Ok, I guess I answered most of those questions, I understand how soapUI Pro is now embedded in ready api and so on. It also seems like it is loading up our 4.6 composite project without any issues, which is great news! Regards, Ton Vlaming10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2KViews0likes0CommentsRe: [Resolved] NPE in 5.1.2 trying to load existing 4.6 project
I am sorry for being dense perhaps (I only spent a few minutes trying to figure it out from the website)... Is ReadyAPI just the new name for soapUI ? And does it support migrating 4.6 projects? Otherwise this will of course still be an issue for us Regards, Ton Vlaming10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2KViews0likes0Comments[Resolved] NPE in 5.1.2 trying to load existing 4.6 project
Hi there, I was quite excited seeing that 5.1.2 fixed an issue I had logged - about getting random characters attached to folder and file names when converting a 4.6 project to 5.1... Unfortunately, it seems 5.1.2 Pro can't even load my 4.6 Pro composite project... That is not supposed to be a problem, is it? I see the NPE below in the error log. Please note I am not able to provide a copy of my project due to company sensitive information stored in it (staging environment accounts and such). Thu Oct 02 15:17:06 ADT 2014:ERROR:com.eviware.soapui.support.SoapUIException: Failed to load project from file [file:/Users/tvlaming/git/SocialcloudQE/apiqe_soapUI_project/] com.eviware.soapui.support.SoapUIException: Failed to load project from file [file:/Users/tvlaming/git/SocialcloudQE/apiqe_soapUI_project/] at com.eviware.soapui.impl.wsdl.WsdlProjectPro.loadProject(SourceFile:321) at com.eviware.soapui.impl.wsdl.WsdlProject.<init>(WsdlProject.java:220) at com.eviware.soapui.impl.wsdl.WsdlProjectPro.<init>(SourceFile:181) at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(SourceFile:45) at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(SourceFile:16) at com.eviware.soapui.impl.WorkspaceImpl.reloadProject(WorkspaceImpl.java:490) at com.eviware.soapui.impl.WorkspaceImpl.openProject(WorkspaceImpl.java:592) at com.eviware.soapui.impl.wsdl.actions.project.OpenProjectAction.perform(OpenProjectAction.java:39) at com.eviware.soapui.impl.wsdl.actions.project.OpenProjectAction.perform(OpenProjectAction.java:30) at com.eviware.soapui.support.action.swing.SwingActionDelegate.actionPerformed(SwingActionDelegate.java:89) at com.eviware.soapui.support.action.swing.DefaultActionList.performDefaultAction(DefaultActionList.java:97) at com.eviware.soapui.ui.Navigator$TreeMouseListener$1.run(Navigator.java:368) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:312) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:694) at java.awt.EventQueue$3.run(EventQueue.java:692) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.run(EventDispatchThread.java:91) Caused by: java.lang.NullPointerException at com.eviware.soapui.impl.support.loadsave.CompositeProjectSaver.a(SourceFile:782) at com.eviware.soapui.impl.support.loadsave.CompositeProjectSaver.b(SourceFile:735) at com.eviware.soapui.impl.support.loadsave.CompositeProjectSaver.b(SourceFile:728) at com.eviware.soapui.impl.support.loadsave.CompositeProjectSaver.load(SourceFile:674) at com.eviware.soapui.impl.support.wsdl.UrlWsdlLoaderPro.handleFile(SourceFile:27) at com.eviware.soapui.impl.wsdl.support.wsdl.UrlWsdlLoader.load(UrlWsdlLoader.java:116) at com.eviware.soapui.impl.wsdl.support.wsdl.UrlWsdlLoader.load(UrlWsdlLoader.java:96) at com.eviware.soapui.impl.wsdl.WsdlProjectPro.loadProject(SourceFile:192) ... 25 more10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes7CommentsRe: [Res]script folder in soapUI project conflicts with 5.1.1
Yes we added a script folder to store our own groovy scripts after creating the original project of course. And yes, we know how to link to it, the problem was with upgrading to 5.11 as in the original description?10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0CommentsRe: [Res]script folder in soapUI project conflicts with 5.1.1
Sorry, we cannot update to 5.11 yet either, because of other issues (the random chars being added to the filenames) :| .... Anyway, we worked around this by refactoring our project, so it is no longer an issue for us and why we did not log an actual support ticket. I just figured I'd report it on the forums, for someone to take a look at. Or in case someone else runs into it. Cheers, Ton10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0CommentsRe: [Res]script folder in soapUI project conflicts with 5.1.1
SmartBear Support wrote: Hello, Thats interesting, can you please share your original project with me so that I can take a further look into this issue. Thanks. Regards, Temil I am afraid I cannot - there is way too much potentially sensitive information in our test project (urls, test data, etc)... I assume you have tried creating a 4.6 composite project with a test suite or two, adding a 'scripts' folder in it (with a random groovy script file) and then converting the project by opening it in 5.1.1 and were unable to replicate the problem? Ton10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0Comments[Res]script folder in soapUI project conflicts with 5.1.1
Another issue we ran into when upgrading from 4.6 to 5.1.1 - after the automatic conversion of our (composite) project, we noticed our custom script folder did not get copied to the new project. After I copied it manually, 5.1.1 seems to think once again that this is an old style project and needs to be converted... Ad nauseam ( project_new, then project_new_new etc). We had to do some refactoring and move the scripts folder out of the project folder... Is this expected? Regards, Ton10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes6CommentsFile and folder names get random characters in 5.1.1?
Hi there, I did a quick scan of the forums and can't see any reference to this specifically (other than that Windows users appear to be running into max file name issues when upgrading?). I logged a support case, but figure it might make sense to put it on the forum in case I'm missing the obvious. We are trying to upgrade from 4.6 to 5.1.1 - and are aware the (composite) project needs to be converted. We can work around this, however in 5.1.1 it seems all the test suite and test file names get a bunch of random characters attached to them... Which is causing havoc with out source control system. Fortunately we are on Mac machines, I see Windows users are running into max filename size issues... Sample: this testsuite used to be "190---Issues" now it is on the filesystem: 190---Issues-4a463548-9ed0-41c0-a931-eae76387e855 1) Is this expected or a bug of some sort? 2) Is there any way this can be turned off to the old behaviour? 3) If this is expected and cannot be changed - can we at least be guaranteed that these seemingly random strings are consistent? Ie - if a colleague grabs the project and save it, the file and folder names will be the same? Regards, Ton10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes2Comments