Issue 4805: Java mapping changes for core issue 4337 (java-rtf)
Source: Oracle (Mr. Ken Cavanaugh, nobody)
Nature: Uncategorized Issue
Severity: 
Summary: The recent passage of issue 4337 in the core RTF creates a need to update the Java
mapping to include support for the _repository_id operation.  Here is the proposed 
set of updates to the latest (unofficial) Java mapping specifiction (ptc/02-01-01):

--------------------------------------------------------------

In section 1.19.11, add the following method to Object after _get_interface_def:

	string _repository_id() ;
	
In section 1.20.2.1, add the following method to LocalObject after _get_interface_def
(this is the local interface part, I am assumming here that local interfaces
support repository_id.  If not, this should just throw a NO_IMPLEMENT exception):

	public String _repository_id() {
		String[] ids = _ids() ;
		return ids[0] ;
	}
	
In section 1.20.2.2, add the following method to Servant after _get_interface_def:

	public String _repository_id() {
		return _get_delegate().repository_id(this) ;
	}
	
Also in section 1.20.2.2, add the following paragraph after the section
on _get_interface:

	_repository_id
	
	Servant provides a default implementation of _repository_id() that
	can be overridden by derived servants if the default behavior is
	not adequate.  As defined in the CORBA 3.0 specification, 
	section 11.3.1, the default behavior of _repository_id is to 
	return the most derived interface of a static servant or the
	most derived interface retrieved from a dynamic servant.
	This behavior shall be supported by the Delegate that implements
	the servant.
	
In section 1.21.6.3, add the following method to ObjectImpl after _get_interface_def():

	public String _repository_id() {
		return _get_delegate().repository_id(this) ;
	}
	
In section 1.21.7, add the following method to Delegate after get_interface_def:

	public abstract String repository_id( 
	    org.omg.CORBA.Object self) ;
	    
In section 1.21.8, add the following method to Delegate after get_interface_def:

	String repository_id( Servant self ) ;
Resolution: Incorporate changes and close issue
Revised Text: 
Actions taken:
January 14, 2002: received issue
December 11, 2002: closed issue
Discussion: 

