Re: Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-23 Thread Tim Stewart

First let me say sorry for lurking and responding to this message 5 days
late.  I think your suggestions are very good. I also recently went through
hell trying to get mod_jk2 setup in IIS then Apache and have some
suggestions for the docs.  Is there anyway we can setup a WIKI for mod_jk2,
that way people who have suggestions for documentation can just add it?

Do WIKIs exist in the ASF?

Tim


- Original Message - 
From: Daniel Savard [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 19, 2004 9:53 PM
Subject: Re: Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK
2.0.4]


 --- Guenter Knauf [EMAIL PROTECTED] wrote:
 other content deleted
 I would like to see some
  feedback from those admins who have to install the connectors what
 they would
  prefer.
 
 A quick start covering:
 - What to download
 - What to compile
 - Compatible Apache versions
 - Which folder to copy files into
 - What entries does Apache expect
 - What workers and MPM are and how we can configure them
 
  thanks, Guenter.
 
 -- Sriram

 Well, given my recent trauma, oups experience, setting up mod_jk2, may I
 suggest a few things?

 - A working configure script. Let me explain what I expect from a
 configure script. It should check all requirements are met including
 proper versions and not require more than necessary (for example, if
 Berkley BD version 2.5 and up is fine, do not insist on version 4.0
 because it may have some cascading effect on my system and if not
 necessary, why should someone insist I upgrade 50% of the packages on
 the system?)

 - Working Makefiles. This is a side effect of a working configure
 script. Given proper checking and identification of the system, the
 proper Makefiles should be build. This include the appropriate list of
 libraries I should link to in order to have working modules. To make
 things clear, I should never get undefined symbols at runtime because
 the Makefile never specified a complete list of libraries required to
 resolve all the symbols in my module and the module has no hint on where
 it should look for the undefined symbols to get them resolved. The
 sysadmin is not supposed to be a developper (even if it happens it's not
 always true) and don't expect him to manually edit the Makefile to make
 it working with his system. If the configure cannot find the libraries,
 it means they are not installed or the user didn't specified the correct
 options to configure (library paths, if any) and it should be catch at
 the configure step, not at runtime.

 - A comprehensive guide of the configuration options (properties), not
 necessarily something lengthy, but enough to figure out what is the
 purpose of each configuration option and how it is used.

 - Don't make any RPMS available if it is not possible to guarantee they
 will provide a working system. Instead, with limited man-power and time,
 I think it will be a better move to invest in a clean, documented,
 straight forward building process with consistent results.

 This should reduce drastically the number of redundant questions on the
 Tomcat-user mailing list (including mines).



 -- 

 ===
 Daniel Savard
 Consultation Informatique Daniel Savard
 551, boul. Sir-Wilfrid-Laurier
 suite 105
 Beloeil, (Québec)
 Canada J3G 4J1

 Tél: (450) 467-8014
 Internet: [EMAIL PROTECTED]
 ===



 -
 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]



Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-23 Thread Tim Funk
The faq uses the wiki for some stuff. Feel free to add content there.

http://jakarta.apache.org/tomcat/faq/

-Tim

Tim Stewart wrote:
First let me say sorry for lurking and responding to this message 5 days
late.  I think your suggestions are very good. I also recently went through
hell trying to get mod_jk2 setup in IIS then Apache and have some
suggestions for the docs.  Is there anyway we can setup a WIKI for mod_jk2,
that way people who have suggestions for documentation can just add it?
Do WIKIs exist in the ASF?

Tim

- Original Message - 
From: Daniel Savard [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 19, 2004 9:53 PM
Subject: Re: Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK
2.0.4]



--- Guenter Knauf [EMAIL PROTECTED] wrote:
other content deleted
I would like to see some
feedback from those admins who have to install the connectors what
they would

prefer.
A quick start covering:
- What to download
- What to compile
- Compatible Apache versions
- Which folder to copy files into
- What entries does Apache expect
- What workers and MPM are and how we can configure them

thanks, Guenter.

