Debz
Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Property transfer step failed when run through Maven
Hi, I am a bit confused with the details you provided. It's posted in the Open Source forums but the declaration on the POM file is showing SoapUI Pro 4.6. If it's really open source and you just copied that XML and modified it for your variables, you might be missing some plugin declarations to make it work since the versions there seem to be a bit old. You might want to consider doing a backup and upgrading to 5.3.0. Anyway, it's free. They have already made a lot of fixes on that version to make life easier. If you still want to proceed with that version, you might need the following: the plugin for Maven 2. Maven is now on version 3 though. I think they have already stopped support for 2...just a wild guess why the transfer is failing on your end only when Maven is run...so you'll be needing the items listed below. redfish4ktc2's plugin. He did some great work for some issues. the compiler plugin...but you already have Java 1.8 so, just check the details there if it's still necessary since you have the latest one. We are working on an older version on our end so we are using this one. Goodluck!Re: how to share session id to other request
Hi, I suppose session ID = token. Create a property for the session ID under the Project level. Use groovy test step to process it if your session ID comes as part of a response data and store it to the Project Property. Ex. trim the part you need. You may refer to the code sample I have here. In the Headers tab of the test case, click the + icon for "Add a custom HTTP header to this session". Specify the name of your session ID variable. For the value on the right side, instead of writing or hardcoding the whole token, call the project property. Ex. Header: myToken Value: ${#Project#cleanedToken} 6. Sessions usually expire after a period of time, I would suggest you select the test case on the navigator tree on the left side of SoapUI, right-click and select Options. When Test Case options pops-up make sure Basic tab is selected and check Session: Maintain HTTP session to avoid timeout. Regards, DebzRe: How to connect Phoenix DB with SOAP UI tool
Hi, try adding one via File > Preferences > JDBC Driver > + You will be asked to provide a name for it, then add the connection string (username, pasword, hostname, port, sid, etc) which should be available here. It seems that the jar should be "packaged" along with the installer. They have a repo but I can't confirm at the moment because that's 266 MB for the bin folder alone. Maybe other guys who have worked with Phoenix can share a direct download for the version you need.
