This content has been marked as final. Show 1 reply
We have installed JBoss 4.0.5.GA from the zip (jboss-4.0.5.GA.zip) and with the installers (jems-installer-1.2.0.BETA3.jar and jems-installer-1.2.0.CR1.jar). All three (server/default) installations are different. The results from the installers differ only slightly (e.g. in-memory transaction manager). But the results from unpacking the zip seems to be totally different. The files in the zip are dated from 23.10.2006, while the files in the installers are from 17.10.2006. Over 200 files are changed in size and content.
All I can tell you is that before release, we have a full suite of smoke tests that we run on both the unzipped version and the installer-generated version. As long those tests pass, I we don't investigate too deep why and how those AS installations are different.
Will the Messaging installation continue to support both AS installations in the future? I remember one case where a Messaging (pre-)release did not work properly with the AS installer variant (when it still was a jboss-installer and not a jems-installer).
Yes. That's why we have the smoke tests. If you find problems with a specific installation, please report it, and we will add a smoke test for it, so you (and anybody else) won't run into the same problem in the future.
The problem with this is, that to install our own application based on the Messaging configuration, we have to modify some configuration files from the installation. This is rather difficult to achieve automatically, if the original files differ depending on the way they have been installed.
Can someone please give some guidance for the recommended and future-proof way to install JBoss AS? We do not make use of the advanced features (e.g. EJB3) that are only available with the installer.
We know this is a pain. The problem will completely go away with the 4.2 and 5 series, when Messaging will be the default JMS provider and you won't have to go through any Messaging installation procedure.