GlassFish is an open-source Jakarta EE platform application server project started by Sun Microsystems , then sponsored by Oracle Corporation , and now living at the Eclipse Foundation and supported by OmniFish, Fujitsu and Payara. The supported version under Oracle was called Oracle GlassFish Server. GlassFish is free software and was initially dual-licensed under two free software licences : the Common Development and Distribution License (CDDL) and the GNU General Public License (GPL) with the Classpath exception . After having been transferred to Eclipse, GlassFish remained dual-licensed, but the CDDL license was replaced by the Eclipse Public License (EPL).
14-550: GlassFish is the Eclipse implementation of Jakarta EE (formerly the reference implementation from Oracle) and as such supports Jakarta REST , Jakarta CDI , Jakarta Security , Jakarta Persistence , Jakarta Transactions , Jakarta Servlet , Jakarta Faces , Jakarta Messaging , etc. This allows developers to create enterprise applications that are portable and scalable, and that integrate with legacy technologies. Optional components can also be installed for additional services. Built on
28-484: A corresponding specification. The reference implementation often accompanies a technical standard , and demonstrates what should be considered the "correct" behavior of any other implementation of it. Reference implementations of algorithms, for instance cryptographic algorithms , are often the result or the input of standardization processes. In this function they are often dedicated to the public domain with their source code as public domain software . Examples are
42-607: A derivative of Apache Tomcat as the servlet container for serving web content, with an added component called Grizzly which uses Java non-blocking I/O (NIO) for scalability and speed. The commercially supported version of GlassFish was known as Oracle GlassFish Server , formerly Sun GlassFish Enterprise Server, and previously Sun Java System Application Server (SJSAS) has a history, along with other iPlanet software, going back to Netscape Application Server . This includes code from other companies such as Oracle Corporation for TopLink Essentials. Ericsson 's SIP Servlet support
56-547: A modular kernel powered by OSGi , GlassFish runs straight on top of the Apache Felix implementation. It also runs with Equinox OSGi or Knopflerfish OSGi runtimes. HK2 abstracts the OSGi module system to provide components, which can also be viewed as services. Such services can be discovered and injected at runtime. GlassFish is based on source code released by Sun and Oracle Corporation 's TopLink persistence system. It uses
70-568: Is a free software project that was first released in 1998 and has incorporated many improvements since then, including an improved psychoacoustic model. The LAME encoder outperforms early encoders like L3enc and possibly the "gold standard encoder" MP3enc, both marketed by Fraunhofer. LAME was required by some programs released as free software in which LAME was linked for MP3 support. This avoided including LAME itself, which used patented techniques, and so required patent licenses in some countries. All relevant patents have since expired, and LAME
84-551: Is included, the opensource version of it is SailFish, developing towards JSR-289. In 2010, the difference between the commercial and open source edition was already quite small. Over the years several companies forked the GlassFish project and created their own distribution: In response to Oracle’s announcement to end commercial support for GlassFish, a fork called Payara Server was created and released in October 2014. Payara Server
98-478: Is now bundled with Audacity . The name LAME is a recursive acronym for "LAME Ain't an MP3 Encoder". Around mid-1998, Mike Cheng created LAME 1.0 as a set of modifications against the 8Hz-MP3 encoder source code. After some quality concerns were raised by others, he decided to start again from scratch based on the dist10 MPEG reference software sources. His goal was only to speed up the dist10 sources, and leave its quality untouched. That branch (a patch against
112-485: Is open source under the same licenses as the original Oracle GlassFish (combined GPL2 + CDDL ) and has optional commercial support from Payara Services Ltd., via the Payara Enterprise project. Reference implementation In the software development process , a reference implementation (or, less frequently, sample implementation or model implementation ) is a program that implements all requirements from
126-469: The Fraunhofer Society and others. The developers of LAME did not license the technology described by these patents. Distributing compiled binaries of LAME, its libraries, or programs that derive from LAME in countries where those patents have been granted may have constituted infringement , but since 23 April 2017, all of these patents have expired. The LAME developers stated that, since their code
140-468: The development of the ... conformance test suite, at least one relatively trusted implementation of each interface is necessary to (1) discover errors or ambiguities in the specification, and (2) validate the correct functioning of the test suite. Characteristics of a Reference Implementation: LAME LAME is a software encoder that converts digital audio into the MP3 audio coding format . LAME
154-552: The first CERN's httpd , Serpent cipher, base64 variants, and SHA-3 . The Openwall Project maintains a list of several algorithms with their reference source code in the public domain. A reference implementation may or may not be production quality. For example, the Fraunhofer reference implementation of the MP3 standard usually does not compare favorably to other common implementations, such as LAME , in listening tests that determine sound quality. In contrast, CPython ,
SECTION 10
#1732884491305168-454: The reference implementation of the Python programming language , is also the implementation most widely used in production. Testing the implementation-vs-specification relationship further enhances the production 's inter-process efficiencies: A reference implementation is, in general, an implementation of a specification to be used as a definitive interpretation for that specification. During
182-489: The reference sources) became Lame 2.0. The project quickly became a team project. Mike Cheng eventually left leadership and started working on tooLAME (an MP2 encoder). Mark Taylor then started pursuing increased quality in addition to better speed, and released version 3.0 featuring gpsycho, a new psychoacoustic model he developed. A few key improvements since LAME 3.x, in chronological order: Like all MP3 encoders, LAME implemented techniques covered by patents owned by
196-452: Was only released in source code form, it should only be considered as an educational description of an MP3 encoder, and thus did not infringe any patent in itself. They also advised users to obtain relevant patent licenses before including a compiled version of the encoder in a product. Some software was released using this strategy: companies used the LAME library, but obtained patent licenses. In
#304695