On Mon, Apr 19, 2004 at 11:32:38PM +0200, C. Kukulies wrote:
Can someone give me an advice which way to go WRT to using a
tomcat/apache combo on a Unix (not Linux) system?
There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2.
worker.properties worker2.properties,
On Mon, Apr 19, 2004 at 05:53:19PM -0400, Parsons Technical Services wrote:
I don't know if you will get much response with this request. What you may
wish to do is define your requirements for your application and environment.
Then set back and take in all the opinions on which way is best.
At this point it looks like tomcat 5 will handle your needs.
Look at this for cgi:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cgi-howto.html
What JDK are you developing against? -- 1.4.2 But not crucial
What is you platform? -- What do you mean by that?
By platform
Parsons Technical Services wrote:
At this point it looks like tomcat 5 will handle your needs
Look at this for cgi:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cgi-howto.html
Although it could be done like this, if you have some Apache experience,
I'd recommend Apache in front of Tomcat
Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is
the prefered way to link apache2 to tomcat[45])
I would suggest using tomcat 4 for now if you are going immediately into
a production environment where you have to abide by a server level
agreement. Otherwise use tomcat 5.
The reason I must keep using apache 1.3 is because I have been unable to
get remoteUser() from apache2. I have used identicle settings for mod_jk
with both apache 1.3 and 2.x. With apache 1.3 I can get remoteUser()
with apache 2.x I cannot. I need remoteUser() for my web applications to
work.
Great, let's use JK2
My experience:
rant-mode
tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz
cd jakarta-tomcat-connectors-jk2-2.0.4-src/
less README.txt - gibberish, doesn't help me much
less RELEASE-NOTES.txt
--
Sad but true. Why DON'T the ant build files work? Did someone get lazy? Is
JK2 part of a source tree that we're only getting a portion of when we
download the source tarball?
Great, let's use JK2
My experience:
rant-mode
tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz
Hi Michiel !
Cut the developers some slack, man ! Writing the software is difficult
enough, if you need to do a buildfile, test it and document it, it can
seem like a monstrous commitment. If you want instructions on getting it
built, I just updated my Tomcat 5 document to cover jk2.0.4. The
: the pain of choice
Great, let's use JK2
My experience:
rant-mode
tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz
cd jakarta-tomcat-connectors-jk2-2.0.4-src/
less README.txt - gibberish, doesn't help me much
less RELEASE-NOTES.txt
Strange you saying that if everyday I see so many problems and bugs in
jk2...
A question : jk2 can use the same mod_jk.config used by jk?
question 2 : I've asked before but here it goes :
- How can I make tomcat generate the mod_jk.conf withou those
virtualhost tag? this makes apache
once I got jk2 build to work...
I remember having to create dirs and copy files by hand...
[]s
Emerson
to Greg Adams wrote:
Sad but true. Why DON'T the ant build files work? Did someone get lazy? Is
JK2 part of a source tree that we're only getting a portion of when we
download the source tarball?
Chris,
I hope you got enough information to help you decide. It seems this thread
has taken on a life of its own and pushed the boundaries of being on topic
for the thread. Anyway, if you have any further questions or if anyone can
see any pitfalls please advise.
If you still need Apache for
I don't know if you will get much response with this request. What you may
wish to do is define your requirements for your application and environment.
Then set back and take in all the opinions on which way is best. Here are a
few questions to start with:
What JDK are you developing against?
14 matches
Mail list logo
