|submissionset.uniqueId generation problem [message #582922]
||Thu, 08 November 2007 22:12
| Jesse Pangburn
Registered: July 2009
I ran into a funny problem with the submission set's unique id generation.
I passed "184.108.40.206.4.1.118220.127.116.117.11.08.12.15.36.2" as the
submission set's sourceId, and the bridge generated
" 18.104.22.168.4.1.11822.214.171.124126.96.36.199.188.8.131.5201602901714 6133.1194552938546.1 "
as the XDSSubmissionSet.uniqueId. This is evidenced by the following
snippet of the log entry's printout of the message transmitted:
value=" 184.108.40.206.4.1.118220.127.116.1118.104.22.168.22.214.171.12405701300202 3108.1194558984650.1 "><rim:Name><rim:LocalizedString
Unfortunately, the repository complained about the length of uniqueId in
this snippet from the response:
Schema Validation Errors:
Input did not validate against
Error: cvc-maxLength-valid: Value
with length = '80' is not facet-valid with respect to maxLength '64' for
I just did a quick count of my characters and there are about 45. The
unique id generation brings the count to 80, so it adds about 35
characters. If this is typical, it means that the bridge user cannot pass
an OID for the submission set sourceId that is longer than about 29
characters. In my case, the fixed part of the OID is
"126.96.36.199.4.1.11854.1.100." (my IHE testing OID) which is 24 characters-
leaving me only 5 characters to generate all my OIDs for IHE testing.
I don't really know what the technical difference is between the sourceId
and the uniqueId, but does the uniqueId need to be that much longer? Can
it just be the same?
Powered by FUDForum
. Page generated in 0.01837 seconds