diff options
| author | frehberger <frehberger@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 2006-03-29 06:26:35 +0000 |
|---|---|---|
| committer | frehberger <frehberger@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 2006-03-29 06:26:35 +0000 |
| commit | efef0e599c98ce8f02194b8b4a7f4a50a2d176a3 (patch) | |
| tree | df940e25a0a4cb8300316ad185a91ffb0395b5ed /TAO/tao/GIOP_Message_Generator_Parser.cpp | |
| parent | be40195a7eedc4e0f2e33886a5d71c8172143481 (diff) | |
| download | ATCD-efef0e599c98ce8f02194b8b4a7f4a50a2d176a3.tar.gz | |
ChangeLogTag: Tue Mar 28 23:59:00 UTC 2006 Frank Rehberger <frehberger@prismtech.com>
Diffstat (limited to 'TAO/tao/GIOP_Message_Generator_Parser.cpp')
| -rw-r--r-- | TAO/tao/GIOP_Message_Generator_Parser.cpp | 17 |
1 files changed, 7 insertions, 10 deletions
diff --git a/TAO/tao/GIOP_Message_Generator_Parser.cpp b/TAO/tao/GIOP_Message_Generator_Parser.cpp index 63db40953b9..abd302b491e 100644 --- a/TAO/tao/GIOP_Message_Generator_Parser.cpp +++ b/TAO/tao/GIOP_Message_Generator_Parser.cpp @@ -37,9 +37,8 @@ TAO_GIOP_Message_Generator_Parser::parse_reply ( } // and the reply status type. status can be NO_EXCEPTION, - // SYSTEM_EXCEPTION, USER_EXCEPTION, LOCATION_FORWARD - - // Cannot handle LOCATION_FORWARD_PERM here + // SYSTEM_EXCEPTION, USER_EXCEPTION, LOCATION_FORWARD, + // LOCATION_FORWARD_PERM CORBA::ULong rep_stat = 0; if (!stream.read_ulong (rep_stat)) { @@ -76,13 +75,12 @@ TAO_GIOP_Message_Generator_Parser::parse_reply ( TAO_PLUGGABLE_MESSAGE_LOCATION_FORWARD; break; // Reply is a location forward perm type - // @@For the time being the behaviour of the - // LOCATION_FORWARD_PERM would be similar to the - // LOCATION_FORWARD as there is a controversy surrounding the - // usage of this in the OMG. + // LOCATION_FORWARD_PERM is only allowed in context of + // FaultTolerant featured requests and requires PortableGroup + // features in forwarded object and service context case TAO_GIOP_LOCATION_FORWARD_PERM: params.reply_status_ = - TAO_PLUGGABLE_MESSAGE_LOCATION_FORWARD; + TAO_PLUGGABLE_MESSAGE_LOCATION_FORWARD_PERM; break; // Reply is a location forward type case TAO_GIOP_NEEDS_ADDRESSING_MODE: @@ -117,8 +115,7 @@ TAO_GIOP_Message_Generator_Parser::parse_locate_reply ( // and the reply status type. status can be NO_EXCEPTION, // SYSTEM_EXCEPTION, USER_EXCEPTION, LOCATION_FORWARD - - // Cannot handle LOCATION_FORWARD_PERM here + // LOCATION_FORWARD_PERM // Please note here that we are NOT converting to the Pluggable // messaging layer exception as this is GIOP specific. Not many |