appletviewer

Runs applets outside of a web browser.

Synopsis

The command-line options separated by spaces. See Options.

The location of the documents or resources to be displayed. You can specify multiple URLs separated by spaces.

Description

The appletviewer command connects to the documents or resources designated by urls and displays each applet referenced by the documents in its own window. If the documents referred to by urls do not reference any applets with the OBJECT , EMBED , or APPLET tag, then the appletviewer command does nothing. For details about the HTML tags that the appletviewer command supports, see AppletViewer Tags at
http://docs.oracle.com/javase/8/docs/technotes/tools/appletviewertags.html

The appletviewer command requires encoded URLs according to the escaping mechanism defined in RFC2396. Only encoded URLs are supported. However, file names must be unencoded, as specified in RFC2396.

Note: The appletviewer command is intended for development purposes only. For more information, see About Sample/Test Applications and Code at
http://docs.oracle.com/javase/8/docs/technotes/samples/aboutCodeSamples.html

Options

Starts the Applet Viewer in the Java debugger with the jdb command to debug the applets in the document.

Specifies the input HTML file encoding name.

Passes the string javaoption as a single argument to the Java interpreter, which runs the Applet Viewer. The argument should not contain spaces. Multiple argument words must all begin with the prefix -J . This is useful for adjusting the compiler’s execution environment or memory usage.

Источник

Как запустить java web плагин без браузера

Добрый день.
Проблема следующая. Имеется старый видеомагнитофон для видеонаблюдения EverFocus EDSR-900.
К нему есть доступ через web-интерфейс посредством java-web-апплета, для отображения требуется java-плагин в браузере. До определенного момента использовалась java7 установленная в системе(в Ubuntu 14.04 использовался пакет icedtea-7-plugin + firefox, в винде просто устанавливалась java7 + firefox). Но сейчас проблема, последние версии firefox не дружат со старыми плагинами java7, также в Ubuntu16.04 уже нету java7. С плагином из java8 данный web-java-апплет не открывается.
Подскажите, как бы все таки открыть данный апплет. Может есть отдельная софтина для открытия java апплетов?

Добрый день. В комплекте с явой идёт приблуда под названием «appletviewer». Не уверен что поможет, давно дело было, но помню, что как-то она запускала java-апплеты.

Попробовал appletviewer(из java-7-jdk и java-8-jdk) в винде и в линуксе.
Вызываю так:

Подозреваю, что нужно указывать полный урл на сам апплет.

Если запускать так:

Ну извиняйте. Эта софтинка реально запускает апплеты, и реально работает. Только что проверил — запустила несколько простых апплетов. Но должен заметить что нашлись и такие которые не запустились. Что там намутил производитель — это у него спрашивать надо. Ошибка которую выдала софтинка — указывает на какую-то фигню с путями запуска. Это явисты лучше расскажут. Ну а для Вас похоже лучший вариант — виртуалочка с WinXP и IE7, и ява 7 из архивов Оракла.

Источник

appletviewer

Note: You use the appletviewer command to launch the AppletViewer and run applets outside of a web browser. Although available and supported in JDK 9, the Applet API is marked as deprecated in preparation for removal in a future release. Instead of applets, consider alternatives such as Java Web Start or self-contained applications.

Specifies the command-line options separated by spaces. See Options for appletviewer .

Specifies the location of the documents or resources to be displayed. You can specify multiple URLs separated by spaces.

The appletviewer command connects to the documents or resources designated by url and displays each applet referenced by the documents in its own AppletViewer window. If the documents referred to by url don’t reference any applets with the OBJECT , EMBED , or APPLET tag, then the appletviewer command does nothing. The OBJECT , EMBED , and APPLET tags are described in AppletViewer Tags.

The appletviewer command requires encoded URLs according to the escaping mechanism defined in RFC2396. Only encoded URLs are supported. However, file names must be unencoded, as specified in RFC2396.

The appletviewer command is intended for development purposes only.

Options for appletviewer

Specifies the input HTML file encoding name.

Passes the string javaoption as a single argument to the Java interpreter, which runs the AppletViewer. The argument shouldn’t contain spaces. Multiple argument words must all begin with the prefix -J . This is useful for adjusting the compiler’s execution environment or memory usage. Seejava command documentation for more information about JVM options.

AppletViewer Tags

