Issue 749:  Issue with ObjectId_to_string and string_to_ObjectId (orb_revision)
Source:  (, )
Nature:  Uncategorized Issue
Severity:  Minor
Summary: Summary: Section 18.4 "illegal characters": It should be clarified what corresponds to the concept of "illegal characters". On the othe hand, do we want to specify that ObjectIds generated by the POA should not include those "illegal characters?

Resolution: 
Revised Text: 
Actions taken:
October 6, 1997: received issue
June 8, 1999: moved from C++ to Core RTF
October 30, 2000: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <jhierro@ovdm36.cnd.hp.com>
Date: Mon, 6 Oct 1997 11:44:06 -0600
From: Juan Hierro <jhierro@ovdm36.cnd.hp.com>
Subject: Yet another three issues (the lasts, I promise !)
To: juergen@omg.org
Cc: jhierro@ovdm36.cnd.hp.com
Content-Md5: k1zAVq2huoVvGDsUtg6OHQ==

C++ Mapping issues:
===================

Title:

  Issue with ObjectId_to_string and string_to_ObjectId
  
Description:

  In section 18.4 of the C++ Server side mapping, it has been
  specified that "If conversion of an ObjectId to a string
  would result in illegal characters in the string (such as
  a NUL) the first two functions throw the CORBA::BAD_PARAM
  exception."
  
  First of all, it should be clarified what corresponds to
  the concept of 'illegal characters'.  That should be better
  specified.
  
  On the other hand ... Do we want to specify that ObjectIds
  generated by the POA shouldn't include those 'illegal 
  characters' ?  Otherwise, we couldn't use this auxiliar
  functions with them ...
  
  Another alternative is to allow that this two operations
  work for any ObjectId value and specify how to 'illegal
  characters' are mapped into strings ...