-- Sriram
Well, given my recent trauma, oups experience, setting up mod_jk2, may I
suggest a few things?
- A working configure script. Let me explain what I expect from a
configure script. It should check all requirements are met including
proper versions and not require more than necessary (for example, if
Berkley BD version 2.5 and up is fine, do not insist on version 4.0
because it may have some cascading effect on my system and if not
necessary, why should someone insist I upgrade 50% of the packages on
the system?)
- Working Makefiles. This is a side effect of a working configure
script. Given proper checking and identification of the system, the
proper Makefiles should be build. This include the appropriate list of
libraries I should link to in order to have working modules. To make
things clear, I should never get undefined symbols at runtime because
the Makefile never specified a complete list of libraries required to
resolve all the symbols in my module and the module has no hint on where
it should look for the undefined symbols to get them resolved. The
sysadmin is not supposed to be a developper (even if it happens it's not
always true) and don't expect him to manually edit the Makefile to make
it working with his system. If the configure cannot find the libraries,
it means they are not installed or the user didn't specified the correct
options to configure (library paths, if any) and it should be catch at
the configure step, not at runtime.
- A comprehensive guide of the configuration options (properties), not
necessarily something lengthy, but enough to figure out what is the
purpose of each configuration option and how it is used.
- Don't make any RPMS available if it is not possible to guarantee they
will provide a working system. Instead, with limited man-power and time,
I think it will be a better move to invest in a clean, documented,
straight forward building process with consistent results.
This should reduce drastically the number of redundant questions on the
Tomcat-user mailing list (including mines).


--

===
Daniel Savard
Consultation Informatique Daniel Savard
551, boul. Sir-Wilfrid-Laurier
suite 105
Beloeil, (Québec)
Canada J3G 4J1
Tél: (450) 467-8014
Internet: [EMAIL PROTECTED]
===


-
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]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-19 Thread Daniel Savard
--- Guenter Knauf [EMAIL PROTECTED] wrote:
other content deleted
I would like to see some
 feedback from those admins who have to install the connectors what
they would
 prefer.

A quick start covering:
- What to download
- What to compile
- Compatible Apache versions
- Which folder to copy files into
- What entries does Apache expect
- What workers and MPM are and how we can configure them

 thanks, Guenter.
 
-- Sriram

Well, given my recent trauma, oups experience, setting up mod_jk2, may I
suggest a few things?

- A working configure script. Let me explain what I expect from a
configure script. It should check all requirements are met including
proper versions and not require more than necessary (for example, if
Berkley BD version 2.5 and up is fine, do not insist on version 4.0
because it may have some cascading effect on my system and if not
necessary, why should someone insist I upgrade 50% of the packages on
the system?)

- Working Makefiles. This is a side effect of a working configure
script. Given proper checking and identification of the system, the  
proper Makefiles should be build. This include the appropriate list of
libraries I should link to in order to have working modules. To make
things clear, I should never get undefined symbols at runtime because
the Makefile never specified a complete list of libraries required to
resolve all the symbols in my module and the module has no hint on where
it should look for the undefined symbols to get them resolved. The
sysadmin is not supposed to be a developper (even if it happens it's not
always true) and don't expect him to manually edit the Makefile to make
it working with his system. If the configure cannot find the libraries,
it means they are not installed or the user didn't specified the correct
options to configure (library paths, if any) and it should be catch at
the configure step, not at runtime.

- A comprehensive guide of the configuration options (properties), not
necessarily something lengthy, but enough to figure out what is the
purpose of each configuration option and how it is used.

- Don't make any RPMS available if it is not possible to guarantee they
will provide a working system. Instead, with limited man-power and time,
I think it will be a better move to invest in a clean, documented,
straight forward building process with consistent results.

This should reduce drastically the number of redundant questions on the
Tomcat-user mailing list (including mines).



-- 

===
Daniel Savard
Consultation Informatique Daniel Savard
551, boul. Sir-Wilfrid-Laurier
suite 105
Beloeil, (Québec)
Canada J3G 4J1

Tél: (450) 467-8014
Internet: [EMAIL PROTECTED]
===



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-17 Thread Henri Gomez
Hi to all,