The AppletViewer makes it possible to run a Java applet without using a browser.

The AppletViewer ignores any HTML that isn’t immediately relevant to launching an applet. However, it recognizes a wide variety of applet-launching syntax. The HTML code that the AppletViewer recognizes is described in this section. All other HTML code is ignored.

The object tag is the HTML 4.0 tag for embedding applets and multmedia objects into an HTML page. It’s also an Internet Explorer 4.n extension to HTML 3.2 which enables IE to run a Java applet using the latest Java plug-in.

The AppletViewer ignores the classID attribute, on the assumption that it’spointing to the Java plug-in, with the value:

The AppletViewer also ignores the codebase attribute that’s usually included as part of the object tag, assuming that it points to a Java plug-in in a network cab file with a value like:

The optional codebase parameter tag supplies a relative URL that specifies the location of the applet class.

Either code or object is specified, not both.

The type parameter tag isn’t used by AppletViewer, but should be present so that browsers load the plug-in properly. For an applet, the value should be similar to:

For a serialized object or JavaBean, the type parameter value should be similar to:

Other parameter tags are argument values supplied to the applet.

The object tag recognized by IE4.n and the embed tag recognized by Netscape 4.n can be combined so that an applet can use the latest Java plug-in, regardless of the browser that downloads the applet.

The AppletViewer doesn’t recognize the java_code , java_codebase , java_object , or java_type param tags. These tags are needed only when the applet defines parameters with the names code , codebase , object , or type , respectively. In that situation, the plug-in recognizes and uses the java_ version option in preference to the version is be used by the applet. If the applet requires a parameter with one of these four names, then it might not run in the AppletViewer.

The embed tag is the Netscape extension to HTML 3.2 that allows embedding an applet or a multimedia object in an HTML page. It allows a Netscape 4.n browser (which supports HTML 3.2) to run a Java applet using the Java plug-in.

The object and embed tags can be combined so that an applet can use the latest Java plug-in, regardless of the browser that downloads the applet.

Unlike the object tag, all values specified in an embed tag are attributes (part of the tag) rather than parameters (between the start tag and end tag), specified with a param tag.

To supply argument values for applet parameters, you add additional attributes to the embed tag.

The AppletViewer ignores the src attribute that’s usually part of an embed tag.

Either code or object is specified, not both.

The optional codebase attribute supplies a relative URL that specifies the location of the applet class.

The type attribute isn’t used by the AppletViewer, but should be present so that browsers load the plug-in properly.

For an applet, the value should be similar to:

For a serialized object or JavaBean, the type parameter value should be similar to:

The pluginspage attribute isn’t used by the AppletViewer, but should be present so that browsers load the plug-in properly. It should point to a Java plug-in in a network cab file with a value like:

The applet tag is the original HTML 3.2 tag for embedding an applet in an HTML page. Applets loaded using the applet tag are run by the browser, which may not be using the latest version of the Java platform. To ensure that the applet runs with the latest version, use the object tag to load the Java plug-in into the browser. The plug-in then runs the applet.

Either code or object is specified, not both.

The optional codebase attribute supplies a relative URL that specifies the location of the applet class.

The param tags supply argument values for applet parameters.

The app tag was a short-lived abbreviation for applet that’s no longer supported. The AppletViewer translates the tag and prints an equivalent tag that’s supported.

Источник

Как запустить Java-апплеты? [Дубликат]

На этот вопрос уже есть ответ здесь:

Есть ли способ запустить апплет Java на Chrome или Firefox? Я получаю сообщение об ошибке на Тестовая страница Java что Java больше не будет работать на Chrome или Firefox из-за неподдерживаемого NPAPI ,

У меня есть старый набор *.class файлы с .html чтобы запустить его, и я просто хочу иметь возможность запустить этот апплет как-то. Но как?

Есть ли способ запустить апплет Java на Chrome или Firefox?

Нет. Апплеты больше не поддерживаются в Firefox или Chrome.

Firefox больше не обеспечивает поддержку NPAPI (технология, необходимая для Java-апплетов)

