Any locally attached, intranet or Internet user equipped with either Netscape Navigator or Microsoft Internet Explorer, and Java Plug in 1.3 can use ThinView applets.

ThinView applets are stored on the AS/400 as program objects. The applet appearances are saved in the "thinview/options" database file. The html documents, needed to launch ThinView applets, can be stored in the PC-like directory of your choice.

Just include the aspectjrt.jar as a required archive. For example, here is the HTML code for an HTML editor applet that contains some debugging aspects: <APPLET CODE='com.company.swing.applets.EditorApplet' WIDTH='700' HEIGHT='525'> <PARAM NAME="CODE" VALUE="com.company.swing.applets.EditorApplet" > <PARAM NAME="ARCHIVE" VALUE ="../company-applets.jar,../aspectjrt.jar,../xmlrpc-applet.jar" > <PARAM NAME="type" VALUE="application/x-java-applet;version=1.

One way to accomplish this is to have the applets communicate via TCP/IP sockets to the servlet. The servlet would then use a custom protocol to receive and push information between applets. However, this solution does have firewall problems if the system is to be used over and Internet verses an Intranet.

Yes. Those are client-side technologies, so the host doesn't have to do anything to support or enable them. Any browser (such as Internet Explorer or Netscape) that supports them is enough, so any host will do. It doesn't matter whether Java or Flash are listed among the plan's features, they are supported by default.

ThinView is a Java-based, Web-to-host e-business application developer that allows secure Web browser access to AS/400 applications and data. No prior programming experience is required, since ThinView's unique "set-up wizards" quickly produce easy-to-use applets for 5250 terminal emulation, viewing and/or printing reports, or database applications.

Microsoft supplies the J# Browser Controls that provide the capability to migrate existing applets to run within the context of the .NET Framework - usually with no changes to the Java applet source code!

Java v1.0.2 is limited in its font choices. To be safe with cross-platform names stick with one of the following (exactly as named): TimesRoman, Courier, Dialog, DialogInput, Helvetica. Font size can be just about any positive integer, but certain browsers don't support values greater than 36. The font style may be either: 'plain', 'bold', 'italic', or 'bolditalic'.

Droplets have full browser-independent capabilities, and remain as persistent desktop applications even when the browser is closed. Unlike applets, Droplets deliver zero application code to the client, making start-up much faster. This gives developers the ability to write much larger, enterprise-strength applications without worrying about the start-up cost.

For now, we prefer that you simply link to this site. For one thing, that lets people have a discussion around a visualization using the bookmarking and forums that we provide.

Author: Alex Chaffee (http://www.jguru.com/guru/viewbio.jsp?EID=3) Question originally posed by swati m (http://www.jguru.com/guru/viewbio.jsp?EID=64343 Applets run inside browsers, and servlets run inside servers. So broadly speaking, use applets when you need dynamism on the client side, and use servlets when you need dynamism on the server side. Servlets can produce any HTML (or indeed, any file type), and therefore are much more versatile than applets.

Java Applets inside Safari can be configured to run any installed Java version by using the Java Preferences application.

Yes, JavaMail will work in applets in browsers that support the required JDK version. The Java Plug-in may be required to provide such support.

Most of the applets I use come from Fabio Ciucci's site Anfy Java. Some other good resources for java applets are Gamelan, Java Boutique and Web Developers Journal.

Yes. Even though the Java Plug-in has been enhanced to support APPLET tags, it is fully backward compatible with existing web pages that use OBJECT tags to launch applets. Moreover, the JRE/Java Plug-in continues to ship with the HTML Converter for those developers who want to invoke their applets using OBJECT rather than APPLET tags.

Standard? Hmmm... just link to The Applet Depot's front page (http://www.ericharshbarger.com/java/), and maybe mention me by name (Eric Harshbarger). Go for it. I am always willing to hear new ideas. I cannot guarantee the suggestion will be implemented, but I will consider it.

Yes in signed applets, but no in unsigned applets (most cases). Since we do not allow unsigned applets access to any communications port under the JDK1.1 security model, you can not use the Java communications API with unsigned applets. We do plan to be compliant to JDK1.2 security model in later releases, which might allow trusted applet access to ports. The javax.comm.properties file is not intended to be edited by users.

ThinView secures your data. Users must have a valid AS/400 user ID and Password. After the initial protocol handshake, all data to and from the client and server is encrypted utilizing Secure Sockets Layer (SSL) for client and server authentication, data integration and privacy. ThinView also honors AS/400 system security through levels 40 and 50, and produces an audit trail listing all changes made by users.

In general, applets loaded over the net are prevented from reading and writing files on the client file system, and from making network connections except to the originating host. In addition, applets loaded over the net are prevented from starting other programs on the client. Applets loaded over the net are also not allowed to load libraries, or to define native method calls. If an applet could define native method calls, that would give the applet direct access to the underlying computer.

In Java-enabled browsers, untrusted applets cannot read or write files at all. By default, downloaded applets are considered untrusted. There are two ways for an applet to be considered trusted: The applet is installed on the local hard disk, in a directory on the CLASSPATH used by the program that you are using to run the applet. Usually, this is a Java-enabled browser, but it could be the appletviewer, or other Java programs that know how to load applets.

In both Java-enabled browsers and the appletviewer, applets can read these system properties by invoking System.getProperty(String key): key meaning ____________ ______________________________ java.version Java version number java.vendor Java vendor-specific string java.vendor.url Java vendor URL java.class.version Java class version number os.name Operating system name os.arch Operating system architecture os.version Operating system version file.separator File separator (eg, "/") path.

There are two different ways that applets are loaded by a Java system. The way an applet enters the system affects what it is allowed to do. If an applet is loaded over the net, then it is loaded by the applet class loader, and is subject to the restrictions enforced by the applet security manager. If an applet resides on the client's local disk, and in a directory that is on the client's CLASSPATH, then it is loaded by the file system loader.

Author: John Zukowski (http://www.jguru.com/guru/viewbio.jsp?EID=7) Oracle basically has two JDBC drivers: an OCI driver which includes native code and a Thin driver which is 100% Pure Java. Since the OCI driver includes native code, it cannot be used in applets. You must use thin driver. You can get all Oracle JDBC drivers from http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm.

No. All you need to do is copy and paste the code of the applet you wish to use into the html code of your webpage and upload it.