Contents - Cultural View

Contents - Cultural View Contents - Cultural View

culturalview.com
from culturalview.com More from this publisher
14.07.2013 Views

OpenJDK 244 [48] graphics-rasterizer project page (http:/ / openjdk. java. net/ projects/ graphics-rasterizer/ ) [49] Graham, Jim (2007-10-03). "Open Source rasterizer" (http:/ / mail. openjdk. java. net/ pipermail/ 2d-dev/ 2007-October/ 000078. html). Sun Microsystems. . Retrieved 2007-05-09. [50] "Javascript is encumbered and there is no javascript plugin support." (http:/ / icedtea. classpath. org/ bugzilla/ show_bug. cgi?id=85). IcedTea. 2008-03-11. . Retrieved 2008-06-01. "Changing Summary. JavaScript is no longer encumbered, but we still need liveconnect support." [51] Andrew, Haley (2007-06-07). "Experimental Build Repository at icedtea.classpath.org" (http:/ / article. gmane. org/ gmane. comp. java. openjdk. distro-packaging. devel/ 5). . Retrieved 2007-06-09. [52] Mark, Wielaard (2007-06-07). "Experimental Build Repository at icedtea.classpath.org" (http:/ / developer. classpath. org/ pipermail/ classpath/ 2007-June/ 002109. html). . Retrieved 2007-06-09. [53] Fitzsimmons, Thomas (2007-06-08). "Credits" (http:/ / mail. openjdk. java. net/ pipermail/ distro-pkg-dev/ 2007-June/ 000032. html). . Retrieved 2007-06-08. [54] "Red Hat and Sun Collaborate to Advance Open Source Java Technology" (http:/ / home. businesswire. com/ portal/ site/ google/ index. jsp?ndmViewId=news_view& newsId=20071105005882& newsLang=en). Red Hat. 2007-11-05. . Retrieved 2007-11-06. [55] http:/ / openjdk. java. net/ legal/ openjdk-trademark-notice. html [56] "icedtea-java7 in Ubuntu" (https:/ / launchpad. net/ ubuntu/ + source/ icedtea-java7). . Retrieved 2008-04-19. [57] http:/ / www. sun. com/ software/ opensource/ java/ faq. jsp [58] http:/ / parleys. com/ display/ PARLEYS/ OpenJDK+ -+ The+ First+ Year?showComments=true PHP/Java Bridge There are three well known implementations of the PHP scripting language: • The original implementation of PHP and the de facto standard is the open source PHP distribution. • Project Zero has a PHP runtime written in Java. It also distributes extensions from the open source implementation of PHP. • Quercus is an open-source pure Java implementation of the PHP scripting language. To bridge between PHP scripts and Java libraries all three implementations provide a PHP/Java bridge. The de facto implementation of PHP has a PHP/Java Bridge separately available from SourceForge. This uses a dual process model where the Java libraries are run in a separate process from the PHP runtime. Interactions with Java objects are marshalled across to the Java process using an XML [1] protocol. Quercus and Project Zero implement PHP on top of the Java Virtual Machine and so can run the Java libraries in the same process as the PHP runtime. This reduces the overhead of interacting with Java libraries when compared with the dual process model. See also • Quercus (software) External links • Open source PHP homepage [2] • SourceForge PHP/Java Bridge homepage [3] • Project Zero homepage [4] • Quercus homepage [5]

PHP/Java Bridge 245 References [1] http:/ / php-java-bridge. sourceforge. net/ pjb/ PROTOCOL. TXT [2] http:/ / www. php. net/ [3] http:/ / php-java-bridge. sourceforge. net/ [4] http:/ / www. projectzero. org/ documentation/ [5] http:/ / quercus. caucho. com/ Java package A Java package is a mechanism for organizing Java classes into namespaces similar to the modules of Modula. Java packages can be stored in compressed files called JAR files, allowing classes to download faster as a group rather than one at a time. Programmers also typically use packages to organize classes belonging to the same category or providing similar functionality. • A package provides a unique namespace for the types it contains. • Classes in the same package can access each other's package-access members. Overview In general, a package can contain the following kinds of types. • Classes • Interfaces • Enumerated types • Annotations Using packages In a Java source file, the package that this file's class or classes belong to is specified with the package keyword. This keyword is usually the first keyword in source file. [1] package java.awt.event; To use a package's classes inside a Java source file, it is convenient to import the classes from the package with an import declaration. The following declaration import java.awt.event.*; imports all classes from the java.awt.event package, while the next declaration import java.awt.event.ActionEvent; imports only the ActionEvent class from the package. After either of these import declarations, the ActionEvent class can be referenced using its simple class name: ActionEvent myEvent = new ActionEvent(); Classes can also be used directly without an import declaration by using the fully-qualified name of the class. For example, java.awt.event.ActionEvent myEvent = new java.awt.event.ActionEvent(); does not require a preceding import declaration. [2] [3] Note that if you do not use a package declaration, your class ends up in an unnamed package.

PHP/Java Bridge 245<br />

References<br />

[1] http:/ / php-java-bridge. sourceforge. net/ pjb/ PROTOCOL. TXT<br />

[2] http:/ / www. php. net/<br />

[3] http:/ / php-java-bridge. sourceforge. net/<br />

[4] http:/ / www. projectzero. org/ documentation/<br />

[5] http:/ / quercus. caucho. com/<br />

Java package<br />

A Java package is a mechanism for organizing Java classes into namespaces similar to the modules of Modula. Java<br />

packages can be stored in compressed files called JAR files, allowing classes to download faster as a group rather<br />

than one at a time. Programmers also typically use packages to organize classes belonging to the same category or<br />

providing similar functionality.<br />

• A package provides a unique namespace for the types it contains.<br />

• Classes in the same package can access each other's package-access members.<br />

Overview<br />

In general, a package can contain the following kinds of types.<br />

• Classes<br />

• Interfaces<br />

• Enumerated types<br />

• Annotations<br />

Using packages<br />

In a Java source file, the package that this file's class or classes belong to is specified with the package keyword. This<br />

keyword is usually the first keyword in source file. [1]<br />

package java.awt.event;<br />

To use a package's classes inside a Java source file, it is convenient to import the classes from the package with an<br />

import declaration. The following declaration<br />

import java.awt.event.*;<br />

imports all classes from the java.awt.event package, while the next declaration<br />

import java.awt.event.ActionEvent;<br />

imports only the ActionEvent class from the package. After either of these import declarations, the ActionEvent<br />

class can be referenced using its simple class name:<br />

ActionEvent myEvent = new ActionEvent();<br />

Classes can also be used directly without an import declaration by using the fully-qualified name of the class. For<br />

example,<br />

java.awt.event.ActionEvent myEvent = new java.awt.event.ActionEvent();<br />

does not require a preceding import declaration.<br />

[2] [3]<br />

Note that if you do not use a package declaration, your class ends up in an unnamed package.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!