| java.lang.Object org.netbeans.modules.web.monitor.client.Controller
Controller | class Controller (Code) | | |
Inner Class :class ServerCheck implements Runnable | |
Inner Class :class CompAlpha implements Comparator | |
debug | final static boolean debug(Code) | | |
addTransaction | void addTransaction(String id)(Code) | | Adds a transaction to the list of current transactions.
|
checkServer | boolean checkServer(boolean replay)(Code) | | |
deleteTransaction | void deleteTransaction(Node[] nodes)(Code) | | Invoked by DeleteAction. Deletes a saved transaction
|
deleteTransactions | void deleteTransactions()(Code) | | |
getDataRecord | DataRecord getDataRecord(AbstractNode node)(Code) | | Parameters: node - A node on the Monitor GUI a data recordConvenience method - this gets the DataRecord corresponding toa node on the TransactionView panel from the cache if it ispresent. This is used to display the data from the node. |
getDataRecord | DataRecord getDataRecord(AbstractNode anode, boolean fromCache)(Code) | | Parameters: node - A node on the Monitor GUI Parameters: fromCache - true if it is OK to get the data record fromthe cache a data record |
getMonitorData | MonitorData getMonitorData(TransactionNode node, boolean fromCache, boolean cacheIt)(Code) | | Parameters: node - A node on the Monitor GUI Parameters: fromCache - true if it is OK to get the data record fromthe cache Parameters: cacheIt - true if it is OK to cache the data that weretrieve a data record, null if monitor date could not be got |
getRoot | protected NavigateNode getRoot()(Code) | | Adds a transaction to the list of current transactions.
|
getTransactions | void getTransactions()(Code) | | |
getUseBrowserCookie | boolean getUseBrowserCookie()(Code) | | |
haveDirectories | boolean haveDirectories()(Code) | | |
replayTransaction | void replayTransaction(Node node)(Code) | | Invoked by ReplayAction. Replays the transaction corresponding to
the selected node.
PENDING - it would be better if the nodes know which server
they were processed on. This would be the case if we listed the
nodes separately depending on the server that collected the
data.
|
retrieveMonitorData | MonitorData retrieveMonitorData(String id, String dirS)(Code) | | Parameters: id - The ID of the record Parameters: dirS - The name of the directory in which the transactionresides |
retrieveMonitorData | MonitorData retrieveMonitorData(String id, FileObject dir)(Code) | | Parameters: id - The ID of the record. Parameters: dir - The directory in which the transaction resides. monitor date, null if monitor date could not be retrieved. |
saveTransaction | void saveTransaction(Node[] nodes)(Code) | | |
setServer | static void setServer(String loc, int p)(Code) | | Sets the machine name and port of the web server. Not used in
this version, we do not support remote debugging.
|
setUseBrowserCookie | void setUseBrowserCookie(boolean value)(Code) | | This method toggles whether the request uses the browser's
cookie or a cookie specified by the user. In 3.6, it is not
possible to configure the monitor to use user-specified
cookies, but I leave the method, in case it becomes possible in
the future. Basically, we can no longer set the cookie on the
server side (the Servlet APIs does not provide any method for
doing this) but we could technically tell the browser that
issues the replay request to send another cookie (the APIs for
that are not there now). If so, the feature can be
reintroduced.
|
updateNodeNames | void updateNodeNames()(Code) | | |
|
|