Tomcat RPMs and database pools - no joy
Hi all, I have a war that connects to a database pool defined in a Resource section within server.xml. This war is run in a tomcat v5.0.19 environment as binary released by the jakarta project, and works 100%. I now want to deploy the war inside a jpackage RPM version of tomcat on my production server, and use the identical configurations for the Resource section and war, but an attempt to start the application fails like so: javax.servlet.ServletException: Error initialising za.co.fma.patricia.struts.PatriciaPlugin with configuration file at '/usr/share/tomcat5/webapps/patricia/WEB-INF/torque.properties': za.co.fma.patricia.PatriciaException: org.apache.torque.TorqueException: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null', cause: No suitable driver I tried the v5.0.24 RPM, and the same results were evident. Googling for the above shows lots of questions, but no definitive answers. Usually the problem goes away when the person with the problem goes over the config. In my case I know my config works, because my test environment is 100% functional. I am trying to work out what could be different between my test environment and the final tomcat RPM file. I have checked that the Postgresql driver is placed in common/lib in both the test environment and the RPM environment. In order for tomcat to install at all, I have forced it to ignore the following three dependancies, as (to my knowledge) they are are included in Sun's JDK v1.4.2 (and jpackage provides no compatibility packages to fake these dependancies for JDK v1.4.x): - [javamail].jar (is there already courtesy of Redhat supplied package, but jpackage cannot find it) - [jdbc-stdext].jar (part of v1.4.2, not present in Jakarta's official tomcat release) - [jndi].jar (part of v1.4.2, not present in Jakarta's official tomcat release) Has anybody got database pools and the tomcat5 RPM to work properly together, and was there anything you needed to do over and above the normal Resource configuration? The config for server.xml looks like this: !-- Global JNDI resources -- GlobalNamingResources Resource name=jdbc/GlobalPatricia auth=Container type=javax.sql.DataSource/ ResourceParams name=jdbc/GlobalPatricia parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter parameter namedriverClassName/name valueorg.postgresql.Driver/value /parameter parameter nameurl/name valuejdbc:postgresql://127.0.0.1:5432/patricia/value /parameter parameter nameusername/name valuexxx/value /parameter parameter namepassword/name valuexxx/value /parameter parameter namemaxActive/name value20/value /parameter parameter namemaxIdle/name value10/value /parameter parameter namemaxWait/name value-1/value /parameter /ResourceParams /GlobalNamingResources The config for warfile.xml looks like this: Context path=/patricia docBase=patricia Valve className=org.apache.catalina.valves.RemoteAddrValve allow=127.0.0.1/ Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_patricia_log. suffix=.txt timestamp=true/ ResourceLink name=jdbc/GlobalPatricia global=jdbc/GlobalPatricia type=javax.sql.DataSource/ Realm className=org.apache.catalina.realm.DataSourceRealm debug=0 dataSourceName=jdbc/GlobalPatricia userTable=person userNameCol=uid userCredCol=user_password userRoleTable=company_person roleNameCol=serial/ /Context Can anyone shed some light? Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JPackage RPMs for mod_jk2
Hi All, I'm trying to help someone out with his integration of Apache and Tomcat. He's using the jpackage RPM packages for mod_jk2 and he's having problems. I remember that someone on this list once got them working and posted the instructions. I tried looking for that email in the Tomcat list archives, but came up empty. Could someone point me to the email or re-post the instructions? TIA! -- A large number of installed systems work by fiat. That is, they work by being declared to work. -- Anatol Holt ++ | Pascal Chong | | email: [EMAIL PROTECTED] | || | Please visit my site at : http://cymulacrum.net| | If you're using my documentation, please read the Terms and| | and Conditions at http://cymulacrum.net/terms.html | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JPackage RPMs for mod_jk2
I've just spent about a week trying to get Apache 1.3 with mod_jk working and Tomcat 4 (embedded in JBoss). I gave up, tossed Tomcat and swapped in Jetty. I haven't got mod_jk working with that either, but at least Jetty doesn't balk at web requests every third click. On Mar 6, 2004, at 9:53 PM, Chong Yu Meng wrote: Hi All, I'm trying to help someone out with his integration of Apache and Tomcat. He's using the jpackage RPM packages for mod_jk2 and he's having problems. I remember that someone on this list once got them working and posted the instructions. I tried looking for that email in the Tomcat list archives, but came up empty. Could someone point me to the email or re-post the instructions? TIA! -- A large number of installed systems work by fiat. That is, they work by being declared to work. -- Anatol Holt ++ | Pascal Chong | | email: [EMAIL PROTECTED] | || | Please visit my site at : http://cymulacrum.net| | If you're using my documentation, please read the Terms and| | and Conditions at http://cymulacrum.net/terms.html | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Where to find Tomcat RPMs?
Hello I cannot find any more rpm packets for Tomcat installation. I usually found them at http://jakarta.apache.org I've got 4.1.24. Is there any newer rpms for Tomcat 4.x, maybe for Tomcat 5.x? rpm are more suitable for our use than tar. Thanks Jens Ove
Re: Where to find Tomcat RPMs?
Check this http://marc.theaimsgroup.com/?l=tomcat-userm=106639528807348w=2 Antony Paul - Original Message - From: Jens Ove Lillegraven [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, November 20, 2003 1:03 PM Subject: Where to find Tomcat RPMs? Hello I cannot find any more rpm packets for Tomcat installation. I usually found them at http://jakarta.apache.org I've got 4.1.24. Is there any newer rpms for Tomcat 4.x, maybe for Tomcat 5.x? rpm are more suitable for our use than tar. Thanks Jens Ove - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[HOWTO] Tomcat 4.1.27 Standalone Jpackage RPMs
How To Install Tomcat 4.1.27 Standalone using Jpackage RPMs --- The Tomcat Team no longer generates monolithic RPMs for the full or LE version of Tomcat after 4.1.24. Instead, RPMs can be obtained from www.jpackage.org. Jpackage's apparent goal is to generate RPMs for common Java based packages and to standardize the installed directory structure and environment. Because Jpackage manages many RPMs, (at least one for each Java library/tool), there are over 20 RPMs that make up a working Tomcat 4.1 installation. This includes RPMs for the j2sdk and its extensions. As with other RPM managed products, future upgrades to Tomcat may only include one or a handfull of RPMs to be updated. If this sounds daunting or difficult to manage, remember that RPMs make the whole process fairly easy. As mentioned above, Jpackage attempts to unify the Java install environment by repackaging JVMs/JREs into a consistent form that allows multiple versions of Sun, Blackdown, and IBM product RPMs to be plug compatible with other Jpackage components like Tomcat. This eliminates many configuration problems and makes user and service environments generally stable. To realize this goal, some Jpackage RPM installation scripts require that the JVM and related components be installed using Jpackage RPMs; this includes the Tomcat 4.1 RPM. Also, there is also a Jpackage utilities RPM that must be installed to support this install architecture. For many reasons, (see the site FAQ for details), Jpackage cannot distribute binary RPMs for many vendor's products or components. However, Jpackage has created nosrc RPMs that you manually compose, (only once), after pulling the products binary sources from the vendor's web sites. The nosrc designation can be misleading: by building RPMs from these templates, downloaded binary components are not rebuilt from Java or other sources, they are simply repackaged as Jpackage compatible binary RPMs! For a Tomcat 4.1 install, this process must be done for only the JVM and a few of its extensions. Don't let this extra step color your opinion of the Jpackage RPMs! Here are the steps I used to install Tomcat 4.1.27 using the Sun 1.4.2_01 j2sdk on a RedHat 8.0 server, (YMMV): --- 1. Erase any j2sdk and obsolete Tomcat RPM installs. For example, these were the commands I used after saving any Tomcat configuration files or webapps: su - Password: rpm -e j2sdk-1.4.2_01-fcs rpm -e tomcat4-4.1.24-full.2jpp rm -rf /var/tomcat4 rm -rf /etc/tomcat4 exit --- 2. Download the following RPMs from www.jpackage.org: ant-1.5.4-2jpp.noarch.rpm jaf-1.0.2-3jpp.nosrc.rpm jakarta-commons-beanutils-1.6.1-4jpp.noarch.rpm jakarta-commons-collections-2.1-4jpp.noarch.rpm jakarta-commons-daemon-1.0.cvs20030227-6jpp.noarch.rpm jakarta-commons-dbcp-1.0-4jpp.noarch.rpm jakarta-commons-digester-1.5-3jpp.noarch.rpm jakarta-commons-fileupload-1.0-1jpp.noarch.rpm jakarta-commons-logging-1.0.3-4jpp.noarch.rpm jakarta-commons-modeler-1.1-2jpp.noarch.rpm jakarta-commons-pool-1.0.1-5jpp.noarch.rpm java-1.4.2-sun-1.4.2.01-7jpp.nosrc.rpm javamail-1.3.1-1jpp.nosrc.rpm jpackage-utils-1.5.27-1jpp.noarch.rpm jta-1.0.1-0.b.3jpp.nosrc.rpm mx4j-1.1.1-5jpp.noarch.rpm regexp-1.3-1jpp.noarch.rpm servletapi4-4.0.4-3jpp.noarch.rpm tomcat4-4.1.27-2jpp.noarch.rpm tyrex-1.0-3jpp.noarch.rpm xalan-j2-2.5.1-1jpp.noarch.rpm xerces-j2-2.4.0-3jpp.noarch.rpm xml-commons-1.0-0.b2.6jpp.noarch.rpm xml-commons-apis-1.0-0.b2.6jpp.noarch.rpm If you wish to use an older JVM version, choose the nosrc RPM that you wish to use; you may also need to include the following nosrc RPMs for required extensions and libraries depending on the JVM version: jaas-ext-1.0.1-2jpp.nosrc.rpm jdbc-stdext-ext-2.0-12jpp.nosrc.rpm jndi-ext-1.2.1-10jpp.nosrc.rpm jsse-ext-1.0.3.01-5jpp.nosrc.rpm ldapjdk-4.1-5jpp.noarch.rpm oro-2.0.7-1jpp.noarch.rpm --- 3. Download the following binary sources from the Sun j2sdk and appropriate product web sites: j2sdk-1_4_2_01-linux-i586.bin jaf-1_0_2.zip javamail-1_3_1.zip jta-1_0_1B-classes.zip Again, you may also need to download these if you are using older JVM versions: jaas-1_0_01.zip jdbc2_0-stdext.jar jndi-1_2_1.zip jsse-1_0_3_02-do.zip, (or jsse-1_0_3_02-gl.zip) --- 4. Install the require Jpackage utility RPM: su - Password: rpm -U jpackage-utils-1.5.27-1jpp.noarch.rpm exit --- 5. Because we are going to build binary RPMs using the nosrc RPMs and the downloaded binary sources, we need a standard host RPM directory structure. Note that the following RPM building steps should be done in a user directory and not as root on your machine! More details for these steps can be found on the www.jpackage.org web site. Here are the commands to prepare the RPM environment: mkdir ~/rpm mkdir ~/rpm/BUILD mkdir ~/rpm/RPMS mkdir ~/rpm/RPMS/i386 mkdir ~/rpm/RPMS/i586
[HOWTO UPDATE] Tomcat 4.1.27 Standalone Jpackage RPMs
How To Install Tomcat 4.1.27 Standalone using Jpackage RPMs --- The Tomcat Team no longer generates monolithic RPMs for the full or LE version of Tomcat after 4.1.24. Instead, RPMs can be obtained from www.jpackage.org. Jpackage's apparent goal is to generate RPMs for common Java based packages and to standardize the installed directory structure and environment. Because Jpackage manages many RPMs, (at least one for each Java library/tool), there are over 20 RPMs that make up a working Tomcat 4.1 installation. This includes RPMs for the j2sdk and its extensions. As with other RPM managed products, future upgrades to Tomcat may only include one or a handfull of RPMs to be updated. If this sounds daunting or difficult to manage, remember that RPMs make the whole process fairly easy. As mentioned above, Jpackage attempts to unify the Java install environment by repackaging JVMs/JREs into a consistent form that allows multiple versions of Sun, Blackdown, and IBM product RPMs to be plug compatible with other Jpackage components like Tomcat. This eliminates many configuration problems and makes user and service environments generally stable. To realize this goal, some Jpackage RPM installation scripts require that the JVM and related components be installed using Jpackage RPMs; this includes the Tomcat 4.1 RPM. Also, there is also a Jpackage utilities RPM that must be installed to support this install architecture. For many reasons, (see the site FAQ for details), Jpackage cannot distribute binary RPMs for many vendor's products or components. However, Jpackage has created nosrc RPMs that you manually compose, (only once), after pulling the products binary sources from the vendor's web sites. The nosrc designation can be misleading: by building RPMs from these templates, downloaded binary components are not rebuilt from Java or other sources, they are simply repackaged as Jpackage compatible binary RPMs! For a Tomcat 4.1 install, this process must be done for only the JVM and a few of its extensions. Don't let this extra step color your opinion of the Jpackage RPMs! Here are the steps I used to install Tomcat 4.1.27 using the Sun 1.4.2_01 j2sdk on a RedHat 8.0 server, (YMMV): --- 1. Erase any j2sdk and obsolete Tomcat RPM installs. For example, these were the commands I used after saving any Tomcat configuration files or webapps: su - Password: rpm -e j2sdk-1.4.2_01-fcs rpm -e tomcat4-4.1.24-full.2jpp rm -rf /var/tomcat4 rm -rf /etc/tomcat4 rm -rf /var/log/tomcat4 exit --- 2. Download the following RPMs from www.jpackage.org: ant-1.5.4-2jpp.noarch.rpm jaf-1.0.2-3jpp.nosrc.rpm jakarta-commons-beanutils-1.6.1-4jpp.noarch.rpm jakarta-commons-collections-2.1-4jpp.noarch.rpm jakarta-commons-daemon-1.0.cvs20030227-6jpp.noarch.rpm jakarta-commons-dbcp-1.0-4jpp.noarch.rpm jakarta-commons-digester-1.5-3jpp.noarch.rpm jakarta-commons-fileupload-1.0-1jpp.noarch.rpm jakarta-commons-logging-1.0.3-4jpp.noarch.rpm jakarta-commons-modeler-1.1-2jpp.noarch.rpm jakarta-commons-pool-1.0.1-5jpp.noarch.rpm java-1.4.2-sun-1.4.2.01-7jpp.nosrc.rpm javamail-1.3.1-1jpp.nosrc.rpm jpackage-utils-1.5.27-1jpp.noarch.rpm jta-1.0.1-0.b.3jpp.nosrc.rpm mx4j-1.1.1-5jpp.noarch.rpm regexp-1.3-1jpp.noarch.rpm servletapi4-4.0.4-3jpp.noarch.rpm tomcat4-4.1.27-2jpp.noarch.rpm tyrex-1.0-3jpp.noarch.rpm xalan-j2-2.5.1-1jpp.noarch.rpm xerces-j2-2.4.0-3jpp.noarch.rpm xml-commons-1.0-0.b2.6jpp.noarch.rpm xml-commons-apis-1.0-0.b2.6jpp.noarch.rpm If you wish to use an older JVM version, choose the nosrc RPM that you wish to use; you may also need to include the following nosrc RPMs for required extensions and libraries depending on the JVM version: jaas-ext-1.0.1-2jpp.nosrc.rpm jdbc-stdext-ext-2.0-12jpp.nosrc.rpm jndi-ext-1.2.1-10jpp.nosrc.rpm jsse-ext-1.0.3.01-5jpp.nosrc.rpm ldapjdk-4.1-5jpp.noarch.rpm oro-2.0.7-1jpp.noarch.rpm --- 3. Download the following binary sources from the Sun j2sdk and appropriate product web sites: j2sdk-1_4_2_01-linux-i586.bin jaf-1_0_2.zip javamail-1_3_1.zip jta-1_0_1B-classes.zip Again, you may also need to download these if you are using older JVM versions: jaas-1_0_01.zip jdbc2_0-stdext.jar jndi-1_2_1.zip jsse-1_0_3_02-do.zip, (or jsse-1_0_3_02-gl.zip) --- 4. Install the require Jpackage utility RPM: su - Password: rpm -U jpackage-utils-1.5.27-1jpp.noarch.rpm exit --- 5. Because we are going to build binary RPMs using the nosrc RPMs and the downloaded binary sources, we need a standard host RPM directory structure. Note that the following RPM building steps should be done in a user directory and not as root on your machine! More details for these steps can be found on the www.jpackage.org web site. Here are the commands to prepare the RPM environment: mkdir ~/rpm mkdir ~/rpm/BUILD mkdir ~/rpm/RPMS mkdir ~/rpm/RPMS/i386 mkdir ~/rpm/RPMS
4.1.27 Full RPMs
Our Tomcat production upgrade process has been constructed around the usage of the full RPMs that were formerly generated by Henri Gomez. Unfortunately, the binary distribution for 4.1.27 no longer seems to include the RPMs that were part of 4.1.24. Of course, www.jpackage.org does have a 4.1.27 RPM available, but it does not seem to be a full version. Before I set out to install the jpackage.org RPM set, I am wondering if the lack of a Jakarta-Tomcat RPM binary is permanent or if it simply remains to be done for 4.1.27? Randy Watler Finali Corporation
Re: RPMs
try to tail catalina.out to see the errors. tail -f /var/log/tomcat/catalina.out if it isn't there look for CATALINA_LOGDIR inside your /etc/tomcat.conf or /etc/tomcat/conf/tomcat.conf Luciano - Original Message - From: Neil Zanella [EMAIL PROTECTED] To: Tomcat Users Mailing List [EMAIL PROTECTED] Sent: Saturday, June 21, 2003 4:22 AM Subject: RPMs Hello, I have installed the tomcat 4 RPMs but when I http to port 8080 I see nothing despite the fact that I have started tomcat and apache from the /etc/init.d directory. Any ideas? Thanks!!! Neil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RPMs
Hello, I have installed the tomcat 4 RPMs but when I http to port 8080 I see nothing despite the fact that I have started tomcat and apache from the /etc/init.d directory. Any ideas? Thanks!!! Neil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat4 / Apache2 / mod_jk2 / Redhat 9 / FalseHope RPMs
I have a working install using all RPMs. At least the tomcat examples are running. I installed the FalseHope RPM, Tomcat4 RPM and mod_jk2 RPM. The FalseHope RPM uses ports 8092(http) and 8093(https) by default. If I change the httpd2.conf and the ssl.conf to use port 80 and port 443, I get errors. If i change httpd2.conf to use port 80, I get a port already used error when I try to restart apache ( /etc/init.d/httpd2 restart ). However; when I run 'lsof | grep LISTEN' nothing is running on port 80. If I change ssl.conf to Listen on port 443, I can start apache OK, but I get the cannot connect error when I try the url https://localhost/examples/; Can anyone advise me about how to proceed? Thanks, -- *** * Rick Roberts* * Advanced Information Technologies, Inc. * *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat4 / Apache2 / mod_jk2 / Redhat 9 / FalseHope RPMs
Never mind. I got it! :) Yea! Thanks a ton to everyone who helped me. -- *** * Rick Roberts* * Advanced Information Technologies, Inc. * *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
modjk2 2.0.2 RPMs
Is anyone working on a new rpm distribution of modjk2 2.0.2, the latest rpm available from the jakarta site is 2.0.1, and of course it would be nice to take advantage of any bug fixes in 2.0.2. I'd rather use an rpm because of the ease of administration. Thank you for any information that you might have. Alberto --- Alberto J. Chinique Network Engineer LEROS Technologies Corporation 9990 Lee Highway Suite 500 Fairfax, VA 22030 (703) 691-1506 x241 [EMAIL PROTECTED]
Binary RPMS
Does anyone know if/when new RPMs for Tomcat 4.1.24, and modjk2 2.02 will be released on the jakarta site? Alberto --- Alberto J. Chinique Network Engineer LEROS Technologies Corporation 9990 Lee Highway Suite 500 Fairfax, VA 22030 (703) 691-1506 x241 [EMAIL PROTECTED]
RPMs: LE vs. Full
I am trying to install Tomcat via the PRMs. I know, RPMs are a pain sometimes, but once I get them working it is easy to install them on a bunch of machines. So, I am using Java JDK 1.4.1. It is installed: # rpm -q j2sdk-1.4.1-fcs j2sdk-1.4.1-fcs I think that 1.4.1 comes with all the xml stuff, so Tomcat LE should work, right? JAVA_HOME is set correctly, to /usr/java/j2sdk1.4.1. Java was installed via the RPM from Sun. Here is what happens when I install the Tomcat LE RPM: # rpm -Uvh tomcat4-4.1.18-le.1jpp.noarch.rpm warning: tomcat4-4.1.18-le.1jpp.noarch.rpm: V3 DSA signature: NOKEY, key ID 307a10a5 error: Failed dependencies: jaxp_parser_impl is needed by tomcat4-4.1.18-le.1jpp xml-commons-apis is needed by tomcat4-4.1.18-le.1jpp The tomcat full RPM works, but I would like to be able to use the LE so that it uses the XML tools that come already with Java 1.4.1. Any suggestions on this? Btw, this is all on Redhat 8.0. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RPMs
where are all the RPMs for the 4.1.X versions of Tomcat?
Re: RPMs
i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RPMs
Actually, the release builds have moved to a new scenario, basically the same as Apache HTTP. Tomcat release binaries are available from various mirror sites. On any given mirror, there are only /bin and /src, and in /bin there are the full versions and the LE versions. I think RPMs went away with 4.1.17, though I could be wrong. In any case, you can find pre-4.1.18 RPMs here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/ On that note, there's no need for an RPM for Tomcat, in my opinion. The only thing a RPM adds (AFAIK) is the creation of a tomcat user and the installation of a start/stop init script. Both tasks are easily completed manually, leaving just the need for the binaries themselves. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:08 PM To: Tomcat Users List Subject: Re: RPMs i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RPMs [off topic: why rpm?]
RPMs provide transaction level control for system modification. When you install an application manually, you ASSUME that the administrator has investigated ALL interactions and dependences. Can correctly uninstall the package when needed, rembers it is installed. Now rpm puts these details on the packager, who is assumed to have knowledge of the workings of the application. But lastly, there are services that can issue updates automaticly as needed. Esp for security. on RedHat there is the Red Hat Network on Windows there is windows update That being said, our Systems admin are not allowed to install ANY application, patch any software without using/creating a RPM. This is company policy, the same goes for our windows boxes. -jason On Tue, 7 Jan 2003, Turner, John wrote: Actually, the release builds have moved to a new scenario, basically the same as Apache HTTP. Tomcat release binaries are available from various mirror sites. On any given mirror, there are only /bin and /src, and in /bin there are the full versions and the LE versions. I think RPMs went away with 4.1.17, though I could be wrong. In any case, you can find pre-4.1.18 RPMs here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/ On that note, there's no need for an RPM for Tomcat, in my opinion. The only thing a RPM adds (AFAIK) is the creation of a tomcat user and the installation of a start/stop init script. Both tasks are easily completed manually, leaving just the need for the binaries themselves. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:08 PM To: Tomcat Users List Subject: Re: RPMs i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RPMs
If you have a Linux box and like to keep your installed programs nice and tidy using the RPM program then rpms are essential unless there is another program used for managing installation of program from tar/tgz/tar.gz archives? I run SuSE v8.0 8.1 and there was a kb article that said to use a program called /sbin/installpkg for installing .tgz packages but I have never seen this nor am I sure that tar.gz is the same as .tgz Guidance? -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 11:15 AM To: 'Tomcat Users List' Subject: RE: RPMs Actually, the release builds have moved to a new scenario, basically the same as Apache HTTP. Tomcat release binaries are available from various mirror sites. On any given mirror, there are only /bin and /src, and in /bin there are the full versions and the LE versions. I think RPMs went away with 4.1.17, though I could be wrong. In any case, you can find pre-4.1.18 RPMs here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/ On that note, there's no need for an RPM for Tomcat, in my opinion. The only thing a RPM adds (AFAIK) is the creation of a tomcat user and the installation of a start/stop init script. Both tasks are easily completed manually, leaving just the need for the binaries themselves. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:08 PM To: Tomcat Users List Subject: Re: RPMs i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RPMs
rpm -tb tarfile will create a rpm from a tarball, it assumes that there is a spec file inside the tarball. If there is no spec file present you can make one. Google: rpm howto http://www.linux.org/docs/ldp/howto/RPM-HOWTO/ On Tue, 7 Jan 2003, Kevin Wilson wrote: If you have a Linux box and like to keep your installed programs nice and tidy using the RPM program then rpms are essential unless there is another program used for managing installation of program from tar/tgz/tar.gz archives? I run SuSE v8.0 8.1 and there was a kb article that said to use a program called /sbin/installpkg for installing .tgz packages but I have never seen this nor am I sure that tar.gz is the same as .tgz Guidance? -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 11:15 AM To: 'Tomcat Users List' Subject: RE: RPMs Actually, the release builds have moved to a new scenario, basically the same as Apache HTTP. Tomcat release binaries are available from various mirror sites. On any given mirror, there are only /bin and /src, and in /bin there are the full versions and the LE versions. I think RPMs went away with 4.1.17, though I could be wrong. In any case, you can find pre-4.1.18 RPMs here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/ On that note, there's no need for an RPM for Tomcat, in my opinion. The only thing a RPM adds (AFAIK) is the creation of a tomcat user and the installation of a start/stop init script. Both tasks are easily completed manually, leaving just the need for the binaries themselves. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:08 PM To: Tomcat Users List Subject: Re: RPMs i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RPMs [off topic: why rpm?]
Believe me, I understand what/why RPMs (and other package schemes) were developed. My point was that there is no need for them with Tomcat. A binary install does nothing to the system. I change Tomcat installations simply by changing a symlink. There is only one dependency, and that is the JDK. I guess it comes down to a trust issue. There's no guarantee that the builder of an RPM did the right thing, nor that an RPM is secure or trusted. All of my servers are RH servers, for example. Unless I'm buying support from Red Hat, any RPM is foreign and untrusted. The only trusted RPM would be one obtained from RH (appropriately signed) under an RH support contract. In the time it takes me or another admin to dissect and analyze an untrusted RPM's actions on a sacrifice box, we can install the app ourselves and have exact, explicit control over how it gets installed. RPMs and a lot of the other package schemes I've worked with over the years have a myth about them...people assume that because it's an RPM that everything is OK. That's a bad assumption to make, and all due respect, it's not wise to base corporate policy on bad assumptions. At my company, the administrators install and configure things themselves, and track it all in a maintenance tracking system for future reference. After all, an RPM can't make any decision about dependencies and interactions if there are custom applications installed; and RPM only knows what it knows, and how can Joe RPMBuilder on the other side of the world know what you've done to your server? I guess for a plain vanilla server that only performs basic services and is the same as everyone else's, that would be OK, but for any server that has proprietary applications installed or custom compiled versions of common software, blindly installing a RPM, accepting what it does, and believing everything will be OK just because it's a RPM is foolish. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:27 PM To: Tomcat Users List Subject: RE: RPMs [off topic: why rpm?] RPMs provide transaction level control for system modification. When you install an application manually, you ASSUME that the administrator has investigated ALL interactions and dependences. Can correctly uninstall the package when needed, rembers it is installed. Now rpm puts these details on the packager, who is assumed to have knowledge of the workings of the application. But lastly, there are services that can issue updates automaticly as needed. Esp for security. on RedHat there is the Red Hat Network on Windows there is windows update That being said, our Systems admin are not allowed to install ANY application, patch any software without using/creating a RPM. This is company policy, the same goes for our windows boxes. -jason On Tue, 7 Jan 2003, Turner, John wrote: Actually, the release builds have moved to a new scenario, basically the same as Apache HTTP. Tomcat release binaries are available from various mirror sites. On any given mirror, there are only /bin and /src, and in /bin there are the full versions and the LE versions. I think RPMs went away with 4.1.17, though I could be wrong. In any case, you can find pre-4.1.18 RPMs here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/ On that note, there's no need for an RPM for Tomcat, in my opinion. The only thing a RPM adds (AFAIK) is the creation of a tomcat user and the installation of a start/stop init script. Both tasks are easily completed manually, leaving just the need for the binaries themselves. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:08 PM To: Tomcat Users List Subject: Re: RPMs i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http://www.pyerotechnics.com - - Owner Lead Pyerotechnics Development, Inc. - - +1 410 808 6646 (c) 500 West University Parkway #1S - - +1 410 467 2266 (f) Baltimore, Maryland 21210-3253 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any
Re: RPMs
* Kevin Wilson [EMAIL PROTECTED] [0134 17:34]: If you have a Linux box and like to keep your installed programs nice and tidy using the RPM program then rpms are essential unless there is another program used for managing installation of program from tar/tgz/tar.gz archives? I run SuSE v8.0 8.1 and there was a kb article that said to use a program called /sbin/installpkg for installing .tgz packages but I have never seen this nor am I sure that tar.gz is the same as .tgz Guidance? tgz == tar.gz == tarball. You just extract them and everything you need is there. You get on with your life. For a taste of how much saner than RPM things can get, I recommend the Penguinistas among you try something like gentoo, or another Linux software system which is based on *BSD packages. You get all the ease of admin and version control, without the horrors of updating (say) Mozilla and finding it's been compiled against slightly differnet versions of your libraries, so having to download 12 new RPMs for those libraries, which in turn breaks dependencies on other packages which need those libraries... rinse, repeat. Try doing that for libraries that RPM itself depends on, or libc, for example. Fun for all the family. How we laughed when RedHat released the new version of rpm, and the rpm of, uh, rpm was released in the *new* format. Which made it impossible to install, unless you'd already installed it. Nice. I haven't used Linux since, and still have bad dreams about it. I hear Suse is less horrible, but then I hear a lot of things... -- Rasputin :: Jack of All Trades - Master of Nuns -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RPMs [off topic: why rpm?]
IMHO: You do have many valid points there. To justifty what we do here: We do not assume, the validity of any package (unless our support contract covers it). That said we role our own RPMs here. We put together systems (servers?) for our clients. We need the assurance that we can deploy a patch, update, or new software on these machines. We use RPMs and MSIs for this reason. If you have a hundred RedHat 7.x and fifty Win2k machines out there running slightly different flavors of your product, you would use (need?) this type of mgmt system. On Tue, 7 Jan 2003, Turner, John wrote: Believe me, I understand what/why RPMs (and other package schemes) were developed. My point was that there is no need for them with Tomcat. A binary install does nothing to the system. I change Tomcat installations simply by changing a symlink. There is only one dependency, and that is the JDK. I guess it comes down to a trust issue. There's no guarantee that the builder of an RPM did the right thing, nor that an RPM is secure or trusted. All of my servers are RH servers, for example. Unless I'm buying support from Red Hat, any RPM is foreign and untrusted. The only trusted RPM would be one obtained from RH (appropriately signed) under an RH support contract. In the time it takes me or another admin to dissect and analyze an untrusted RPM's actions on a sacrifice box, we can install the app ourselves and have exact, explicit control over how it gets installed. RPMs and a lot of the other package schemes I've worked with over the years have a myth about them...people assume that because it's an RPM that everything is OK. That's a bad assumption to make, and all due respect, it's not wise to base corporate policy on bad assumptions. At my company, the administrators install and configure things themselves, and track it all in a maintenance tracking system for future reference. After all, an RPM can't make any decision about dependencies and interactions if there are custom applications installed; and RPM only knows what it knows, and how can Joe RPMBuilder on the other side of the world know what you've done to your server? I guess for a plain vanilla server that only performs basic services and is the same as everyone else's, that would be OK, but for any server that has proprietary applications installed or custom compiled versions of common software, blindly installing a RPM, accepting what it does, and believing everything will be OK just because it's a RPM is foolish. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:27 PM To: Tomcat Users List Subject: RE: RPMs [off topic: why rpm?] RPMs provide transaction level control for system modification. When you install an application manually, you ASSUME that the administrator has investigated ALL interactions and dependences. Can correctly uninstall the package when needed, rembers it is installed. Now rpm puts these details on the packager, who is assumed to have knowledge of the workings of the application. But lastly, there are services that can issue updates automaticly as needed. Esp for security. on RedHat there is the Red Hat Network on Windows there is windows update That being said, our Systems admin are not allowed to install ANY application, patch any software without using/creating a RPM. This is company policy, the same goes for our windows boxes. -jason On Tue, 7 Jan 2003, Turner, John wrote: Actually, the release builds have moved to a new scenario, basically the same as Apache HTTP. Tomcat release binaries are available from various mirror sites. On any given mirror, there are only /bin and /src, and in /bin there are the full versions and the LE versions. I think RPMs went away with 4.1.17, though I could be wrong. In any case, you can find pre-4.1.18 RPMs here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/ On that note, there's no need for an RPM for Tomcat, in my opinion. The only thing a RPM adds (AFAIK) is the creation of a tomcat user and the installation of a start/stop init script. Both tasks are easily completed manually, leaving just the need for the binaries themselves. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:08 PM To: Tomcat Users List Subject: Re: RPMs i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron http
RE: RPMs [off topic: why rpm?]
forgot the most import issue, we use RPM/MSI for jar files. IMHO: You do have many valid points there. To justifty what we do here: We do not assume, the validity of any package (unless our support contract covers it). That said we role our own RPMs here. We put together systems (servers?) for our clients. We need the assurance that we can deploy a patch, update, or new software on these machines. We use RPMs and MSIs for this reason. If you have a hundred RedHat 7.x and fifty Win2k machines out there running slightly different flavors of your product, you would use (need?) this type of mgmt system. On Tue, 7 Jan 2003, Turner, John wrote: Believe me, I understand what/why RPMs (and other package schemes) were developed. My point was that there is no need for them with Tomcat. A binary install does nothing to the system. I change Tomcat installations simply by changing a symlink. There is only one dependency, and that is the JDK. I guess it comes down to a trust issue. There's no guarantee that the builder of an RPM did the right thing, nor that an RPM is secure or trusted. All of my servers are RH servers, for example. Unless I'm buying support from Red Hat, any RPM is foreign and untrusted. The only trusted RPM would be one obtained from RH (appropriately signed) under an RH support contract. In the time it takes me or another admin to dissect and analyze an untrusted RPM's actions on a sacrifice box, we can install the app ourselves and have exact, explicit control over how it gets installed. RPMs and a lot of the other package schemes I've worked with over the years have a myth about them...people assume that because it's an RPM that everything is OK. That's a bad assumption to make, and all due respect, it's not wise to base corporate policy on bad assumptions. At my company, the administrators install and configure things themselves, and track it all in a maintenance tracking system for future reference. After all, an RPM can't make any decision about dependencies and interactions if there are custom applications installed; and RPM only knows what it knows, and how can Joe RPMBuilder on the other side of the world know what you've done to your server? I guess for a plain vanilla server that only performs basic services and is the same as everyone else's, that would be OK, but for any server that has proprietary applications installed or custom compiled versions of common software, blindly installing a RPM, accepting what it does, and believing everything will be OK just because it's a RPM is foolish. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:27 PM To: Tomcat Users List Subject: RE: RPMs [off topic: why rpm?] RPMs provide transaction level control for system modification. When you install an application manually, you ASSUME that the administrator has investigated ALL interactions and dependences. Can correctly uninstall the package when needed, rembers it is installed. Now rpm puts these details on the packager, who is assumed to have knowledge of the workings of the application. But lastly, there are services that can issue updates automaticly as needed. Esp for security. on RedHat there is the Red Hat Network on Windows there is windows update That being said, our Systems admin are not allowed to install ANY application, patch any software without using/creating a RPM. This is company policy, the same goes for our windows boxes. -jason On Tue, 7 Jan 2003, Turner, John wrote: Actually, the release builds have moved to a new scenario, basically the same as Apache HTTP. Tomcat release binaries are available from various mirror sites. On any given mirror, there are only /bin and /src, and in /bin there are the full versions and the LE versions. I think RPMs went away with 4.1.17, though I could be wrong. In any case, you can find pre-4.1.18 RPMs here: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/archives/ On that note, there's no need for an RPM for Tomcat, in my opinion. The only thing a RPM adds (AFAIK) is the creation of a tomcat user and the installation of a start/stop init script. Both tasks are easily completed manually, leaving just the need for the binaries themselves. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:08 PM To: Tomcat Users List Subject: Re: RPMs i think the general tree structure is as follows: /.../bin /rpm /src different builds move around the tree, and not all builds have rpms (at least until some one builds them) On Tue, 7 Jan 2003, Kevin Wilson wrote: where are all the RPMs for the 4.1.X versions of Tomcat
RE: RPMs [off topic: why rpm?]
Agreed. I'm not arguing, just saying that the typical RPM user isn't someone who is capable of building their own RPMs, yet somehow there is the perception that RPMs are safe and easy just because they do a lot of work with just one command and someone says here's the RPM for product X. There's nothing wrong with a package system, RPM or not, in and of itself, just in the way it's used and in the way it's trusted by default by those who aren't building the packages. John -Original Message- From: Jason Pyeron [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 3:41 PM To: Tomcat Users List Subject: RE: RPMs [off topic: why rpm?] IMHO: You do have many valid points there. To justifty what we do here: We do not assume, the validity of any package (unless our support contract covers it). That said we role our own RPMs here. We put together systems (servers?) for our clients. We need the assurance that we can deploy a patch, update, or new software on these machines. We use RPMs and MSIs for this reason. If you have a hundred RedHat 7.x and fifty Win2k machines out there running slightly different flavors of your product, you would use (need?) this type of mgmt system. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: RPMs are quirky, not evil (was RE: Stuck, frustrated and in desperate need of help....)
I wouldn't call requiring root on ports less than 1024 a bug or a misfeature. I know I don't want any user on my servers able to start up their own HTTP, FTP, or DNS daemon (or anything else on ports traditionally left open on firewalls and routers). That would be begging for disaster. John -Original Message- From: Joe Tomcat [mailto:tomcat;mobile.mp] Sent: Thursday, November 07, 2002 7:35 PM To: Tomcat Users List Subject: RPMs are quirky, not evil (was RE: Stuck, frustrated and in desperate need of help) /etc/tomcat4/tomcat4.conf defines the default user as tomcat4. If you are running it on port 80, this needs to be set to root. This is more of a bug/misfeature in Linux than a Tomcat problem, but it is a quirk. -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RPMs are quirky, not evil (was RE: Stuck, frustrated and indesperate need of help....)
On Thu, 2002-11-07 at 15:47, Mark Eggers wrote: RPMs are evil, RPMs are evil . . . There definitely are some painful things about the Tomcat rpms, but once you understand their quirks they are fine. Here are their quirks that I know of so far: Tomcat LE doesn't install when using JDK 1.4. You have to install Tomcat full, even though it shouldn't be necessary (I think). /etc/tomcat4/tomcat4.conf defines the default user as tomcat4. If you are running it on port 80, this needs to be set to root. This is more of a bug/misfeature in Linux than a Tomcat problem, but it is a quirk. You MUST have a /etc/java/java.conf file to set JAVA_HOME. I think that the startup scripts could be smarter and use `which java` to find JAVA_HOME based on the location of JAVA_HOME/bin/java, but they don't so make sure that /etc/java/java.conf exists. I have not found any way to get JNI stuff to work at all with the rpms, short of installing the relevant jars in JAVA_HOME/jre/lib/ext (I think that's the path). tomcat4.conf suggests that I can put an export LD_LIBRARY_PATH in it and that will work but it doesn't. The only two ways to get JMagick to work are to put it in jre/lib/ext or to edit dtomcat4 so that it is in the classpath. This isn't right. But, after getting those problems fixed, the rpms are very handy. Maybe there should be a How do I use the RPMs faq? -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
RE: 4.1.12 rpms
I believe the LE version is for jdk1.4. As jdk1.4 includes some of the XML parsers necessary to run tomcat, the LE version does not include them. -Original Message- From: Charles Baker [mailto:rascharles;yahoo.com] Sent: Sunday, November 03, 2002 6:23 PM To: tomcat Subject: 4.1.12 rpms What is the difference between the full and le versions of the 4.1.12 rpms? = [EMAIL PROTECTED] http://www.charleshbaker.com/~chb/ Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: 4.1.12 rpms
The LE-1.4 version also excludes several jars with additional features. I think JMS was one of them. I use the LE-1.4 version with 1.3.1, but add the jaxp, crimson and xalan jars. David Niaz Habib wrote: I believe the LE version is for jdk1.4. As jdk1.4 includes some of the XML parsers necessary to run tomcat, the LE version does not include them. -Original Message- From: Charles Baker [mailto:rascharles;yahoo.com] Sent: Sunday, November 03, 2002 6:23 PM To: tomcat Subject: 4.1.12 rpms What is the difference between the full and le versions of the 4.1.12 rpms? = [EMAIL PROTECTED] http://www.charleshbaker.com/~chb/ Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
JK 2.0.1 for Linux (binaries and rpms) uploaded
JK 2.0.1 for Linux i386 binaries and rpms (including sources) are available : http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.1/bin/linux/i386/ http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.1/rpms/ Regards -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
rpms for Tomcat4.0.4
Hello All, Is anyone planning to build RPMs for 4.0.4 like there were for 4.0.3? Thanks! -- john = John Cartwright Associate Scientist Geospatial Data Services Group CIRES, National Geophysical Data Center/NOAA (303) 497-6284 [EMAIL PROTECTED] = -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Distribution Policy? Where did the RPMs go?
Note: This is a slightly reworded posting from yesterday. I got no response, and really wanted one. I'm reposting because I'm assuming nobody that knew saw it - and that it's so far down in the stack now they will not see it. Hi - just curious if there would be no more RPM distributions past 4.0.3. That's the last version I see one for. I rather like the RPMs myself and would like to see them continue. Did someone accidentally comment out that part of the Ant script? =) I certainly hope you all haven't decided to no longer build RPM distributions =( Anyone know what is up? Thanks! Eddie
RE: Distribution Policy? Where did the RPMs go?
Don't take me as a definitive source as I'm not a commiter (or even a developer) but I believe there is work to make the RPMs for tomcat4 more FHS compliant. There is also some debate as to how FHS compliance should be achieved (proper directory structure, symlinking in post-install, etc.). This is not a small task, so the RPMs may be a bit delayed as compared to how quickly they were posted in the past. And I do not believe the RPMs are built via the same build tasks that produce the other platform binaries, although that seems like a worthwhile goal to move towards if possible. Rest assured though that tomcat RPMs have not been dropped from the plans as far as I've seen, and if they have been I'll start building some. :-) Jason -Original Message- From: Eddie Bush [mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 12:01 PM To: Tomcat Users Mailing List Subject: Distribution Policy? Where did the RPMs go? Note: This is a slightly reworded posting from yesterday. I got no response, and really wanted one. I'm reposting because I'm assuming nobody that knew saw it - and that it's so far down in the stack now they will not see it. Hi - just curious if there would be no more RPM distributions past 4.0.3. That's the last version I see one for. I rather like the RPMs myself and would like to see them continue. Did someone accidentally comment out that part of the Ant script? =) I certainly hope you all haven't decided to no longer build RPM distributions =( Anyone know what is up? Thanks! Eddie -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Distribution Policy? Where did the RPMs go?
Don't take me as a definitive source as I'm not a commiter (or even a developer) but I believe there is work to make the RPMs for tomcat4 more FHS compliant. There is also some debate as to how FHS compliance should be achieved (proper directory structure, symlinking in post-install, etc.). This is not a small task, so the RPMs may be a bit delayed as compared to how quickly they were posted in the past. And I do not believe the RPMs are built via the same build tasks that produce the other platform binaries, although that seems like a worthwhile goal to move towards if possible. Rest assured though that tomcat RPMs have not been dropped from the plans as far as I've seen, and if they have been I'll start building some. :-) Jason I'm working on tomcat 4.0.4 rpms, which need much more externals rpms (many from commons). That's why it take a little more times than expected -Original Message- From: Eddie Bush [mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 12:01 PM To: Tomcat Users Mailing List Subject: Distribution Policy? Where did the RPMs go? Note: This is a slightly reworded posting from yesterday. I got no response, and really wanted one. I'm reposting because I'm assuming nobody that knew saw it - and that it's so far down in the stack now they will not see it. Hi - just curious if there would be no more RPM distributions past 4.0.3. That's the last version I see one for. I rather like the RPMs myself and would like to see them continue. Did someone accidentally comment out that part of the Ant script? =) I certainly hope you all haven't decided to no longer build RPM distributions =( Anyone know what is up? Thanks! Eddie -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Distribution Policy? Where did the RPMs go?
Thank you for the update =) I'm guessing the 4.1.x series won't start having RPM builds until they reach a full release - is that assumpiton correct? Thanks! Eddie - Original Message - From: GOMEZ Henri [EMAIL PROTECTED] To: Jason Corley [EMAIL PROTECTED]; Tomcat Users List [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, June 21, 2002 11:38 AM Subject: RE: Distribution Policy? Where did the RPMs go? I'm working on tomcat 4.0.4 rpms, which need much more externals rpms (many from commons). That's why it take a little more times than expected -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[RPMINFO] Tomcat 4.0.3 rpms reuploaded
The TC 4.0.3 rpm have been reuploaded since there was a nasty problem in previous upload and only .asc file where present. Sorry for the disturbance. - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Tomcat 4.0.1 RPMs: installation fails, even as root
I can't get Tomcat 4 to install under Linux using the 4.0.1 RPMs (specifically, tomcat4-4.0.1-1.src.rpm). Even as root, it fails with the following message: error: unpacking of archive failed on file /usr/bin: cpio: chown failed - file system is read only I'm a bit of a linux novice - can someone tell me how to fix this? Thanks, Chris B. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.0.1 RPMs: installation fails, even as root
I've fixed this; a security-aware admin had made /usr read-only ... - Original Message - From: chris brown [EMAIL PROTECTED] To: tomcat-user [EMAIL PROTECTED] Sent: Thursday, January 17, 2002 10:48 AM Subject: Tomcat 4.0.1 RPMs: installation fails, even as root I can't get Tomcat 4 to install under Linux using the 4.0.1 RPMs (specifically, tomcat4-4.0.1-1.src.rpm). Even as root, it fails with the following message: error: unpacking of archive failed on file /usr/bin: cpio: chown failed - file system is read only I'm a bit of a linux novice - can someone tell me how to fix this? Thanks, Chris B. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Tomcat 3.3a RPMs updated
The Tomcat 3.3 rpms has been updated to release 2 to fix a problem with launchers configuration paths. http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3/rpms/ -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Alternative Tomcat 3.3 RPMS (was: trouble with apache 1.3.22 and tomcat 3.3 on redhat 7.0)
Not sure if anyone might find this useful, but I compiled my own Tomcat 3.3 RPMs for RedHat 7.2 that depend on the IBMJava2-SDK RPM from IBM. I recognize that there are official Tomcat RPMS that can be downloaded from the Jakarta web site, and I've used the 3.2 ones for a long time in several production environments. I admire Henri Gomez's ability to produce great RPMS; the reason I made my own were: 1. I wanted the directory structure to mirror the binary distribution a little more closely. It makes understanding the documentation a little easier. I'm (slowly) getting used to the filesystem standard (FHS), but I'm not sold on it for 100% of things that are out there. 2. The RPM is built from the binary distribution. I didn't care about how to build tomcat 3.3 per se; I just wanted a script (via RPM) that documented what files needed configuration, etc. Basically, given the binary distribution, what do you have to do to get it installed? 3. My RPM doesn't mangle /etc/httpd/conf/httpd.conf in any way. Instead I provide mod_jk.conf that can be included within httpd.conf when the user wants to. I also tried to document some things in my sample mod_jk.conf file. The example also illustrates how to serve static content from apache and dynamic content from tomcat (using the /examples context). 4. I needed a more flexible startup script (rc file) that could be customized to support more JVMs (Tomcat workers). I've only tested with RedHat 7.1 and 7.2 with the IBM SDK. If they're of any use to anyone--great! If not, please continue to use the RPMs available on the jakarta site--they're great too. Stuff can be downloaded from: http://www.lxpro.com/tomcat/ Greg Bailey [EMAIL PROTECTED] Subject: trouble with apache 1.3.22 and tomcat 3.3 on redhat 7.0 Date: Tue, 8 Jan 2002 16:02:35 -0700 From: Namrata Kasthuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hello, I am trying to integrate apache 1.3.22 with tomcat 3.3. Here's a summary of what I've done 1. intalled apache binaries and it runs fine standalone 2. installed tomcat binaries alone and it runs fine standalone 3. downloaded the mod_jk.so module and placed it in apache's libext directory 4. modifed the tomcat server.xml file to include ApacheConfig / so that the mod_jk.conf file gets auto-generated (any specific place it should go?) 5. modified apache's httpd.conf file to include the above auto-generated file (last line of file) 6. then I restarted both tomcat and apache and apache doesn't start. it says httpd could not start because there is an error in the autoconfig file...that something is mispelled or defined by a module that is not included in the server configuration. Can someone please tell me what I have missed or done incorrectly, as I am new to all of these technologies.also, once working, how can I make sure that tomcat is only being used as the servlet container? Thanks Namrata __ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ smime.p7s Description: S/MIME Cryptographic Signature
Tomcat RPMs?
I went to http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/rpms/ downloaded tomcat4-4.0.1-1.noarch.rpm installed using rpm -iv tomcat4-4.0.1-1.noarch.rpm everything appeared to be going ok until I came to the part in the doc file I found called running.txt execute shell command: $CATALINA_HOME/bin/startup.sh That didn't work. It turns out my Tomcat installation went to /var/tomcat4 which is where I set $CATALINA_HOME to. I looked in the $CATALINA_HOME/bin directory and to my surprise, there was no startup.sh, only a bootstrap.jar. I searched my whole system for a startup.sh and could not find one, so I decided that something was dreadfully wrong, and went back to the tomcat site. I went into http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/bin/ this time and downloaded jakarta-tomcat-4.0.1.zip I unpacked it and it created it's own directory of jakarta-tomcat-4.0.1. I basically cut and pasted the contents of that directory into my /var/tomcat4 directory and over wrote all directories and files. I then ran $CATALINA_HOME/bin/startup.sh and tested my installation with http://localhost:8080 and all appears to be well.I have a question, when I installed the rpm it created a directory etc/tomcat4/conf/tomcat4.conf. As this was not part of my list of installation procedures, can I assume that this directory/file is not needed? I was wondering if I could safely delete this directory or is something left out of the running.txt file? Can anybody tell me what the purpose of the rpms are if they do not properly install tomcat? Thanks, and God Bless and have a happy new year! -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
[Q] Hard to find Tomcat RPMs on the site?
(Please Email any reply directly as well as post to the list) Hi - I've been hand installing Tomcat on my linux box for weeks now because I haven't been able to find an RPM for it. I just found out there is one* - but I can't find a link to it on the site? *http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/rpms/ What I tried: If you go to the download section of the site look for the latest production quality Tomcat release (say 3.2.3) You have to choose between binary or source. If you choose binary - you end up at this link: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/bin/ Which has tarballs but not RPMs if you chose the source - you ended up at this link: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/src/ But how do you end up at: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/rpms/ without knowing it is there? 'deep -- Amandeep Jawa Worker Bee Software -- [EMAIL PROTECTED] 225A Dolores St. San Francisco, CA 94103-2202 Home: 415 255 6257 (ALL MALP) professional: http://www.worker-bee.com personal: http://www.deeptrouble.com political: http://www.sflcv.org
RE: [Q] Hard to find Tomcat RPMs on the site?
Amandeep, version 4.0 of Tomcat is out. Since it is radically different from the version you mentioned below, it's advised that you download the newest version and compile from source. (It's not as hard as it sounds. Actually, there's an article in the latest edition of _Linux Magazine_ that can walk you through the installation.) Shane -Original Message- From: Amandeep Jawa [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 26, 2001 11:37 AM To: [EMAIL PROTECTED] Subject: [Q] Hard to find Tomcat RPMs on the site? (Please Email any reply directly as well as post to the list) Hi - I've been hand installing Tomcat on my linux box for weeks now because I haven't been able to find an RPM for it. I just found out there is one* - but I can't find a link to it on the site? *http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/rpms/ What I tried: If you go to the download section of the site look for the latest production quality Tomcat release (say 3.2.3) You have to choose between binary or source. If you choose binary - you end up at this link: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/bin/ Which has tarballs but not RPMs if you chose the source - you ended up at this link: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/src/ But how do you end up at: http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.3/rpms/ without knowing it is there? 'deep -- Amandeep Jawa Worker Bee Software -- [EMAIL PROTECTED] 225A Dolores St. San Francisco, CA 94103-2202 Home: 415 255 6257 (ALL MALP) professional: http://www.worker-bee.com personal: http://www.deeptrouble.com political: http://www.sflcv.org
RE: 4.0 RPMs: when
From: Jonathan Eric Miller [mailto:[EMAIL PROTECTED]] Sent: Monday, September 24, 2001 2:43 AM To: [EMAIL PROTECTED] Subject: Re: 4.0 RPMs: when What's wrong with the .zip file? Jon Problems with license of all the required jar (jta, jmx, ldap, tyrex). I asked Craig to have all the jars in a tarball available on jakarta.apache.org site. === here is a copy of the mail on tomcat-dev Craig I-am-not-a-lawyer Although there's no technical challenge to doing this, the licensing permission becomes much more murky. The standard permission to redistribute paragraph on the other JAR files talks about packaging inside something with which you are adding value -- and it's not obvious that your proposed approach would qualify, where it's pretty obvious that the value add in the single-download approach is a complete application that includes functionality requiring those JARs. /I-am-not-a-lawyer The whole problem is there is just too many non OSS packages in TC 4.0 and that brake RPM policies. And we're speaking about packaging an Apache Product, not a M$ tool and people used to see Apache 110% OSS. In general, though, how would making two RPMs rather than one satisfy the RPM packing requirements rules any better? If the JARs are not supposed to be packaged in the primary RPM, why is having them in a separate RPM OK? We were speaking about the possibility to have the required jars outside TC 4.0 in an unique tarball which could be used in primary TC 4.0 RPM or build into a second. Having a second RPM, will clearly indicate to users that this stuff IS MANDATORY and a PRE-REQUISITE to build or use TC 4.0 Personally, I'd lean a little further on the side of the poor user whom we force to go through incredible machinations to install and use a binary distribution ... That's why some people works on packaging, allowing poor users to have just to type rpm -Uvh tomcat-xxx.noarch.rpm and have all the stuff magically installed and working. Personally, I'd like to see a more modular approach of TC 4.0 build, allowing a diet TC 4.0 without any requirements on non OSS software. If JSSE is still required for native HTTP/SSL in TC 3.2/3.3/4.0 but users could still Apache + mod_ssl + mod_jk/webapp to have a 100% OSS SSL solutions and that one could be dropped. BTW, till we find a solution to the externals jars problems, having for example a tomcat-4.0-supplimental.tar.gz located at jakarta.apache.org, we'll have to wait for the RPM. I'm sure you could find a Sun Layer which will find an acceptable solution ;)
Re: 4.0 RPMs: when
What's wrong with the .zip file? Jon - Original Message - From: Sergey V. Udaltsov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, September 22, 2001 12:05 PM Subject: Re: 4.0 RPMs: when Hi We still have problems with related jars, like jdbc2.0ext, jta, jmx, ldap which are copyrigthed by Sun and so couldn't be included in RPM I see. But if you cannot include these jars - you're always able to include them into dependancies... What's wrong with this solution? Regards, Sergey
Re: 4.0 RPMs: when
Hi We still have problems with related jars, like jdbc2.0ext, jta, jmx, ldap which are copyrigthed by Sun and so couldn't be included in RPM I see. But if you cannot include these jars - you're always able to include them into dependancies... What's wrong with this solution? Regards, Sergey
4.0 RPMs: when
Hi all I heard a lot of good things about 4.0. But there are no RPMs released:( Can anyone comment the situation with them (or just give URL:)? Regards, Sergey
RE: 4.0 RPMs: when
I heard a lot of good things about 4.0. But there are no RPMs released:( Can anyone comment the situation with them (or just give URL:)? We still have problems with related jars, like jdbc2.0ext, jta, jmx, ldap which are copyrigthed by Sun and so couldn't be included in RPM
[POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
Hi Sergey, With Tomcat 3.2.2 RPMS, I got some XML parser. I suspect it is sun's JAXP implementation 1.0. It DOES NOT support namespaces (I found it from the error messages:) so it is not possible to use XSL in JSPs/Beans/servlets. That's a known problem. I package these RPMs and asked previously in tomcat-dev which parser used by default. Some proposed crimson, others xerces-j (?). Will it be any problem to use JAXP 1.1? Or Xerces? What is the current policy of using XML parsers in tomcat? Why tomcat does not use Xerces having the same Apache licence? I launch that poll to see if which XML parser RPMS users want to see included by default. I could add xerces-j 1.4.0 or crimson 1.1 (from xml-crimson CVS or from http://xml.apache.org/dist/crimson/crimson-1.1.zip) FYI, I removed on all my sites (which use this RPM), jaxp.jar/parser.jar and used xerces-j instead !
Re: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
I launch that poll to see if which XML parser RPMS users want to see included by default. Probably no XML parser should be included. . Just document the fact that admin should synlink necessary jars to the tomcat lib directory. IMHO it is wrong idea to include parser with any java app which requires it. JAXP API makes this unnecessary (definitely unless Tomcat uses some special private API from crimson or xerces). Regards, Sergey
RE: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
I launch that poll to see if which XML parser RPMS users want to see included by default. Probably no XML parser should be included. . Just document the fact that admin should synlink necessary jars to the tomcat lib directory. IMHO it is wrong idea to include parser with any java app which requires it. JAXP API makes this unnecessary (definitely unless Tomcat uses some special private API from crimson or xerces). If I didn't include a default XML parser, we'll receive just too many emails from new users telling about 'tomcat couldn't find XML parser'. The XML parser should be included in the distro since new and average users MAY never use XML in their apps. The experienced users in XML known what is JAXP, NAMESPACE, and also know what parser they want to be used. Note that with TC 3.3/4.0 you'll could use a different parser... The real question is what could be a reasonable choice as XML for Tomcat (size, functionnalities, stability...) I'll forward the POLL to general-xml and general-jakarta !:
Re: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
The XML parser should be included in the distro since new and average users MAY never use XML in their apps. OK. My vote is for xerces (it is good and has same licence). Also, it would be good to have the list of tomcat-compatible parsers. At the moment, I tried jaxp 1.1 and latest xerces - they work correct. What about people using IBM's one? MS's one? BTW, for new and average users it is possible to use RPM dependancies. For example, ask xerces (and sun's) people to put their classes to parser.jar and check for this jar in RPM. Another option, RPM pre-install script could try to find existing parser (and fail if there is no one). RPM is rather sophisticated mechanism to deal with this problem... Regards, Sergey
RE: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
The XML parser should be included in the distro since new and average users MAY never use XML in their apps. OK. My vote is for xerces (it is good and has same licence). Also, it would be good to have the list of tomcat-compatible parsers. At the moment, I tried jaxp 1.1 and latest xerces - they work correct. What about people using IBM's one? MS's one? IBM xml4j is at 99% xerces-j Did MS got a jav parser ? BTW, for new and average users it is possible to use RPM dependancies. I started think at this that's why my latest xerces-j RPM have a : Provides jaxp 1.1 May be next release For example, ask xerces (and sun's) people to put their classes to parser.jar and check for this jar in RPM. Another option, RPM pre-install script could try to find existing parser (and fail if there is no one). RPM is rather sophisticated mechanism to deal with this problem... The build process of RPM allready deal with installed parser (jaxp 1.0/xerces-j) may be next time crimson. I could add such system at install time but what to do when a user got at the same time, crimson and xerces-j ??? Regards, Sergey
Re: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
GOMEZ Henri wrote: IBM xml4j is at 99% xerces-j Did MS got a jav parser ? I do not know whether it is JAXP-compatible and native but some MS XML parser does exist... I started think at this that's why my latest xerces-j RPM have a : Provides jaxp 1.1 Great! This is a way! May be next release OK may be next time crimson. I could add such system at install time but what to do when a user got at the same time, crimson and xerces-j ??? Can two installed RPMs provide jaxp 1.1? Is this valid in RPM world? If yes, some post-install script should ask user to choose the parser somehow... Is this possible with RPM technology? Cheers, Sergey
RE: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
I do not know whether it is JAXP-compatible and native but some MS XML parser does exist... I'm not sure we will ever saw a MS XML parser on Linux and may never a MS Java XML Parser I started think at this that's why my latest xerces-j RPM have a : Provides jaxp 1.1 Great! This is a way! May be next release OK may be next time crimson. I could add such system at install time but what to do when a user got at the same time, crimson and xerces-j ??? Can two installed RPMs provide jaxp 1.1? Is this valid in RPM world? If yes, some post-install script should ask user to choose the parser somehow... With the RPM exclusive, you just could have at the Is this possible with RPM technology? No, they are not exclusive... (but I not sure at 100%)
RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released
What problems were you encountering? And I want to try this with TOMCAT 4? The problem was with cookies support used to track the session. -Thoughts or comments! I didn't try to rebuild mod_webapp from the all latest CVS but last time I tried, there was many files missing :! -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 4:28 PM To: [EMAIL PROTECTED] Subject: RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released Sure ftp://ftp.falsehope.com/home/gomez/mod_webapp/ But it didn't works well and is pretty old ;( - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Nael Mohammad [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 01, 2001 1:21 AM To: '[EMAIL PROTECTED]' Subject: RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released Gomez do you have an RPM for mod_webapp ? -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 4:19 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released RPM available at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2- beta-4/rpms/ Linux i386 mod_jk.so (EAPI and STDAPI) at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2- beta-4/bin/li nux/i386/ - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released
Gomez do you have an RPM for mod_webapp ? -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 4:19 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released RPM available at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/rpms/ Linux i386 mod_jk.so (EAPI and STDAPI) at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/bin/li nux/i386/ - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released
Sure ftp://ftp.falsehope.com/home/gomez/mod_webapp/ But it didn't works well and is pretty old ;( - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Nael Mohammad [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 01, 2001 1:21 AM To: '[EMAIL PROTECTED]' Subject: RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released Gomez do you have an RPM for mod_webapp ? -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 4:19 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released RPM available at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2- beta-4/rpms/ Linux i386 mod_jk.so (EAPI and STDAPI) at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/bin/li nux/i386/ - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released
What problems were you encountering? And I want to try this with TOMCAT 4? -Thoughts or comments! -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 4:28 PM To: [EMAIL PROTECTED] Subject: RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released Sure ftp://ftp.falsehope.com/home/gomez/mod_webapp/ But it didn't works well and is pretty old ;( - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Nael Mohammad [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 01, 2001 1:21 AM To: '[EMAIL PROTECTED]' Subject: RE: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released Gomez do you have an RPM for mod_webapp ? -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Monday, April 30, 2001 4:19 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released RPM available at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2- beta-4/rpms/ Linux i386 mod_jk.so (EAPI and STDAPI) at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/bin/li nux/i386/ - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
[ANNOUNCEMENT] Tomcat 3.2.2 beta 4 RPMS released
RPM available at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/rpms/ Linux i386 mod_jk.so (EAPI and STDAPI) at : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2-beta-4/bin/li nux/i386/ - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
INFO on mod_jk and RPMs ....
Hi, More than 10% of the message on the [EMAIL PROTECTED] (and some on [EMAIL PROTECTED]), are all about mod_jk build and many are related to Linux Box : 1) Could we change reference to projects in http://jakarta.apache.org/site/binindex.html. Some points to xxx/bin : http://jakarta.apache.org/builds/jakarta-ant/release/v1.2/bin/ http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.1/bin/ Some points to xxx : http://jakarta.apache.org/builds/jakarta-ecs/release/v1.4.1/ http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b1/ I'll be or move rpms directory in bin to help users find it ? 2) I will provide binary for TC 3.2.1 as I do for TC 3.3-m1 : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3-m1/bin/linux/i3 86/ with both STD API and EAPI. I'll will also add a INFO about when using stdapi or eapi 3) There is a FACOMATIC but it's not really used by users. Could we build a FAQ.html where we will put info about mod_jk and build. We could also use the Just to remember there is RPM for both TC 3.2.1, 3.3-m1, 4.0b1 : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.1/rpms/ http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3-m1/rpms/ http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b1/rpms/ Direct linux binary : http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.1/bin/linux/i38 6/ (mod_jk/jserv) http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3-m1/bin/linux/i3 86/ (mod_jk/jserv) http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b1/linux/i3 86/ (mod_webapp) THANKS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[ANNOUNCEMENT] RPMs for jakarta.apache.org projects
Hi, Just started to upload my RPMS for jakarta projects : I followed the general recommandation and create a rpms subdir in each project subdir. Each source rpm follow the following rules : - All binaries are rebuilt from source code. No RPM with just copy of allready generated jars. - General jars (jakarta-regexp.jar) goes in /usr/share/java/ to follow the Debian recommandation. Allready done are : ant 1.1 = http://jakarta.apache.org/builds/jakarta-ant/release/v1.1/rpms/ ant 1.2 = http://jakarta.apache.org/builds/jakarta-ant/release/v1.2/rpms/ ecs 1.4.1 = http://jakarta.apache.org/builds/jakarta-ecs/release/v1.4.1/rpms/ oro 2.0.1 = http://jakarta.apache.org/builds/jakarta-oro/release/v2.0.1/rpms/ regexp 1.2 = http://jakarta.apache.org/builds/jakarta-regexp/release/v1.2/rpms/ tomcat 3.2.1= http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.1/rpms/ this one contains both tomcat RPM and mod_jk/mod_jserv apache connectors in an RPM called tomcat-mod ;-) tomcat 4.0-b1 = http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b1/rpms/ this one contains both tomcat4 RPM and mod_webapp apache connector ;-) To be done : SLIDE - STRUTS - TAGLIBS - VELOCITY Since there is many Sun employees around I need your clue and help since I finished jaxp 1.0 and 1.1 RPMs and need to know where to export them. Also does a RPM from jsse 1.0.2 (here fron binaries since I didn't have acess to source code ;-(() Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
TOMCAT 3.3 RPMs from CVS
Hi, Just released RPMs for TOMCAT 3.3 (from CVS). When installing, this RPM replace TOMCAT 3.2BETA since it goes in the same area /var/tomcat but as TC 3.2B could be used at the same time that TC 4.0-m4. TC 3.3 = http://rpmized.free.fr/rpms/tomcat/ http://rpmized.free.fr/rpms/tomcat/tomcat-3.3-cvs.20001110.src.rpm http://rpmized.free.fr/rpms/tomcat/tomcat-3.3-cvs.20001110.noarch.rpm http://rpmized.free.fr/rpms/tomcat/tomcat-manual-3.3-cvs.20001110.noarch.rpm http://rpmized.free.fr/rpms/tomcat/tomcat-mod-3.3-cvs.20001110.src.rpm http://rpmized.free.fr/rpms/tomcat/tomcat-mod-3.3-cvs.20001110.i386.rpm TC 4.0-m4 = http://rpmized.free.fr/rpms/tomcat4/ http://rpmized.free.fr/rpms/tomcat4/tomcat4-4.0-m4.1.src.rpm http://rpmized.free.fr/rpms/tomcat4/tomcat4-4.0-m4.1.noarch.rpm http://rpmized.free.fr/rpms/tomcat4/tomcat4-manual-4.0-m4.1.noarch.rpm Enjoy ;-)
