Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD

com.ibm.etools.iseries.subsystems.qsys.objects
Class RemoteObjectContext

java.lang.Object
  extended by com.ibm.etools.iseries.subsystems.qsys.objects.RemoteObjectContext
All Implemented Interfaces:
IRemoteObjectContext
public class RemoteObjectContext
extends Object
implements IRemoteObjectContext

Context provider for QSYS based objects, members, procedures, fields, etc...

Field Summary
static String copyright
           
 
Constructor Summary
RemoteObjectContext(QSYSObjectSubSystem subsystem)
           
 
Method Summary
 QSYSObjectSubSystem getObjectSubsystem()
          Get the Object subsystem (which in turn provides access to the IHost
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static String copyright
Constructor Detail

RemoteObjectContext

public RemoteObjectContext(QSYSObjectSubSystem subsystem)
Method Detail

getObjectSubsystem

public QSYSObjectSubSystem getObjectSubsystem()
Description copied from interface: IRemoteObjectContext
Get the Object subsystem (which in turn provides access to the IHost

Specified by:
getObjectSubsystem in interface IRemoteObjectContext
Overview  Package   Class  Tree  Serialized  Deprecated  Index  Help 
Rational Developer for Power Systems Software
V7.6
 PREV CLASS   NEXT CLASS FRAMES    NO FRAMES    
SUMMARY: NESTED | FIELD | CONSTR | METHOD DETAIL: FIELD | CONSTR | METHOD
Copyright © 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.