По состоянию на сентябрь 2018 года Firefox больше не предлагает версию, которая поддерживает NPAPI, технологию, необходимую для запуска апплетов Java. Ява Плагин для веб-браузеров опирается на кроссплатформенный плагин архитектура NPAPI, которая поддерживалась всеми основными веб-браузерами на протяжении более десяти лет. 64-битная версия Firefox никогда не поддерживалась NPAPI и Firefox версии 52ESR являются последним выпуском, который поддерживает технология. Это ниже базовой линии безопасности, и больше не поддерживается.

Chrome больше не поддерживает NPAPI (технология, необходимая для апплетов Java)

Плагин Java для веб-браузеров опирается на кроссплатформенную архитектуру плагинов NPAPI, которая поддерживается всеми основными веб-браузерами уже более десяти лет. Google Chrome версии 45 и выше прекратил поддержку NPAPI, поэтому Java Plugin больше не работает в этих браузерах.

Так как мне запустить Java-апплеты?

Используйте AppletViewer из JDK до Java SE 11.

Команда appletviewer позволяет запускать апплеты вне сети браузер.

СИНТАКСИС

ОПИСАНИЕ

Команда appletviewer подключается к документам или ресурсам обозначается URL-адресами и отображает каждый апплет, на который ссылается документы в собственном окне. Примечание: если документы, указанные URL не ссылаются ни на какие апплеты с OBJECT, EMBED или APPLET тег, то appletviewer ничего не делает. Подробнее о тегах HTML, которые Поддержка appletviewer, см. Теги AppletViewer.

Примечание. Программа просмотра приложений предназначена только для разработки.

В качестве альтернативы прочтите Oracle White Paper (pdf) Переход с Java-апплетов на подключаемые бесплатные Java-технологии , который рекомендует Java Web Start:

Java Web Start была включена в Oracle JRE с 2001 года и является запускается автоматически, когда приложение Java использует Java Web Start Технология загружается впервые. Преобразование апплет к приложению Java Web Start предоставляет возможность запуска и обновить полученное приложение, не полагаясь на веб-браузер

Обратите внимание, что как Java-апплеты, так и Java Web Start были удален полностью в Java SE 11 (выпуск сентябрь 2018). Начиная с этой версии нет (поддерживаемого) способа запуска приложений Applets или Web Start.

Источник

C
AppletViewer

C.1 Introduction

This appendix describes the AppletViewer, an alternative to using Oracle JInitiator. The AppletViewer is a JDK component and an Oracle-supported product that client machines use to view applications running on the Forms Server. Upgraded versions are available for download from the Forms Developer Web site.

The AppletViewer is only supported on Windows 95 and Windows NT 4.0.

C.2 Running Application in the AppletViewer

To run applications in the AppletViewer, you must complete the following steps:

Prepare to run your application with the AppletViewer.

Add the clientBrowser parameter to your base HTML file.

Set the clientBrowser parameter.

When running your application in the AppletViewer, requests to show a URL (for example, web.showDocument and RUN_PRODUCT) will be ignored by the AppletViewer. If this is the case, you will need to follow the process to trust the Forms applet, as described later in this chapter in Section C.3.1, «Trusting the Forms Applet by Registering Its Signature».

C.2.1 Preparing to Run Your Application with the AppletViewer

In order to prepare to run your application within the AppletViewer, make the AppletViewer available for download and inform your users that they will have to install the AppletViewer on their client machines. Complete the following:

JDK_DOWNLOAD.HTM is the template HTML file that allows your users to download the AppletViewer.

Copy JDK.EXE to your Web server.

You must copy JDK.EXE to the location specified within JDK_DOWNLOAD.HTM.

Copy JDK_DOWNLOAD.HTM to your Web server.

You must copy JDK_DOWNLOAD.HTM to the location specified within JDK_DOWNLOAD.HTM.

C.2.2 Adding the clientBrowser Parameter to your Base HTML File

To use the clientBrowser parameter, you must have security permissions to issue a system call that executes the named application. In general, when loading Java class files, the Forms applet is not trusted and, as such, cannot issue such system calls. However, when the Forms applet is trusted, it is able to issue these calls. The Forms applet is considered trusted when one of the following is true:

The Forms applet signature is «registered» on the client machine as described in Section C.3.1, «Trusting the Forms Applet by Registering Its Signature».

The Forms Java class files are installed locally on the client system and the CLASSPATH environment variable is set as described in Section C.3.2, «Trusting the Forms Applet by Installing the Forms Java Class Files Locally».

