java applications

JFrameBuilder is an easy-to-use visual Java GUI Builder for Java Swing applications.
It provides the application GUI solution for Java developers. The Java GUI designer enables Java developers to create sophisticated GUI applications using drag-and-drop interface without spending a lot of time writing code.

Features:
- What you see is truly what you get.
- Generates human readable Java code.
- Generated Java code doesnt require any additional library to compile and run.
- Retrieves GUI design from Java source code.
- Sets component properties and event handling methods with easy understandable interface.
- Supports 4 kinds of layout manager for the JPanel.
- Ability to set Look&Feel at any time.

JFrameBuilder supports these components:
JFrame, JInternalFrame, JDialog, JSplitPane, JScrollPane, JTabbedPane, JPanel, JSeparator, JProgressBar, JSlider, JSpinner, JTree, JTable, JList, JComboBox, JTextPane, JEditorPane, JTextArea, JPasswordField, JTextField, JLabel, JCheckBox, JRadioButton, JToggleButton, JButton.

Enterprise Java Application Server (EJAS) technology is a framework for developing and executing Distributed Applications. These Applications provide System - Level Services such as Transaction Management, Security, Client Connectivity and Database Access. Enterprise Java Beans provide a Component Model that will help you to build Business Application with your existing Databases, Applications, Systems, and Infrastructure Management. Enterprise Java Application Server (EJAS) offers you: Automatic Persistence (Database and File Access), Automatic Declarative Transaction Models, Client Authentication and Access Control at the Method Level, Resource Management for Threads, Network, and Database Connections, Bean Caching, Bean Life-Cycle Management for Creating, Finding, and Destroying Beans, Concurrency Control, External Configuration of Bean Runtime Properties, Dynamic Deployment of Beans in a Running Server. The Enterprise Java Application Server (EJAS) is "Container s Container" - it contains the EJB Container. This Server is responsible for providing the container with Lower-Level Services. EJAS Container: An EJAS Container is an environment in which Enterprise Java Beans executes. Its primary role is to serve as a buffer between an EJB and the outside world. Clients do not directly connect to the EJB Bean itself, rather, they connect to representation of the Bean provided by the Container, which then forwards the Clients requests to the Bean. The Container controls the Enterprise Beans and provides them with important Systems-Level Services. The Container provides the following services to Enterprise Bean: 1) Transaction Management. 2) Security. 3) Remote Client Connectivity. 4) Life Cycle Management. 5) Database Connection Pooling.

Java Application Monitor (JAMon) project is a free, simple, high performance, thread safe, Java API that allows developers to easily monitor production applications. JAMon can be used to determine application performance bottlenecks, user/application interactions, and application scalability.

JAMon gathers summary statistics such as hits, execution times (total, average, minimum, maximum, standard deviation), and simultaneous application requests. JAMon statistics are displayed in the clickable JAMon Report. Click JAMon report to see a live demo of JAMon.

JAMon was developed primarily for monitoring J2EE applications, however it can be used in any JDK 1.2 or higher environment. JAMon can be used in Servlets, JSPs, EJBs and Java Beans in various J2EE Application Servers (Sybases EAServer, and BEAs WebLogic, ), and can also be used in other programming environments that can call Java code (ColdFusion, PowerBuilder, BroadVision, ...).

Feel free to continue reading the users guide or download JAMon and read the Java Docs.

Using JAMon is easy. Place JAMon.jar (90K) in your classpath, and surround the code that you wish to monitor with the JAMon APIs start() and stop() methods. See the code sample below:

import com.jamonapi.*;
...
Monitor mon=MonitorFactory.start("myFirstMonitor");
...Code Being Timed...
mon.stop();

For example, to collect statistics for all JSP pages in a Web Application, a developer would place a call to the start() method at the top of every JSP, and a call to the stop() method at the bottom. With a few minutes work the developer will have statistics for all application pages. The statistics will include number of page hits, average page execution times, and the number of users simultaneously accessing each page. The statistics can be displayed as an HTML table by calling the getReport() method, or using JAMonAdmin.jsp.

JAMon requires no special administration accounts. Many monitoring tools require administrative accounts to install monitoring software, and to view statistics. Due to the complexity of these tools, developers typically go through specially trained administrators to access monitoring statistics. Many of these monitoring tools also require holes punched in firewalls.

JAMon has none of these problems. Statistics gathered via JAMon are available to all developers via JAMonAdmin.jsp. No administrative accounts, rights, or set-up are required for gathering and viewing statistics. Because the JAMon API is part of the application code, developers can switch J2EE App Servers and monitoring will continue to work. JAMonAdmin.jsp is accessed via HTTP and so can be viewed without punching any additional holes in firewalls.

JAMon can be used to monitor production systems. Monitoring production systems is important because it is the only way we can see the frequency that our code is being executed by real users. Also, many times the configuration of the production environment is different from the test environment, so the performance numbers between the two environments may be considerably different. For both these reasons monitoring only the test environment is not enough.

Unlike many monitoring tools, JAMon, due to its minimal performance overhead and multi-threaded capabilities, can be used in production systems. JAMon can be disabled at runtime (using JAMonAdmin.jsp), further reducing performance overhead. On a 2 Ghz Pentium IV, JAMons start(), and stop() methods execute 500,000 times per second. After disabling, the methods execute 30,000,000 times per second.

To test JAMons performance download JAMon.jar and execute the following command. The number represents how many times start(), and stop() should be called in the various tests (100,000 will be used as the default if a number is not provided).

