Re: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
Brian, On 9/13/23 23:25, Brian Wolfe wrote: The PKCS12 is the industry standard keystore format. Your mac should be creating it in that version. You should get familiar using the pkcs12. Its not difficult to set it up. keytool and openssl support pkcs12 and have for some time now. Its possible your older keystores are of the storetype JKS or JCEKS, JKS used to be the default I think back in Java 6. Anything newer should throw a warning telling you the industry standard is pkcs12. But you can still open older formats by specifying the "--storetype" option. Your getting that error because you probably didn't tell it what kind it is and its default assumption is wrong. Using a keystore is much better for managing your keys than using PEM files. Why? It's best practice to have seperate stores for keys and for trust. +1, and using files in PEM format do not preclude this. by default java has the "cacerts" file for establishing trust. True, but not terribly relevant. -chris On Wed, Sep 13, 2023 at 8:16 PM James H. H. Lampert wrote: Java Keystores work. And I don't find them especially difficult to work with (other than new formats not being backward-compatible with older JVMs, and as one who has made a comfortable living banging out code for IBM Midrange boxes for over a quarter century, I am quite familiar with a much worse variation on that theme, namely, unless you explicitly set the TGTRLS parameter (and have the appropriate previous version compiler installed, and don't need to go back more than it will let you), your programs will not even *restore* onto a prior release system. And the one time I attempted to get anything other than a Java Keystore to work in Tomcat, on an IBM Midrange box, I failed miserably. Putting shell-script wrappers around two different versions of keytool on my work Mac, so that "keytool" launches the Java 8 version, and "keytool-default" launches the default version (in the unlikely event that I'd ever need it) was a relatively simple exercise. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
The PKCS12 is the industry standard keystore format. Your mac should be creating it in that version. You should get familiar using the pkcs12. Its not difficult to set it up. keytool and openssl support pkcs12 and have for some time now. Its possible your older keystores are of the storetype JKS or JCEKS, JKS used to be the default I think back in Java 6. Anything newer should throw a warning telling you the industry standard is pkcs12. But you can still open older formats by specifying the "--storetype" option. Your getting that error because you probably didn't tell it what kind it is and its default assumption is wrong. Using a keystore is much better for managing your keys than using PEM files. It's best practice to have seperate stores for keys and for trust. by default java has the "cacerts" file for establishing trust. On Wed, Sep 13, 2023 at 8:16 PM James H. H. Lampert wrote: > Java Keystores work. And I don't find them especially difficult to work > with (other than new formats not being backward-compatible with older > JVMs, and as one who has made a comfortable living banging out code for > IBM Midrange boxes for over a quarter century, I am quite familiar with > a much worse variation on that theme, namely, unless you explicitly set > the TGTRLS parameter (and have the appropriate previous version compiler > installed, and don't need to go back more than it will let you), your > programs will not even *restore* onto a prior release system. > > And the one time I attempted to get anything other than a Java Keystore > to work in Tomcat, on an IBM Midrange box, I failed miserably. > > Putting shell-script wrappers around two different versions of keytool > on my work Mac, so that "keytool" launches the Java 8 version, and > "keytool-default" launches the default version (in the unlikely event > that I'd ever need it) was a relatively simple exercise. > > -- > JHHL > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Thanks, Brian Wolfe https://www.linkedin.com/in/brian-wolfe-3136425a/
Re: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
Java Keystores work. And I don't find them especially difficult to work with (other than new formats not being backward-compatible with older JVMs, and as one who has made a comfortable living banging out code for IBM Midrange boxes for over a quarter century, I am quite familiar with a much worse variation on that theme, namely, unless you explicitly set the TGTRLS parameter (and have the appropriate previous version compiler installed, and don't need to go back more than it will let you), your programs will not even *restore* onto a prior release system. And the one time I attempted to get anything other than a Java Keystore to work in Tomcat, on an IBM Midrange box, I failed miserably. Putting shell-script wrappers around two different versions of keytool on my work Mac, so that "keytool" launches the Java 8 version, and "keytool-default" launches the default version (in the unlikely event that I'd ever need it) was a relatively simple exercise. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
Shawn and Mark, On 9/13/23 09:30, Mark Thomas wrote: On 13/09/2023 14:00, Shawn Heisey wrote: On 9/12/23 01:06, Thomas Hoffmann (Speed4Trade GmbH) wrote: I moved away from using the proprietary java keystore format. I switched to using Base64 PEM format. This is usually also the format you get from the certificate issuer. No need to convert it into Java format any more and you can also open it with any text editor. I have never been able to get a Java program to accept a certificate/key in PEM format. The closest I've been able to come is creating a PKCS12 file with openssl. Annoying because all the other software I use accepts PEM with no problem, and as you have said, PEM is the format generally produced by a CA. How did you get it to take a PEM cert? Tomcat has supported this for a while. The bulk of th ecode can be found in: https://github.com/apache/tomcat/blob/main/java/org/apache/tomcat/util/net/jsse/PEMFile.java I also have code on GitHub that is very similar. https://github.com/ChristopherSchultz/pem-utils The hard part is the wide variety of "private key" formats that are out there in the wild. Reading a certificate in PEM format from Java is pretty much a one-liner. But reading a private key in one of the many possible formats, encodings, encryption strategies, etc. requires miles and miles of code. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
AW: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
Hello, > -Ursprüngliche Nachricht- > Von: Shawn Heisey > Gesendet: Mittwoch, 13. September 2023 15:00 > An: users@tomcat.apache.org > Betreff: Re: AW: Solution to "Invalid keystore format" (cross-posted to > Tomcat Users List at Apache, and Java 400 List at Midrange) > > On 9/12/23 01:06, Thomas Hoffmann (Speed4Trade GmbH) wrote: > > I moved away from using the proprietary java keystore format. > > I switched to using Base64 PEM format. This is usually also the format you > get from the certificate issuer. > > No need to convert it into Java format any more and you can also open it > with any text editor. > > I have never been able to get a Java program to accept a certificate/key in > PEM format. The closest I've been able to come is creating a PKCS12 file with > openssl. Annoying because all the other software I use accepts PEM with no > problem, and as you have said, PEM is the format generally produced by a > CA. > > How did you get it to take a PEM cert? > > Thanks, > Shawn > If you want to use it for SSL / https, my server.xml snippet looks like: Greetings, Thomas - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
On 13/09/2023 14:00, Shawn Heisey wrote: On 9/12/23 01:06, Thomas Hoffmann (Speed4Trade GmbH) wrote: I moved away from using the proprietary java keystore format. I switched to using Base64 PEM format. This is usually also the format you get from the certificate issuer. No need to convert it into Java format any more and you can also open it with any text editor. I have never been able to get a Java program to accept a certificate/key in PEM format. The closest I've been able to come is creating a PKCS12 file with openssl. Annoying because all the other software I use accepts PEM with no problem, and as you have said, PEM is the format generally produced by a CA. How did you get it to take a PEM cert? Tomcat has supported this for a while. The bulk of th ecode can be found in: https://github.com/apache/tomcat/blob/main/java/org/apache/tomcat/util/net/jsse/PEMFile.java Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
On 9/12/23 01:06, Thomas Hoffmann (Speed4Trade GmbH) wrote: I moved away from using the proprietary java keystore format. I switched to using Base64 PEM format. This is usually also the format you get from the certificate issuer. No need to convert it into Java format any more and you can also open it with any text editor. I have never been able to get a Java program to accept a certificate/key in PEM format. The closest I've been able to come is creating a PKCS12 file with openssl. Annoying because all the other software I use accepts PEM with no problem, and as you have said, PEM is the format generally produced by a CA. How did you get it to take a PEM cert? Thanks, Shawn - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
On 2023/09/12 07:06:52 "Thomas Hoffmann (Speed4Trade GmbH)" wrote: > Hallo James, > > > -Ursprüngliche Nachricht- > > Von: James H. H. Lampert > > Gesendet: Montag, 11. September 2023 18:31 > > An: Java 400 List ; Tomcat Users List > > > > Betreff: Solution to "Invalid keystore format" (cross-posted to Tomcat Users > > List at Apache, and Java 400 List at Midrange) > > > > Ladies and Gentlemen of Both Lists: > > > > Last Friday evening, I ran into a problem updating SSL/TLS keystores on two > > customer boxes, and spent three hours yesterday, finding the cause, doping > > out a way to salvage the certs they'd paid for, and doping out a solution to > > keep it from happening in the future. > > > > It seems that with the new keystores (generated on my Mac, initially created > > with Keytool, and then maintained with Keystore Explorer), they were > > getting: > > > > > Throwable occurred: java.io.IOException: Invalid keystore format > > > at com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source) > > > at java.security.KeyStore.load(KeyStore.java:414) > > > > I put them back on their old keystores, and cycled Tomcat again, to get them > > back up, and then spent three hours working the problem yesterday > > (Sunday) afternoon. > > > > It turns out that the default keytool on my new Mac is the one from Java 17. > > And the customer boxes are running Tomcat under much older JVMs, > > because there's always a significant time lag before any given JVM makes it > > to an IBM Midrange box. > > > > So I was able to salvage one of the certs (and its CA reply, and its > > chain) by moving the cert to a keystore generated on my *old* Mac (with > > Java 8 as the default JVM), and then re-signing and re-chaining it in KSE. > > And I > > tested the KS on our V6 box, to make *sure* it worked. > > > > I then looked for a way, since my new Mac *has* a Java 8 JVM (it's just not > > the default), to conveniently use that JVM's Keytool, and came up with a > > wrapper BASH script to do the job. I tested the wrapper script by using it > > to > > generate their new keystore. > > > > Key takeaway (no pun intended) here: if you get an "Invalid keystore > > format" in Tomcat (or presumably anything else that uses Java Keystores), > > when generating a keystore on one box for use on another, *look for a > > difference in JVM.* > > > > -- > > JHHL > > > > I moved away from using the proprietary java keystore format. > I switched to using Base64 PEM format. This is usually also the format you > get from the certificate issuer. > No need to convert it into Java format any more and you can also open it with > any text editor. This is exactly the same what I have been doing for the past 10 years. No pointless fiddling with Java keystores. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
AW: Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
Hallo James, > -Ursprüngliche Nachricht- > Von: James H. H. Lampert > Gesendet: Montag, 11. September 2023 18:31 > An: Java 400 List ; Tomcat Users List > > Betreff: Solution to "Invalid keystore format" (cross-posted to Tomcat Users > List at Apache, and Java 400 List at Midrange) > > Ladies and Gentlemen of Both Lists: > > Last Friday evening, I ran into a problem updating SSL/TLS keystores on two > customer boxes, and spent three hours yesterday, finding the cause, doping > out a way to salvage the certs they'd paid for, and doping out a solution to > keep it from happening in the future. > > It seems that with the new keystores (generated on my Mac, initially created > with Keytool, and then maintained with Keystore Explorer), they were > getting: > > > Throwable occurred: java.io.IOException: Invalid keystore format > > at com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source) > > at java.security.KeyStore.load(KeyStore.java:414) > > I put them back on their old keystores, and cycled Tomcat again, to get them > back up, and then spent three hours working the problem yesterday > (Sunday) afternoon. > > It turns out that the default keytool on my new Mac is the one from Java 17. > And the customer boxes are running Tomcat under much older JVMs, > because there's always a significant time lag before any given JVM makes it > to an IBM Midrange box. > > So I was able to salvage one of the certs (and its CA reply, and its > chain) by moving the cert to a keystore generated on my *old* Mac (with > Java 8 as the default JVM), and then re-signing and re-chaining it in KSE. > And I > tested the KS on our V6 box, to make *sure* it worked. > > I then looked for a way, since my new Mac *has* a Java 8 JVM (it's just not > the default), to conveniently use that JVM's Keytool, and came up with a > wrapper BASH script to do the job. I tested the wrapper script by using it to > generate their new keystore. > > Key takeaway (no pun intended) here: if you get an "Invalid keystore > format" in Tomcat (or presumably anything else that uses Java Keystores), > when generating a keystore on one box for use on another, *look for a > difference in JVM.* > > -- > JHHL > I moved away from using the proprietary java keystore format. I switched to using Base64 PEM format. This is usually also the format you get from the certificate issuer. No need to convert it into Java format any more and you can also open it with any text editor. Greetings, Thomas - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Solution to "Invalid keystore format" (cross-posted to Tomcat Users List at Apache, and Java 400 List at Midrange)
Ladies and Gentlemen of Both Lists: Last Friday evening, I ran into a problem updating SSL/TLS keystores on two customer boxes, and spent three hours yesterday, finding the cause, doping out a way to salvage the certs they'd paid for, and doping out a solution to keep it from happening in the future. It seems that with the new keystores (generated on my Mac, initially created with Keytool, and then maintained with Keystore Explorer), they were getting: > Throwable occurred: java.io.IOException: Invalid keystore format > at com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source) > at java.security.KeyStore.load(KeyStore.java:414) I put them back on their old keystores, and cycled Tomcat again, to get them back up, and then spent three hours working the problem yesterday (Sunday) afternoon. It turns out that the default keytool on my new Mac is the one from Java 17. And the customer boxes are running Tomcat under much older JVMs, because there's always a significant time lag before any given JVM makes it to an IBM Midrange box. So I was able to salvage one of the certs (and its CA reply, and its chain) by moving the cert to a keystore generated on my *old* Mac (with Java 8 as the default JVM), and then re-signing and re-chaining it in KSE. And I tested the KS on our V6 box, to make *sure* it worked. I then looked for a way, since my new Mac *has* a Java 8 JVM (it's just not the default), to conveniently use that JVM's Keytool, and came up with a wrapper BASH script to do the job. I tested the wrapper script by using it to generate their new keystore. Key takeaway (no pun intended) here: if you get an "Invalid keystore format" in Tomcat (or presumably anything else that uses Java Keystores), when generating a keystore on one box for use on another, *look for a difference in JVM.* -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat Users List
Hi, This is my web.xml file. Nothing special. I'm just getting started. ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd; version=2.4/ web-app /web-app - when I start Tomcat, I get the following error org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unkno wn Source) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1644) at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextCo nfig.java:369) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1062) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.j ava:261) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:117) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4252 ) at org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:11 14) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1212) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:29 3) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:117) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.j ava:1337) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.proc essChildren(ContainerBase.java:1601) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.proc essChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run( ContainerBase.java:1590) at java.lang.Thread.run(Unknown Source) SEVERE: Occurred at line 11 column 6 Any thoughts would be deeply appreciated. Many thanks. Bob This email may contain material confidential to Pearson. If you were not an intended recipient, please notify the sender and delete all copies. We may monitor email to and from our network. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Users List
2008/5/21 Riaz, Bob [EMAIL PROTECTED]: web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd; version=2.4/ web-app REMOVE THIS -- /web-app Remove the extra web-app tag. Antonio - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Users List
Thanks, Antonio! -Original Message- From: Antonio Petrelli [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 21, 2008 10:08 AM To: Tomcat Users List Subject: Re: Tomcat Users List 2008/5/21 Riaz, Bob [EMAIL PROTECTED]: web-app xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd; version=2.4/ web-app REMOVE THIS -- /web-app Remove the extra web-app tag. Antonio - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This email may contain material confidential to Pearson. If you were not an intended recipient, please notify the sender and delete all copies. We may monitor email to and from our network. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
change the email address for Tomcat Users List
Did anybody figure out how to change the email address for Tomcat Users List? Abdelmonaam KALLALI Test Specialist DragonWave 411 Legget Dr mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] tel: mobile: http://www.plaxo.com/click_to_call?src=jj_signatureTo=613-599++ext+275 [EMAIL PROTECTED] 613-599 ext 275 http://www.plaxo.com/click_to_call?src=jj_signatureTo=613-889+0732Email=a [EMAIL PROTECTED] 613-889 0732 https://www.plaxo.com/add_me?u=38657297599v0=4784174k0=538185312src=clie nt_sig_212_1_banner_joininvite=1 Want to always have my latest info? http://www.plaxo.com/signature?src=client_sig_212_1_banner_sig Want a signature like this?
Re: TomCat users' list, forum or documentation ?
Stephen, On May 11, 2007, at 8:54 AM, Stephen Caine wrote: Sorry I misunderstood you. I wish you luck. No problem, I was probably not as clear as I should have been. To close out the thread; I switched over from JForum to phpBB this morning. After about 2-3 hours I had it up and running and now have some 25+ forums ready for traffic. Back to more mundane challenges :-) Thanks to all for the suggestions ! -Sven A prince who is not himself wise cannot be wisely advised… good advice depends on the shrewdness of the prince who seeks it. - Machiavelli, The Prince - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
Good Morning Sven Didnt necessarily want to push you to a Apache solution but considering these (albeit dated) tests http://mail-archives.apache.org/mod_mbox/tomcat-users/200308.mbox/[EMAIL PROTECTED] demonstrates that for situations for serving small static pages Apache does serve small pages faster YMMV! Martin-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Sven [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Sunday, May 13, 2007 3:57 AM Subject: Re: TomCat users' list, forum or documentation ? Stephen, On May 11, 2007, at 8:54 AM, Stephen Caine wrote: Sorry I misunderstood you. I wish you luck. No problem, I was probably not as clear as I should have been. To close out the thread; I switched over from JForum to phpBB this morning. After about 2-3 hours I had it up and running and now have some 25+ forums ready for traffic. Back to more mundane challenges :-) Thanks to all for the suggestions ! -Sven A prince who is not himself wise cannot be wisely advised… good advice depends on the shrewdness of the prince who seeks it. - Machiavelli, The Prince - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
En l'instant précis du 11/05/07 04:15, Sven s'exprimait en ces termes: I downloaded a fresh copy of TomCat and put it on another server since I didn't know how to set up JForum to use the same TomCat as my MySQL-based Confluence and JIRA installations. If you downloaded tomcat+jira/confluence bundle, it may not be that easy, otherwise, since java webp application are supposed to be independent, it should be as easy as if it was on a brand new tomcat. [As a matter of fact, I'm still looking for info that will let me understand the functional architecture in TomCat and Apache+TomCat installations ... who does the serving of what and how do they collaborate ? That's getting off the current topic] for tomcat architecture, http://tomcat.apache.org/ - see the left bar, something called documentation Apache + tomcat - Apache is a fundation, not a software (dont confuse with the 'apache http server' which is not related to 'apache tomcat'). Tomcat and web server can collaborate in the sense that a web server can serve as proxy to a tomcat server. You can configure a web server so that parts of it's ressources are served by tomcat, but tomcat does not require a web server. Docs about this are available in tomcat documentation (http proxy, ajp connector) - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
On May 11, 2007, at 8:24 AM, Caldarale, Charles R wrote: By the way, the product is Tomcat, not TomCat. Ooops, I'd actually read that but forgot it in the heat of the hunt. Didn't mean to offend anyone's sensibilities :-) -Sven - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
Hi David, On May 11, 2007, at 4:28 AM, David Delbecq wrote: for tomcat architecture, http://tomcat.apache.org/ - see the left bar, something called documentation Been there, still exploring. Apache + tomcat - Apache is a fundation, not a software (dont confuse with the 'apache http server' which is not related to 'apache tomcat'). You've hit the nail on the head. For someone who comes in with a Webstar, Webstar/SSL, WebCat, 4D, Phantom, ListStar, PageSentry, MacAuthorize, and CGI background the TomCat experience is quite different and requires a lot of basic assumptions to be scrapped. A lot of what I would have expected to be in end-user TomCat documentation is now probably better suited for documentation in the using application, like JForum. I think, correct me if I'm wrong, that most of the TomCat documentation is out of necessity aimed at developers rather than end users as the TomCat functionality can not anticipate end-user issues for using applications ? Back to trying to get JForum installed, but not struggling with TomCat. Many thanks for the insights, -Sven A prince who is not himself wise cannot be wisely advised… good advice depends on the shrewdness of the prince who seeks it. - Machiavelli, The Prince - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
Stephen, On May 11, 2007, at 8:33 AM, Stephen Caine wrote: Before your give up with Tomcat Not at all. I'm very happily using it with Confluence, JIRA and JForum ... I just have to debug the JForum installation, but that's not a Tomcat problem. -Sven - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
Sven, Before your give up with Tomcat Not at all. I'm very happily using it with Confluence, JIRA and JForum ... I just have to debug the JForum installation, but that's not a Tomcat problem. Sorry I misunderstood you. I wish you luck. Stephen Caine CommonGround Softworks, Inc. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
Hassan, On May 10, 2007, at 12:59 PM, Hassan Schroeder wrote: If this directory that's in the ZIP file is the webapp itself, you should be able to just copy it into the webapps directory and run. Though you may want to rename it as suggested to something simple like 'jforum' because that's the path you'll access it by... Thanks for the reply. I'm still not sure what JForum installation instruction register the JForum application within your Servlet means so I just ignored it. I downloaded a fresh copy of TomCat and put it on another server since I didn't know how to set up JForum to use the same TomCat as my MySQL-based Confluence and JIRA installations. [As a matter of fact, I'm still looking for info that will let me understand the functional architecture in TomCat and Apache+TomCat installations ... who does the serving of what and how do they collaborate ? That's getting off the current topic] After a few stumbles (due to missing files in the JForum installation archive I'm almost there. I've gotten to the point where I'm getting some org.hsqldb.jdbcDriver permission error that I'll bring back to the JForum forum. If you're new to all this, you'll definitely be skipping the merging idea in #2 :-) This is definitely different from the web and applications I installed and managed starting back in '95. I have a lot to unlearn before I can get the correct mindset to understand the current software suites. It would probably be easier if I was coming at it without the prior experience. I really appreciate the hints and suggestions. They nudged me far enough to get started. Thanks, -Sven - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TomCat users' list, forum or documentation ?
Is there a TomCat users' list, forum or documentation that is for actual end-users of TomCat as opposed to developers ? I've read through he last 200 messages on the list hoping to get some insight into how to use TomCat as an end user and am concluding that this is not the right list. Specifically, I'm just trying to figure out how to install JForum using TomCat under OS X. I currently have copies of both Confluence and JIRA running under TomCat on OS X Intel Mac Minis, but JForum has me stumped. Any pointers to other lists, forums or documentation would be appreciated. Thanks, -Sven - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TomCat users' list, forum or documentation ?
On 5/9/07, Sven [EMAIL PROTECTED] wrote: Is there a TomCat users' list yep, and you're there :-) I'm just trying to figure out how to install JForum Sounds like you need a JForum mailing list instead, if you're having an application-specific problem, yes? -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
