Bug 38 - Is the TAO_Unknown_Profile class working correctly?
Summary: Is the TAO_Unknown_Profile class working correctly?
Status: RESOLVED FIXED
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 1.0.3
Hardware: All All
: P2 normal
Assignee: Ossama Othman
URL:
Depends on:
Blocks: 294
  Show dependency tree
 
Reported: 1999-07-08 12:48 CDT by Carlos O'Ryan
Modified: 1999-11-12 15:57 CST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos O'Ryan 1999-07-08 12:48:38 CDT 
There are several reports that passing IORs from platforms with UIOP to
platforms without UIOP support gives problems, specially to obtain the initial
Naming Service IOR.
The error message reported is:

	TAO (136|46) could not create all the profiles
	(136|46) Unable to get the Naming Service.
Comment 1 Ossama Othman 1999-07-08 18:16:59 CDT 
Accepted.
Comment 2 Ossama Othman 1999-08-22 11:30:59 CDT 
TAO_Unknown_Profile appears to be working but I'd like to run some stress tests
before I resolve this bug.
Comment 3 Ossama Othman 1999-09-03 09:58:59 CDT 
There have been reports of interoperability problems between TAO and other ORBs.
This bug may be related to the problem.
Comment 4 Ossama Othman 1999-11-12 15:57:59 CST 
I just ran what should be definitive test.  I bound a the reference of an UIOP
object (on Linux) to a Name Service running on an NT host.  Then I resolved the
reference stored in that Name Service on the Linux box, and then did an
object_to_string on that resolved object.  The stringified IOR was printed in
URL format.  The endpoint in that IOR was the same as the endpoint the UIOP
server was running on.  I think this proves that TAO_Unknown_Profile is working
properly.