| Home >> All >> junk >> [ system Javadoc ] |
| • | junk.system.io.* (4) | • | junk.system.jvm.* (3) |
• junk.system: Javadoc index of package junk.system.
Package Samples:
• junk.system.io
• junk.system.jvm
Classes:
• JXProcess: JXProcess is design to allow native programs to be executed within the JD4X environment. Each created JXProcess can be tracked and administered to by JUNK. The JXProcess uses a Java thread to wrap around each native process execution that was requested. JXProcess does not work well with scripts of any form and therefore scripts should not be used in a JXProcess. According to Sun's Java, a native process is executed outside the JVM's control and security, therefore the use of JXProcess is recommended to be kept to the minimum. The execution path of a JXProcess actually jumps outside of the Java ...
• JXJvm: JXJvm is an abstract representation of a Java Virtual Machine running on a Linux process. It will provide all the JVM and class management features offered by Junk. In order to enhance the interaction between the desktop clients and the often neglected JVM, Junk provides a GUI interface to the features that the JXJvm offers. These features will allow multiple classes to be loaded into the JXJvm's runtime domain such that each JVM can host multiple programs using separate classloaders. Some basic JVM administration features will also be provided for the clients so that they can directly manipulate ...
• JXClassLoader: JXCLassLoader provides the capability to load classes into the current JVM runtime. This is a basic implementation of a network class loader. The boot strip class loader is not over written because over writing it will introduce security problems. The client should ensure that each Java application program is only loaded into 1 JXClassLoader for reasons regarding security and JVM guideline compliance. This implementation of the class loading mechanism is used system wide by all JXJvms. Note: findClass(...) is reserved for the JVM to do dynamic loading and it should not be directly called by a client ...
• JXThread: JXThread is design to allow for a parallel execution environment. Each created JXThread can be tracked and administered to by JUNK. JUNK uses the JXThread to dedicate each task that was requested by a client into a separate execution path such that parallel computation is achievable. It will also reduce the possibility of a performance bottle neck situation in JUNK. A JD4X thread is defined by a valid module and a valid task request to that module. If both the module and the task is valid than useful work can be done else the state of the thread is considered to be invalid and no useful work can ...
• JXClassLoaderManager: JXClassLoaderManager provides classloader management for the JXJvm. It allows the selection of all existing classloaders under its management. All the classes loaded into any of its classloaders can also be invoked to create an instance of that class. Reflection facilities are also available to retrieve a break down of the individual class instances.
• JXSystem: JXSystem is the boot class of the entire JD4X system. It takes care of the command line options and passes them to JUNK. If no options are passed, it starts JUNK with the default settings. It also handles request for reboot or termination of the current desktop session Possible options are: None yet.
• JXRedirectPipe: JXRedirectPipe provides a customized print stream to redirect any pipes, so that they can be redirected to client defined output streams. It is mainly used to redirect standard system output streams to the desired client's GUI.
• JXTerminal: JXTerminal provides a panel for invoking system components to sent messages to. It can be used for informing clients about the JVM as well as trouble shooting of system components. It is designed to be as simple as possible.
• JXRedirectService: JXRedirectService is used to define the JXTerminal. It defines the client's redirected pipe streams to their own GUI screen. It is used mainly to implement text terminals.
• JXIOInterface: JXIOInterface is design to reduce the coupling between the IO terminal display and it direct access by Junk.
| Home | Contact Us | Privacy Policy | Terms of Service |