This java.net article describes the clustering capabilities of GlassFish version 3.1 and helps you get started deploying your application to a GlassFish cluster.
Would like to confirm the ff. I got confused actually with the version I needed to download that will work on glassfish 3.0.1
a. Debian Squeeze (HP DL360). Need to use java version6
On Debian, I did apt-get install sun-java6-jdk. So when I check it's
java version "1.6.0_22"
Java(TM) SE... (1 Reply)
questions.
What's basically the difference between if I use the opensource and oracle glassfish (the one that requires license for production use)? Is there an evaluation period for the latter? Pls advise (0 Replies)
I tried to install glassfish on Solaris 10 and it worked fine on other instances. I got the below message
bash-3.00# ./sjsas-9_1_01-solaris-sparc.bin -console
bash: ./sjsas-9_1_01-solaris-sparc.bin: Invalid argument
I logged on as root and the file has execute permission. So strange. Do... (1 Reply)
BUNDLE-PACKAGE(1)BUNDLE-PACKAGE(1)NAME
bundle-package - Package your needed .gem files into your application
SYNOPSIS
bundle package
DESCRIPTION
Copy all of the .gem files needed to run the application into the vendor/cache directory. In the future, when running bundle install(1)
bundle-install.1.html, use the gems in the cache in preference to the ones on rubygems.org.
GIT AND PATH GEMS
In Bundler 1.0, the bundle package command only packages .gem files, not gems specified using the :git or :path options. This will likely
change in the future.
REMOTE FETCHING
By default, if you simply run bundle install(1) bundle-install.1.html after running bundle package(1) bundle-package.1.html, bundler will
still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache.
For instance, consider this Gemfile(5):
source "http://rubygems.org"
gem "nokogiri"
If you run bundle package under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to JRuby and
run bundle install, bundler is forced to check to see whether a "java" platformed nokogiri exists.
Even though the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it actually has a C extension that does not run on
JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more spe-
cific to your platform.
This problem is also not just limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploy-
ing to Linux, or even when developing on OSX and deploying to Linux.
If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local
to skip checking for more appropriate gems, and just use the ones in vendor/cache.
One way to be sure that you have the right platformed versions of all your gems is to run bundle package on an identical machine and check
in the gems. For instance, you can run bundle package on an identical staging box during your staging process, and check in the ven-
dor/cache before deploying to production.
June 2012 BUNDLE-PACKAGE(1)
