header
header
Main Menu
Home
Eviware Store
Downloads
Products
News
Forum
Eviware Blog
Search
FAQs
Customer Area
Support
Documentation
Tutorials
CookBook
Downloads
Forum
Login Form
Welcome, Guest. Please login or register.
November 22, 2008, 02:45:40 am
Username: Password:
Login with username, password and session length

Forgot your password?
 
Property Transfer XPath Bug
Welcome, Guest. Please login or register.
November 22, 2008, 02:45:40 am
Home Help Search Login Register
News: The Forums are up! Welcome to eviware.

+  Eviware Forum
|-+  General Category
| |-+  eviware general
| | |-+  Property Transfer XPath Bug
« previous next »
Pages: [1] Print
Author Topic: Property Transfer XPath Bug  (Read 985 times)
Miles
Newbie
*
Posts: 3


« on: July 14, 2008, 03:17:56 pm »

SoapUI Pro 2.0.2 property transfer is not operating as expected when using XPath statements, as follows.

Example XML:

<x><y1>aaa</y1><y2>bbb</y2><x>

With above XML in a previous test case step, I can use property transfer:

//x[1]

to pass value to another property, say.

But, the result now has some spaces added. Result is:

<x>   <y1>aaa</y1>   <y2>bbb</y2><x>

This has introduced unwanted spaces.

Problem is further compounded by XPath implementation used by SoapUI, which is sensitive to whitespace. That is, if the result is then transferred as above, with same XPath:

//x[1]

Result is just whitespace. Whenever there is whitespace between tags, XPath fails to return correct data.

Probably a bug. Any solution/workaround to this?

Cheers.

Miles.
Logged
omatzura
Administrator
Hero Member
*****
Posts: 1,425


« Reply #1 on: July 15, 2008, 08:04:24 am »

Hi Miles,

hm.. looks a bit like a bug to me.. is the xml part of a response message? Can you turn off pretty-printing to see if that makes a difference?

regards,

/Ole
eviware.com
Logged
Miles
Newbie
*
Posts: 3


« Reply #2 on: July 17, 2008, 11:36:37 am »

Hi Ole,

I tried switching off pretty print but to no avail.

Can you think of any other way around the issue?

Also, does SoapUI treat property values differently when using XML data as opposed to strings?

Miles
Logged
omatzura
Administrator
Hero Member
*****
Posts: 1,425


« Reply #3 on: July 17, 2008, 01:52:43 pm »

Hi Miles,

hmm.. I'll have to check this out in more detail.. soapUI shouldn't make any difference between properties containing xml or not.. sorry for the inconvenience..

regards,

/Ole
eviware.com
Logged
omatzura
Administrator
Hero Member
*****
Posts: 1,425


« Reply #4 on: August 04, 2008, 12:49:02 pm »

Hi,

thanks again, this was a bug that was pretty-printing the result of the property-transfer.. I've removed this for the next version..

regards!

/Ole
eviware.com
Logged
Pages: [1] Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
header header
header
header