Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.remotebuild.util
Class QSYSObjectName

java.lang.Object
  extended by com.ibm.etools.iseries.remotebuild.util.QSYSObjectName

public class QSYSObjectName
extends Object

A QSYSObjectName allows for the presentation and extraction of the various pieces of an object name in its QSYS format -- object, library/object, or library/file(member). It does not have any validation, but does respect quoted names.


Constructor Summary
QSYSObjectName(String objectName)
           
 
Method Summary
 String getLibrary()
           
 String getMember()
           
 String getObject()
           
 boolean isMember()
           
 void setLibrary(String string)
           
 void setMember(String string)
           
 void setObject(String string)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

QSYSObjectName

public QSYSObjectName(String objectName)
Method Detail

isMember

public boolean isMember()

getLibrary

public String getLibrary()
Returns:
the library name, null if the name has not been set, or the name is not library qualified.

getMember

public String getMember()
Returns:
the member name, null if the object name does not identify a file member.

getObject

public String getObject()
Returns:
the object name.

setLibrary

public void setLibrary(String string)
Parameters:
string - the library name of the object.

setMember

public void setMember(String string)
Parameters:
string - the member name of the file member, if this name identiifies a file member.

setObject

public void setObject(String string)
Parameters:
string - the object name.

Rational Developer for Power Systems Software
V7.6

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.