Did some of you, JFC, Mladen, Guenter, Kurt, Norm could works on
a little HOWTO (text based will be suffisant) for jk2, explaining
how to set up jk2 in IIS and Apache 2 web-servers ?
It could be added to the release and will help remove tons of
questions from tomcat-users :)
Volunteers welcome (I can't work on it right now)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-17 Thread Mladen Turk
 

 -Original Message-
 From: Henri Gomez
 
 Did some of you, JFC, Mladen, Guenter, Kurt, Norm could works 
 on a little HOWTO (text based will be suffisant) for jk2, 
 explaining how to set up jk2 in IIS and Apache 2 web-servers ?
 
 It could be added to the release and will help remove tons of 
 questions from tomcat-users :)


Just commited INSTALL.txt

I'll add quick IIS howto.

Can we update the CHANGES too?

 MT.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-17 Thread Henri Gomez
Mladen Turk wrote:

 


-Original Message-
From: Henri Gomez
Did some of you, JFC, Mladen, Guenter, Kurt, Norm could works 
on a little HOWTO (text based will be suffisant) for jk2, 
explaining how to set up jk2 in IIS and Apache 2 web-servers ?

It could be added to the release and will help remove tons of 
questions from tomcat-users :)



Just commited INSTALL.txt

I'll add quick IIS howto.

Can we update the CHANGES too?
Of course :)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-17 Thread Guenter Knauf
Hi all,
probably now I get the -1's back, but nevertheless I'll give it a try...!

 Did some of you, JFC, Mladen, Guenter, Kurt, Norm could works on
 a little HOWTO (text based will be suffisant) for jk2, explaining
 how to set up jk2 in IIS and Apache 2 web-servers ?

 It could be added to the release and will help remove tons of
 questions from tomcat-users :)

 Volunteers welcome (I can't work on it right now)
hmm, I think Norm has already offered that he's more than willing to improve the 
Apache2 docu; 
and in addition he has already put together such an document in html for NetWare, and 
I modified it slighty for Win32 (I linked to recently).
But since we have to deal with a lot of terms which are almost not or insuffient 
explained, I think we should all here put the heads together, specially also those 
which have started with the initial mod_jk2 project, so that we can find proper 
descriptions of all those terms which also f.e. appear on the jkstatus pages.
While I digged last time through BugZilla, I also have read a bunch of cvs commit logs 
to understand why what was changed, changed then back and so on; and I got the strong 
feeling that even those who have commited the changes often only did what users 
requested, but didnt know for sure what's right and what's wrong behaviour.
What I have heard a lot is 'read the code', but that isnt allways the best answer, its 
useless to read the code and understand what's going on unless you know from a docu 
what's right and what's wrong behaviour; we all should know what the module _should_ 
do before we try to archive that.
I've forwarded a html document to Henri and Mladen which Norm has created, and we all 
are not able to answer the questions fully and decribe what the terms really mean. 
Norm will be online in about 1 hour (Australia), and I hope he agrees that we make his 
document here available
It would be very great if all here familar with the connector stuff could clarify 
this, so that we have a good starting point for any further documentation. I believe 
that we in one day could put all info together if everyone reads this document with 
the terms in question, and posts what he thinks is the best description; and also I 
would like to get replies from all other non-commiters here if that what we put 
together is understandable at all.

something other we should perhaps also discuss is the format of the docu.
I think that it is most likely that someone who installs a web connector has also a 
web browser; and therefore I'm +1 for a html document; however everyone has certainly 
a text editor, and IIRC Henri and Mladen are +1 for plain text. Since it doesnt matter 
what we use, I would like to see some feedback from those admins who have to install 
the connectors what they would prefer.

thanks, Guenter.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Minimal HOWTO for jk2 2.0.4 - Was: [Fwd: Releasing JK 2.0.4]

2004-03-17 Thread Sriram N

--- Guenter Knauf [EMAIL PROTECTED] wrote:
other content deleted
I would like to see some
 feedback from those admins who have to install the connectors what they would
 prefer.

A quick start covering:
- What to download
- What to compile
- Compatible Apache versions
- Which folder to copy files into
- What entries does Apache expect
- What workers and MPM are and how we can configure them

 thanks, Guenter.
 
-- Sriram

__
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]