When using a UDDI v3 registry the UDDI-Version should be set to '3.0'
---------------------------------------------------------------------
Key: SCOUT-128
URL: https://issues.apache.org/jira/browse/SCOUT-128
Project: Scout
Issue Type: Bug
Reporter: Kurt T Stam
Assignee: Kurt T Stam
Fix For: 1.2.6
In some tests the TCK connects directly to scout, not using the JNDI lookup. In
this case the UDDI version property is not set, and Scout defaults it to "2.0",
which leads to issues. The preferred way to solve this is to have the TCK set
this property, but this does seem that easy to do. To work around this issue we
check the juddi URL, and if thi contains 'v3' we automatically set the UDDI
version to "3.0" if it is not set.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