These HTML file examples assume that you trusted the Forms applet by registering its signature on your machine. If you trusted the Forms applet by locally installing the Forms Java class files instead, you should not download the F60ALL.JAR file. Therefore, remove the ARCHIVE=»/. /f60all.jar» applet tag from your HTML file.

C.2.3 Setting the clientBrowser Parameter

To set the clientBrowser parameter, do one of the following:

Add the clientBrowser parameter to your HTML file.

Add the clientBrowser parameter to your HTML file, and have each client modify their JDK_SETUP.BAT file.

Add the clientBrowser Parameter to Your HTML File.

This option assumes that every client has its browser executable installed into the same physical directory because the physical path of the browser is hard-coded in the HTML file. For example:

Add the clientBrowser Parameter to Your HTML File and Have Each Client Modify Their JDK_SETUP.BAT File.

This option is best if there is a possibility that clients have installed their browser executables into different physical directories. It does assume, however, that all clients are using the same browser. For example, the HTML file might look like this:

And JDK_SETUP.BAT would look like this:

C.3 Registering the Forms Applet Signature

A signature allows client machines to verify that a file has been downloaded from a valid and trusted entity (a signer ). This allows client machines to protect themselves from malicious or malfunctioning Java archive (JAR) files. In order for a JAR file to be validated by a client, the signature of that file must be registered on the client machine. Javakey is a Sun Microsystems command-line tool that generates digital signatures for JAR files.

The Forms applet is itself a signed JAR file. You have two options for registering the Forms applet signature. Choose one of the following:

Register the signature on your client machine(s) using the Forms applet signature we provide.

Re-sign the Forms applet with your own signature and register that signature on your client machine(s). If you choose this method, please refer to http://java.sun.com/security/usingJavakey.html for instructions on creating and signing JAR files.

C.3.1 Trusting the Forms Applet by Registering Its Signature

To trust the Forms applet by registering its signature:

Copy the Forms Developer certificate to \ORACLE_HOME\FORMS60\JAVA on the client machine.

The certificate is a file named Dev.x509. It is located in \ORACLE_HOME\FORMS60\JAVA on the server.

Open a DOS Command Prompt, and navigate to \ORACLE_HOME\FORMS60\JAVA.

Type: javakey -c Developer true

This command creates a trusted identity for the AppletViewer on the client’s identity database using the exact name of the certificate provider.

Type javakey -ic Developer Dev.x509

This command imports the Dev.x509 certificate into the client’s JDK identity database and associates the certificate with the trusted identity created in step 3.

C.3.2 Trusting the Forms Applet by Installing the Forms Java Class Files Locally

To trust the Forms applet by installing the Java class files locally:

Copy the \ORACLE_HOME\FORMS60\JAVA directory to a new directory on the client machine.

Copy this directory exactly; do not change the directory structure in any way.

Modify JDK_SETUP.BAT in your ORACLE_HOME directory:

Open JDK_SETUP.BAT in a text editor.

Modify the CLASSPATH environment variable to reference the new directory.

Save your changes to JDK_SETUP.BAT.

C.4 Instructions for the User

To run an application from within the AppletViewer, complete the following steps:

Install the AppletViewer.

Run the AppletViewer.

Invoke a Web browser from within the AppletViewer.

C.4.1 Installing the AppletViewer

To install the AppletViewer, use the Oracle Installer to install the JDK AppletViewer:

Shut down any active Windows applications.

From the taskbar, choose StartRun .

In the Run dialog, type the following (where D: is your CD-ROM drive letter): D:\setup.exe and click OK .

In the Oracle Installation Settings dialog, check the default values for your company name and your ORACLE_HOME directory.

Click Oracle Forms Server .

From the list of Available Products, select JDK AppletViewer .

C.4.2 Running the AppletViewer

To run the AppletViewer:

From a DOS command, navigate to the AppletViewer executable (appletviewer.exe).

Run the AppletViewer executable, specifying the host name, HTML file virtual directory, and HTML file.

For example, type: appletviewer http://myhost.com/web_html/start.html

C.4.3 Invoking a Web Browser From Within the AppletViewer

To invoke a Web browser from within the AppletViewer:

Trust the Forms using one of two methods:

Register the Forms applet signature.

Install the Forms Java class files locally.

Add the clientBrowser parameter to your base HTML file.

Источник