End of Annotations:=====
Date: Mon, 14 Jan 2002 15:06:24 -0800 (PST)
From: Ken Cavanaugh <Ken.Cavanaugh@sun.com>
Reply-To: Ken Cavanaugh <Ken.Cavanaugh@sun.com>
Subject: New issue for Java RTF: Java mapping changes for core issue
4337
To: issues@omg.org
Cc: ken.cavanaugh@sun.com, java-rtf@omg.org
MIME-Version: 1.0
Content-MD5: w5KfIQnw8bEC2tZUCH4B0A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
Content-Type: TEXT/plain; charset=us-ascii
X-UIDL: bm0!!+72!!^@Fe9`l*e9

The recent passage of issue 4337 in the core RTF creates a need to
update the Java
mapping to include support for the _repository_id operation.  Here is
the proposed 
set of updates to the latest (unofficial) Java mapping specifiction
(ptc/02-01-01):

--------------------------------------------------------------

In section 1.19.11, add the following method to Object after
_get_interface_def:

	string _repository_id() ;
	
In section 1.20.2.1, add the following method to LocalObject after
_get_interface_def
(this is the local interface part, I am assumming here that local
interfaces
support repository_id.  If not, this should just throw a NO_IMPLEMENT
exception):

	public String _repository_id() {
	       String[] ids = _ids() ;
			return ids[0] ;
			}
			
In section 1.20.2.2, add the following method to Servant after
_get_interface_def:

	public String _repository_id() {
	       return _get_delegate().repository_id(this) ;
	       }
	       
Also in section 1.20.2.2, add the following paragraph after the
section
on _get_interface:

   _repository_id
   
   Servant provides a default implementation of _repository_id() that
   can be overridden by derived servants if the default behavior is
   not adequate.  As defined in the CORBA 3.0 specification, 
   section 11.3.1, the default behavior of _repository_id is to 
   return the most derived interface of a static servant or the
   most derived interface retrieved from a dynamic servant.
   This behavior shall be supported by the Delegate that implements
   the servant.
   
In section 1.21.6.3, add the following method to ObjectImpl after
_get_interface_def():

	public String _repository_id() {
	       return _get_delegate().repository_id(this) ;
	       }
	       
In section 1.21.7, add the following method to Delegate after
get_interface_def:

	public abstract String repository_id( 
	    org.omg.CORBA.Object self) ;
	        
In section 1.21.8, add the following method to Delegate after
get_interface_def:

	String repository_id( Servant self ) ;
	
Ken.


Date: Fri, 26 Apr 2002 13:51:42 -0700 (PDT) 
From: Ken Cavanaugh <Ken.Cavanaugh@Sun.COM> 
Reply-To: Ken Cavanaugh <Ken.Cavanaugh@Sun.COM> 
Subject: issue 4805 -- Java RTF issue 
To: java-rtf@omg.org 
Cc: ken.cavanaugh@Sun.COM 
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 


Issue 4337 passed in the last core RTF in vote 10, subject to the
availability
of C++ and Java mapping changes.  The Java changes are issue 4805.
Here is the proposal I sent a while back, as updates to ptc/02-01-22:


--------------------------------------------------------------


In section 1.19.11, add the following method to Object after 
_get_interface_def:


        string _repository_id() ;
        
In section 1.20.2.1, add the following method to LocalObject after 
_get_interface_def:


        public String _repository_id() {
                String[] ids = _ids() ;
                return ids[0] ;
        }
        
In section 1.20.2.2, add the following method to Servant after 
_get_interface_def:


        public String _repository_id() {
                return _get_delegate().repository_id(this) ;
        }
        
Also in section 1.20.2.2, add the following paragraph after the
section
on _get_interface:


        _repository_id
        
        Servant provides a default implementation of _repository_id()
        that
        can be overridden by derived servants if the default behavior
        is
        not adequate.  As defined in the CORBA 3.0 specification,
        section 11.3.1, the default behavior of _repository_id is to
        return the most derived interface of a static servant or the
        most derived interface retrieved from a dynamic servant.
        This behavior shall be supported by the Delegate that
        implements
        the servant.
        
In section 1.21.6.3, add the following method to ObjectImpl after 
_get_interface_def():


        public String _repository_id() {
                return _get_delegate().repository_id(this) ;
        }
        
In section 1.21.7, add the following method to Delegate after 
get_interface_def:


        public abstract String repository_id(
            org.omg.CORBA.Object self) ;
        
In section 1.21.8, add the following method to Delegate after 
get_interface_def:


        String repository_id( Servant self ) ;


--------------------------------------------------------


This will appear in Vote 1 on 4/29.


Ken.

Date: Tue, 30 Apr 2002 08:23:07 -0700 (PDT) 
From: Ken Cavanaugh <Ken.Cavanaugh@Sun.COM> 
Reply-To: Ken Cavanaugh <Ken.Cavanaugh@Sun.COM> 
Subject: Re: Vote 1 in the current RTF 
To: jishnu_mukerji@hp.com 
Cc: java-rtf@omg.org 
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 



>From: Jishnu Mukerji <jishnu_mukerji@hp.com>
>X-Accept-Language: en
>MIME-Version: 1.0
>To: Ken Cavanaugh <Ken.Cavanaugh@sun.com>, java-rtf@omg.org
>Subject: Re: Vote 1 in the current RTF
>Content-Transfer-Encoding: 7bit
>
>Meant to vote YES on all issues. BTW, could you friendly amend the
>resolution for 4805 to say that it takes effect subject to the
>corresponding issue being recommended by the Core RTF? 


I'm happy to take this suggestion as a friendly amendment.  To be
precise, add the following paragraph of discussion to the proposed
resolution for issue 4805:


"Issue 4805 is based on the previous resolution for core issue 4337
which was passed subject to the adoption of appropriate changes in 
the C++ and Java language mappings.  Adopting the proposed resolution
to
issue 4805 means that the resolution is in affect after successful
re-consideration of issue 4337 in the core RTF."


Is there an issue in place for C++?  Is anyone working on it?


Ken.