java -cp JAMon.jar com.jamonapi.TestClassPerformance 500000

The last label ("Full Factory TimingMonitor()") in the output indicates how long it takes to run when monitoring is enabled, and the label starting with "NullMonitor2()" indicates how long it takes to run when monitoring is disabled.

JAMon is flexible. Many monitoring tools specialize in monitoring specific parts of an application. This can force a developer to resort to using multiple monitoring tools to cover all of their monitoring needs. For example, a developer may have to use different tools to monitor each of the following: page hits, EJB invocations, method calls and database connections,... .

JAMons start() method takes a string as an argument. This string can be a JSP page name, an EJB name, a method name or any other code or concept that can be represented by a string.

Also, because strings are passed to the start() method, a developer can decide what to monitor based on runtime data. Using this technique we can monitor trends as well as performance bottlenecks. Some examples of JAMons flexibility:

Keep statistics for a JSP home page
- Monitor mon=MonitorFactory.start("HomePage");
Keep statistics for a DataAccess classs openConnection() method (which opens a database connection)
- Monitor mon=MonitorFactory.start("DataAccess.openConnection()");
Keep statistics for each user that logs into our system
- Monitor mon=MonitorFactory.start(getUserName());
Keep statistics for all page accesses by date. For example, "pageAccesses.05/10/02"
- Monitor mon=MonitorFactory.start("pageAccesses."+getTodaysDate());

Whats New in This Release:

· This release adds a JAMon log4j Appender that will allow developers to keep aggregate statistics on log4j messages.
· For example, they will be able to use a JAMon Web page to view how many errors have been sent to log4j.
· They will also be able to tail the log4j log file via a JAMon Web page.
· All of this can be configured via the log4j XML or properties configurator.
· No code changes are required in your application.

Java Tools is a lightweight integrated development environment for creating, compiling, and executing Java applications and applets.

Java Tools includes point and click access to the Java files, commands, and documents. It also includes a built-in text editor and user interface for the Java debugger.

It is intended for the new Java user who needs help getting started. Its also for the more experienced Java user who wants easy access to the Java commands and a text editor.

Here are some key features of "Java Tools":

· GUI with built-in help and small footprint.
· Point and click access to all files (Java, manifest, HTML, image and sound) and directories (package).
· Point and click access to all commands for compiling (javac), archiving (jar), documenting (javadoc), executing (java), debugging (jdb) and disassembling (javap).
· Point and click access to all documents (Java API Specification, Java Tools and Utilities, Java Features and Java Tutorial).
· Point and click creation of all files (Java, manifest and HTML) and directories (package).
· Point and click installation of distribution archive files (Java document, Java source code, Java Tutorial and Sun Tools).
· Automatic determination of class file dependencies for archiving (jar) and documenting (javadoc) Java files.
· Checking for unused, redundant and missing imports.
· Logging of all commands invoked by GUI.
· Code metrics for Java files.
· Built-in text editor (see Edit for details).
· Built-in user interface for the Java debugger with command-line editing and history.
· Self-installing executable (Java archive file).
· Comprehensive installation and user documentation for Java and Java Tools.

A complete suite of web-enabled, client/server, fully customizable business applications with unmatched price/performance. Currently Available modules include:Application Manager, Common Information, General Ledger, Cash Manager, Sale/Purchase Tax, Accounts Receivable, Accounts Payable, Inventory Manager, Sales Order, Purchase Order, Payroll, Human Resources, Fixed Assets, Manufacturing, Integration, Electronic Data Interchange, Executive Information System, Requisition, Contact Manager, Import/Export. A completely integrated (MDI-multiple document interface) solution which has proven itself at hundreds of companies ranging in size from startup ventures to established organizations with hundreds of millions in revenues and very complex operations. Include Microsoft SQL Server 7 (MSDE distribution) or use your existing Microsoft SQL Server 7/2000 or ORACLE 8.

Using special caching algorithms, Zapp can dramatically accelerate web deployed data source by Oracle database engines. (Other database engines will soon be supported.) The API set is much easier to write to than JDBC, and the included Java Bean offers an even simpler (and faster) interface. Zapp is ideal for LAN data applications, too. If you find that data delivery and development costs are a problem, you need Zapp! A 30 day trial license lets you test drive, right now!

iComic Applications - a new set of iComic Applications icons

Java Tools is a useful and lightweight integrated development environment for creating, compiling and executing Java applications and applets. Java Tools includes point and click access to the Java files, commands and documents.

It also includes a built-in text editor and user interface for the Java debugger. Java Tools is for the new Java user who needs help getting started. Its also for the more experienced Java user who wants easy access to the Java commands and a text editor. Version 0.27 adds file trees and popup menus on right click and is easier to install.

JSON-RPC-Java provides an RPC implementation that allows JavaScript DHTML Web applications to call remote methods in a Java Application Server (AJAX functionality) without the need for page reloading.

JSON-RPC-Java library is an enabler for the next generation of fast and highly dynamic enterprise Java Web applications. Minimal changes (if any) are necessary to existing server-side Java code to allow calling from JavaScript (such as the marshalling and unmarshalling of special types), as JSON-RPC-Java dynamically maps JavaScript objects to and from Java objects using Java reflection.

Whats New in This Release:

· The license has changed from the LGPL to the Apache License, Version 2.0.
· New object registration, lookup, and unregister APIs have been added to JSONRPCBridge.