skillsoft
15 years agoFrequent Contributor
East Asian characters and property expansions in jdbc connection
Hi
According to the topic below, east asian languages will only be displayed correctly in SoapUI if you are using the Native Look and Feel. I tried this and it works, but was wondering why? If I don't use the native look and feel all I see is squares where the characters should be.
http://www.eviware.com/forums/index.php?topic=407.0
Also, property expansions can be used in any field of the JDBC Connection at the project level except for the password. If I attempt to do this I will get:
TestCase failed [java.lang.Exception: Failed to prepare testStep [getidcompanylevel]; java.lang.IllegalArgumentException: Illegal group reference:java.lang.Exception: Failed to prepare testStep [getidcompanylevel]; java.lang.IllegalArgumentException: Illegal group reference], time taken = 0
Is there any way around this? It would be nice to have all the settings that are server specific in one place (project/properties). For the most part the db password is the same, but for some of our older software versions it is different.
Thanks,
Mary
According to the topic below, east asian languages will only be displayed correctly in SoapUI if you are using the Native Look and Feel. I tried this and it works, but was wondering why? If I don't use the native look and feel all I see is squares where the characters should be.
http://www.eviware.com/forums/index.php?topic=407.0
Also, property expansions can be used in any field of the JDBC Connection at the project level except for the password. If I attempt to do this I will get:
TestCase failed [java.lang.Exception: Failed to prepare testStep [getidcompanylevel]; java.lang.IllegalArgumentException: Illegal group reference:java.lang.Exception: Failed to prepare testStep [getidcompanylevel]; java.lang.IllegalArgumentException: Illegal group reference], time taken = 0
Is there any way around this? It would be nice to have all the settings that are server specific in one place (project/properties). For the most part the db password is the same, but for some of our older software versions it is different.
Thanks,
Mary