Download Glassfish Corba Jar Files [TOP]
Chieko Topalian
Trying to do what I thought would be a easy task but search the web up and down and can't find a solution.
I am try to access a remote ejb3 in glassfish(v2) from jboss (4.0.5).
On a stand-alone app, it's easy, I just include the appserv-rt.jar and javaee.jar in my classpath and create an initialcontext and do the lookup. Works just fine.
On jboss, it's different. I deleted all the *.properties file in the appserv-rt.jar so it won't interfere with jboss and rename it to xappserv-rt.jar and put it in the server's lib directory. Jboss won't even start.
Here are the different properties I tried:
1) This failed with ClassNotFound exception because I can't include appserv-rt.jar which define the com.sun.enterprise.naming.SerialInitContextFactory class:
You are receiving a copy of the Javassist (Java Programming Assistant) Library in source form at -GA/javassist-3.14.0-GA-sources.jar and in object code form in the jar file glassfish/modules/weld-osgi-bundle.jar included with the distribution. The terms of the Oracle license do NOT apply to the Javassist (Java Programming Assistant) program; it is licensed under the following license, separately from the Oracle programs you receive. If you do not wish to install this program, you may choose to not proceed with the installation of Oracle GlassFish Server.
For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.
0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.
a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.
The Oracle GlassFish Server 3.1.2 multi-platform ZIP files are compatible with Solaris, Linux, Mac OS, UNIX, and Windows operating systems. See GlassFish Server Download Locations for a list of download locations.
GlassFish Server 3.1.2 is extracted into a new glassfish3 directory under your current directory. This glassfish3 directory is referred to throughout the GlassFish Server documentation set as as-install-parent.
If you choose to cancel the installation at this point, no GlassFish Server files will be installed, but the directory you specified for as-install-parent will remain. This directory can be deleted manually.
Installation information is captured in log files. The names of the files are timestamp-install.log and timestamp-install-summary.html. On Solaris, Linux, and Mac OS X systems, these files are generated by default in the /tmp directory. On Windows systems, these files are generated in the %TEMP% directory.
Eclipse GlassFish 7 is developed through the GlassFish projectopen-source community at -ee4j/glassfish.The GlassFish project provides a structured process for developing theEclipse GlassFish platform that makes the new features of the Jakarta EEplatform available faster, while maintaining the most important featureof Jakarta EE: compatibility. It enables Java developers to access theEclipse GlassFish source code and to contribute to the development of theEclipse GlassFish.
f5d0e4f075