Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.edit.xmllite
Class XmlLiteException

java.lang.Object
  extended by java.lang.Throwable
      extended by java.lang.Exception
          extended by com.ibm.etools.iseries.edit.xmllite.XmlLiteException
All Implemented Interfaces:
Serializable

public class XmlLiteException
extends Exception

See Also:
Serialized Form

Field Summary
 int _iColumnNumber
           
 int _iLineNumber
           
 String _strFilename
           
 String _strLine
           
 String _strMessage
           
static String copyright
           
 
Constructor Summary
XmlLiteException(String strMessage, String strFilename, String strLine, int iLineNumber, int iColumnNumber)
           
 
Method Summary
 
Methods inherited from class java.lang.Throwable
fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values

_strMessage

public String _strMessage

_strFilename

public String _strFilename

_strLine

public String _strLine

_iLineNumber

public int _iLineNumber

_iColumnNumber

public int _iColumnNumber
Constructor Detail

XmlLiteException

public XmlLiteException(String strMessage,
                        String strFilename,
                        String strLine,
                        int iLineNumber,
                        int iColumnNumber)
Parameters:
strMessage - java.lang.String
strLine - java.lang.String
iLineNumber - int
iColumnNumber - int

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.