JacORB IOR not understood by ORBit



Hi. I got an IOR from a friend that was generated using JacORB 1.2.2 and
it is recognized by my ORBit Client.
These are the results of the IOR parsing done at:
http://www.parc.xerox.com/istl/projects/ILU/parseIOR/

I cannot find any differences between them but I'm some eexpert out
there probably knows what's going on.


NOT WORKING in ORBit:

IOR:000000000000000d49444c3a4563686f3a312e3000000000000000030000000000000031000100000000000c3137322e31362e322e3831000411000000000015343938393234393133392f00101016064220004c1e000000000000000000005c000101000000000c3137322e31362e322e3831000411000000000015343938393234393133392f00101016064220004c1e00000000000001000000010000001c0000000005010001000000010001000100010109000000010501000100000001000000080000000000000000



_IIOP_ParseCDR:  byte order BigEndian, repository id <IDL:Echo:1.0>, 3
profiles
_IIOP_ParseCDR:  profile 1 is 49 bytes, tag 0 (INTERNET), BigEndian byte
order
_IIOP_ParseCDR:  profile 2 is 92 bytes, tag 0 (INTERNET), BigEndian byte
order
_IIOP_ParseCDR:  profile 3 is 8 bytes, tag 1 (MULTIPLE COMPONENT),
BigEndian byte order
(iiop.c:parse_IIOP_Profile):  bo=BigEndian, version=1.0,
hostname=172.16.2.81, port=1041, object_key=<4989249139/.....B .L.>
(iiop.c:parse_IIOP_Profile):  encoded object key is
<4989249139%2F%00%10%10%16%06B%20%00L%1E>
(iiop.c:parse_IIOP_Profile):  non-native cinfo is
<iiop_1_0_1_4989249139%252F%2500%2510%2510%2516%2506B%2520%2500L%251E tcp_172 16 2 81_1041>

(iiop.c:parse_IIOP_Profile):  bo=BigEndian, version=1.1,
hostname=172.16.2.81, port=1041, object_key=<4989249139/.....B .L.>
(iiop.c:parse_IIOP_Profile):  encoded object key is
<4989249139%2F%00%10%10%16%06B%20%00L%1E>
(iiop.c:parse_IIOP_Profile):  non-native cinfo is
<iiop_1_1_1_4989249139%252F%2500%2510%2510%2516%2506B%2520%2500L%251E tcp_172 16 2 81_1041>

(iiop.c:parse_MultiComponent_Profile):  profile contains 0 components
object key is <4989249139/#00#10#10#16#06B #00L#1E>;
 no trustworthy most-specific-type info; unrecognized ORB;
 reachable with IIOP 1.1 at host "172.16.2.81", port 1041



WORKING in ORBit:

IOR:000000000000001c49444c3a5173496e666f2f5173496e666f5365727665723a312e3000000000030000000000000032000100000000000e31302e3231312e3134372e32350004c600000016333333373431343435312f001010154b4a3e2801290f00000000000000000038000101000000000e31302e3231312e3134372e32350004c600000016333333373431343435312f001010154b4a3e2801290f00000000000000000001000000080000000000000000

_IIOP_ParseCDR:  byte order BigEndian, repository id
<IDL:QsInfo/QsInfoServer:1.0>, 3 profiles
_IIOP_ParseCDR:  profile 1 is 50 bytes, tag 0 (INTERNET), BigEndian byte
order
_IIOP_ParseCDR:  profile 2 is 56 bytes, tag 0 (INTERNET), BigEndian byte
order
_IIOP_ParseCDR:  profile 3 is 8 bytes, tag 1 (MULTIPLE COMPONENT),
BigEndian byte order
(iiop.c:parse_IIOP_Profile):  bo=BigEndian, version=1.0,
hostname=10.211.147.25, port=1222, object_key=<3337414451/....KJ>(.).>
(iiop.c:parse_IIOP_Profile):  encoded object key is
<3337414451%2F%00%10%10%15KJ%3E%28%01%29%0F>
(iiop.c:parse_IIOP_Profile):  non-native cinfo is
<iiop_1_0_1_3337414451%252F%2500%2510%2510%2515KJ%253E%2528%2501%2529%250F tcp_10 211 147 25_1222>

(iiop.c:parse_IIOP_Profile):  bo=BigEndian, version=1.1,
hostname=10.211.147.25, port=1222, object_key=<3337414451/....KJ>(.).>
(iiop.c:parse_IIOP_Profile):  encoded object key is
<3337414451%2F%00%10%10%15KJ%3E%28%01%29%0F>
(iiop.c:parse_IIOP_Profile):  non-native cinfo is
<iiop_1_1_1_3337414451%252F%2500%2510%2510%2515KJ%253E%2528%2501%2529%250F tcp_10 211 147 25_1222>

(iiop.c:parse_MultiComponent_Profile):  profile contains 0 components
object key is <3337414451/#00#10#10#15KJ>(#01)#0F>;
 no trustworthy most-specific-type info; unrecognized ORB;
 reachable with IIOP 1.1 at host "10.211.147.25", port 1222









[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]