JSP Compilation
Hi all, i have a simple question for which i haven't found an answare by myself: why for the same JSP page tomcat generate a new java/class file in work dir for every modification ?
Encoding URL
Hi all. Can anyone explain me a thing about using RequestDispatcher ? If cookies are disable and i use encodeURL to be sure to include "jsessionid" into url, is it correct that using "RequestDispatcher.forward" the url is not changed, so it does not include jsessionid (this happen to me with tomcat 3.2.1, when my servlet call a jsp to expose results) ? Right way is to use "sendRedirect" (this mean a roundtrip to the web browser) ? it's not verygood... Other way ? Thanks in advance. Max
Tabs vs. spaces (was: cvs commit: blah blah blah)
Jon Stevens typed the following on 06:50 PM 4/10/2001 -0700 Craig, does this mean you (finally) aren't using tabs anymore? :-) So, are spaces kosher? The Sun coding standards document (which is the official Jakarta guideline?) says either is OK, but the mixed tabs and spaces format I've found in the Catalina code I've mucked with is a PITA. Can I just set my editor to use 4 spaces for tabs and reformat files I work with accordingly, without spawning a jihad? Kief
RE: Tabs vs. spaces (was: cvs commit: blah blah blah)
Here's an edited version of a comment on tabs and spaces I sent to our development team that might be useful. ---cut--- Okay, we've had some discussions this morning, and we've got to deal with tabs and indentation better than we have been. Some files are simply unviewable right now in various editors with various settings, and it is time to clean it all up and do it right. First, there is a distinction between *tab stops* and *indentation*. The tab stops define how the editor interprets a tab character in the file---how many space-equivalents that tab character gives. The indentation defines how many spaces a nested level should be indented compared to the previous level. Most editors (including vim and emacs) use the *indentation*, not the tab stops, in interpreting how much whitespace to introduce when the user hits the tab key. That is, when the user hits the tab key, some number of spaces or tabs will be inserted to match the indentation. Most modern editors (including emacs and vi) support both concepts. Unfortunately, most modern programmers (including most of us) only understand the tab stop concept. This is broken. Finally, many programs, printers, and so forth are hard-wired to use 8-character tab stops, and there is often no way to work around this. There is a clean solution. It's simple and it's elegant and it's easy. The rules are as follows. 1. Never ever set your tab stops to something other than 8. This means, never do (setq tab-width 4) in emacs or set tabstop=4 in vim. If you do, you will create files that will be unusable by others. 2. Instead, set your indentation to whatever you want, as the author of a file. This is usually done with (setq c-basic-indent 4) in emacs, or set softtabstop=4 in vim. This is what you want to do, and if you do this, your files will work well with everyone. 3. If you want, in your files, add a line such as /* -*- mode: java; c-basic-indent: 4; -*- */ to force all other emacs users to get *your* desired indentation so that if they edit your files, their new lines will match your indentation. 4. I would prefer that none of our source files contain any tab characters at all since this is what causes the files to display incorrectly in the different editors, but I'm not going to insist on this. To do this, in emacs use (setq indent-tabs-mode nil); in vim use set expandtab. If everyone does as in 1 above, there won't be a problem in any case. If you encounter a file that just doesn't display properly for you, it's probably got a mixture of tabs and spaces and your tab stop is set differently than (one of the) authors'. This is the crux of the problem. To fix this, you can set the tab stop of your editor until it looks most proper, then untabify it (in emacs, untabify; in vi, set expandtab) and save out the file with no tabs. Then fix up any remaining indentation problems by hand and check it in. Unfortunately, the changes will be massive by perforce standards, but it's probably best to deal with this as early as possible, set the standard now, and totally prevent problems in the future. For further reference, consult http://www.jwz.org/doc/tabs-vs-spaces.html If anyone has any questions or further discussion is needed, contact me. -tom -Original Message- From: Kief Morris [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:43 AM To: [EMAIL PROTECTED] Subject: Tabs vs. spaces (was: cvs commit: blah blah blah) Jon Stevens typed the following on 06:50 PM 4/10/2001 -0700 Craig, does this mean you (finally) aren't using tabs anymore? :-) So, are spaces kosher? The Sun coding standards document (which is the official Jakarta guideline?) says either is OK, but the mixed tabs and spaces format I've found in the Catalina code I've mucked with is a PITA. Can I just set my editor to use 4 spaces for tabs and reformat files I work with accordingly, without spawning a jihad? Kief
Re: Tabs vs. spaces (was: cvs commit: blah blah blah)
On Thu, 12 Apr 2001, Kief Morris wrote: Jon Stevens typed the following on 06:50 PM 4/10/2001 -0700 Craig, does this mean you (finally) aren't using tabs anymore? :-) So, are spaces kosher? The Sun coding standards document (which is the official Jakarta guideline?) says either is OK, but the mixed tabs and spaces format I've found in the Catalina code I've mucked with is a PITA. Can I just set my editor to use 4 spaces for tabs and reformat files I work with accordingly, without spawning a jihad? Kief Spaces are definitely kosher for Tomcat code. The coding standards document does say either is OK, and prior to about nine months ago I didn't care (Emacs took care of the details for me when I pressed the TAB key once). At that point, I switched to space-fill -- but of course lots of the Catalina code preceeded that change. If you want to change a source file that you're currently working on, I would say go for it. A suggestion, though, would be to do the untabify change as a single commit (with a message like "cosmetic change only, no functional change") so that we can still clearly identify functional changes in the other commits. Craig
Re: Tabs vs. spaces (was: cvs commit: blah blah blah)
On Thu, 12 Apr 2001, Kief Morris wrote: Jon Stevens typed the following on 06:50 PM 4/10/2001 -0700 Craig, does this mean you (finally) aren't using tabs anymore? :-) So, are spaces kosher? The Sun coding standards document (which is the official Jakarta guideline?) says either is OK, but the mixed tabs and spaces format I've found in the Catalina code I've mucked with is a PITA. Can I just set my editor to use 4 spaces for tabs and reformat files I work with accordingly, without spawning a jihad? Kief One more note on this, even if you are using spaces for indentation, the indentation interval for Tomcat code should be four spaces. Craig
RE: Tabs vs. spaces (was: cvs commit: blah blah blah)
This issue would be moot if you frontended your CVS checkins with a beautifier. Here's an edited version of a comment on tabs and spaces I sent to our development team that might be useful. ---cut--- -- Nick Bauman Software Developer 3023 Lynn #22 Minneapolis, MN 55416 Mobile Phone: (612) 810-7406
Re: JSP Compilation
on 4/12/01 3:46 AM, "Luise Massimo" IMCEAEX-_O=COMPUTER+20CENTER+20ORG_OU=COMPUTER+20CENTER+20SITE_CN=RECIPIENT [EMAIL PROTECTED] wrote: Hi all, i have a simple question for which i haven't found an answare by myself: why for the same JSP page tomcat generate a new java/class file in work dir for every modification ? http://jakarta.apache.org/velocity/ymtd/ymtd-generation.html -jon -- If you come from a Perl or PHP background, JSP is a way to take your pain to new levels. --Anonymous http://jakarta.apache.org/velocity/ymtd/ymtd.html
Re: Tabs vs. spaces (was: cvs commit: blah blah blah)
on 4/12/01 8:43 AM, "Kief Morris" [EMAIL PROTECTED] wrote: So, are spaces kosher? The Sun coding standards document (which is the official Jakarta guideline?) says either is OK, but the mixed tabs and spaces format I've found in the Catalina code I've mucked with is a PITA. Can I just set my editor to use 4 spaces for tabs and reformat files I work with accordingly, without spawning a jihad? Kief You can read what it says on the website... http://jakarta.apache.org/site/source.html -jon
RE: Tabs vs. spaces (was: cvs commit: blah blah blah)
True; not using a beautifier or CVS (now we're using Perforce). I find that beautifiers do more damage than good, but I'm happy to be enlightened; is anyone actually doing this in practice? -tom -Original Message- From: Nick Bauman [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 9:34 AM To: [EMAIL PROTECTED] Subject: RE: Tabs vs. spaces (was: cvs commit: blah blah blah) This issue would be moot if you frontended your CVS checkins with a beautifier. Here's an edited version of a comment on tabs and spaces I sent to our development team that might be useful. ---cut--- -- Nick Bauman Software Developer 3023 Lynn #22 Minneapolis, MN 55416 Mobile Phone: (612) 810-7406
Re: JSP Compilation
On Thu, 12 Apr 2001, Luise Massimo wrote: Hi all, i have a simple question for which i haven't found an answare by myself: why for the same JSP page tomcat generate a new java/class file in work dir for every modification ? Reloading issues. "Normal" reloading ( that is used for regular servlets ) is implemented by replacing the ClassLoader ( after you load a class with a class loader, you just can't load a newer version ). This creates a number of problems - all other servlets and classes must be reloaded, session objects and attributes must also be reloaded ( class loaders define separate namespaces, objects loaded with sibling loaders can't communicate ). Jasper ( and any other system that generates servlets ) has another option - to generate a new class name and use the old loader. Given that JSPs are typically modified many times this saves a lot of overhead. This is not an absolute requirement - it's easy to change jasper to use the "servlet" reloading mechanism ( unfortunately you can't use versioning on regular servlets - since the class name is fixed ). Costin
RE: Tabs vs. spaces (was: cvs commit: blah blah blah)
My company is, for a team of about 15+ people. We use JIndent on .java files. Works great. If it's doing damage, then it misconfigured. True; not using a beautifier or CVS (now we're using Perforce). I find that beautifiers do more damage than good, but I'm happy to be enlightened; is anyone actually doing this in practice? -tom -Original Message- From: Nick Bauman [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 9:34 AM To: [EMAIL PROTECTED] Subject: RE: Tabs vs. spaces (was: cvs commit: blah blah blah) This issue would be moot if you frontended your CVS checkins with a beautifier. Here's an edited version of a comment on tabs and spaces I sent to our development team that might be useful. ---cut--- -- Nick Bauman Software Developer 3023 Lynn #22 Minneapolis, MN 55416 Mobile Phone: (612) 810-7406 -- Nick Bauman Software Developer 3023 Lynn #22 Minneapolis, MN 55416 Mobile Phone: (612) 810-7406
Re: Tabs vs. spaces (was: cvs commit: blah blah blah)
Please, don't start this ( again ). You can read the archives ( every six months some smart people ask this question ), or check other mailing lists for the same question. Use whatever other people are using in that project. In tomcat you'll notice the 4 space indentation, and 09 ( TAB ) is used in many (most) files. Changing a file from 09 ( TAB ) to spaces ( or reverse ) is _bad_, it is (IMHO) lack of respect for the people who wrote the original code. It may be better to use only spaces for new code you write - but at least in tomcat this is not required ( I do use 09 in most code I write for example, and so far nobody -1 a commit I made for this reason ). Costin On Thu, 12 Apr 2001, Kief Morris wrote: Jon Stevens typed the following on 06:50 PM 4/10/2001 -0700 Craig, does this mean you (finally) aren't using tabs anymore? :-) So, are spaces kosher? The Sun coding standards document (which is the official Jakarta guideline?) says either is OK, but the mixed tabs and spaces format I've found in the Catalina code I've mucked with is a PITA. Can I just set my editor to use 4 spaces for tabs and reformat files I work with accordingly, without spawning a jihad? Kief
RE: Tabs vs. spaces (was: cvs commit: blah blah blah)
I believe this topic has been hashed out enough. Can we move on. Todd -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 12:11 PM To: [EMAIL PROTECTED] Subject: Re: Tabs vs. spaces (was: cvs commit: blah blah blah) Please, don't start this ( again ). You can read the archives ( every six months some smart people ask this question ), or check other mailing lists for the same question. Use whatever other people are using in that project. In tomcat you'll notice the 4 space indentation, and 09 ( TAB ) is used in many (most) files. Changing a file from 09 ( TAB ) to spaces ( or reverse ) is _bad_, it is (IMHO) lack of respect for the people who wrote the original code. It may be better to use only spaces for new code you write - but at least in tomcat this is not required ( I do use 09 in most code I write for example, and so far nobody -1 a commit I made for this reason ). Costin On Thu, 12 Apr 2001, Kief Morris wrote: Jon Stevens typed the following on 06:50 PM 4/10/2001 -0700 Craig, does this mean you (finally) aren't using tabs anymore? :-) So, are spaces kosher? The Sun coding standards document (which is the official Jakarta guideline?) says either is OK, but the mixed tabs and spaces format I've found in the Catalina code I've mucked with is a PITA. Can I just set my editor to use 4 spaces for tabs and reformat files I work with accordingly, without spawning a jihad? Kief
Re: Tabs vs. spaces (was: cvs commit: blah blah blah)
[EMAIL PROTECTED] typed the following on 09:11 AM 4/12/2001 -0700 Changing a file from 09 ( TAB ) to spaces ( or reverse ) is _bad_, it is (IMHO) lack of respect for the people who wrote the original code. I take your point about respect for the people who wrote the original code, (and the other developers working on it) which is why I brought it up - not because I wanted to resurrect an old holy war on an extremely dull topic. The only files I'm changing are the ones I'm doing a lot of work on, the session classes in Catalina 4. The original author, Craig has said he doesn't mind. I have no interest in mucking with any other files, I can deal with whatever spacing they already have. Anyway, I don't want to carry this thread on, but figured I ought to justify the changes I made, and reassure that I'm not going to go nuts mangling other files. Kief
Fwd: failure notice
Since the commit message was too big for qmail, anyone interested can check it manually. Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Date: 12 Apr 2001 18:19:02 - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: failure notice Hi. This is the qmail-send program at apache.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: ezmlm-reject: fatal: Sorry, I don't accept messages larger than 10 bytes (#5.2.3) --- Below this line is a copy of the message. Return-Path: [EMAIL PROTECTED] Received: (qmail 15613 invoked by uid 500); 12 Apr 2001 18:19:02 - Delivered-To: [EMAIL PROTECTED] Received: (qmail 15543 invoked by uid 1255); 12 Apr 2001 18:19:01 - Date: 12 Apr 2001 18:19:01 - Message-ID: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session StandardSession.java StandardManager.java PersistentManager.java ManagerBase.java FileStore.java kief01/04/12 11:19:01 Modified:catalina/src/share/org/apache/catalina/session StandardSession.java StandardManager.java PersistentManager.java ManagerBase.java FileStore.java Log: Cosmetic changes only: replaced tabs with spaces.
Re: JSP Compilation
[EMAIL PROTECTED] wrote: On Thu, 12 Apr 2001, Luise Massimo wrote: Hi all, i have a simple question for which i haven't found an answare by myself: why for the same JSP page tomcat generate a new java/class file in work dir for every modification ? Reloading issues. "Normal" reloading ( that is used for regular servlets ) is implemented by replacing the ClassLoader ( after you load a class with a class loader, you just can't load a newer version ). This creates a number of problems - all other servlets and classes must be reloaded, session objects and attributes must also be reloaded ( class loaders define separate namespaces, objects loaded with sibling loaders can't communicate ). Jasper ( and any other system that generates servlets ) has another option - to generate a new class name and use the old loader. Given that JSPs are typically modified many times this saves a lot of overhead. This is not an absolute requirement - it's easy to change jasper to use the "servlet" reloading mechanism ( unfortunately you can't use versioning on regular servlets - since the class name is fixed ). Costin Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer uses the .java/.class versioning system because it uses a URLClassLoader for each JSP page compiled into a servlet. That way if the page is recompiled the URLClassLoader for the JSP page itself can be dumped without affecting the rest of the Context. Regards, Glenn -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | --
Re: JSP Compilation
on 4/12/01 12:01 PM, "Glenn Nielsen" [EMAIL PROTECTED] wrote: Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer uses the .java/.class versioning system because it uses a URLClassLoader for each JSP page compiled into a servlet. That way if the page is recompiled the URLClassLoader for the JSP page itself can be dumped without affecting the rest of the Context. Regards, Glenn YES! -jon
Re: JSP Compilation
On Thu, 12 Apr 2001, Glenn Nielsen wrote: Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer uses the .java/.class versioning system because it uses a URLClassLoader for each JSP page compiled into a servlet. That way if the page is recompiled the URLClassLoader for the JSP page itself can be dumped without affecting the rest of the Context. It is a very good solution, I remember it was used ( long ago ) for servlets as well ( before tomcat ). ( messing with class loaders is something I try to avoid, that's why I prefer explicit versioning - but this should work in most cases as JSPs don't call each other directly and are not called directly from other components ). That's the whole point of refactoring jasper and separating the components - allow multiple schemes to coexist and be easily configured. So far there are 4 reloading mechansims jasper could use: - no name versioning, use the normal servlet reloading - no name versioning, one class loader per jsp - name versioning using a single .class file ( and special class loader) - name versioning and normal (URL)ClassLoader. There are also 3-4 name "mangling" schemes, etc. Flexibility and choice are good. Costin
Re[2]: JSP Compilation
Hello Jon, Do you know how do I unsubscribe from the list? Thursday, April 12, 2001, 3:11:04 PM, you wrote: JS on 4/12/01 12:01 PM, "Glenn Nielsen" [EMAIL PROTECTED] wrote: Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer uses the .java/.class versioning system because it uses a URLClassLoader for each JSP page compiled into a servlet. That way if the page is recompiled the URLClassLoader for the JSP page itself can be dumped without affecting the rest of the Context. Regards, Glenn JS YES! JS -jon -- Best regards, Gazizmailto:[EMAIL PROTECTED]
Re[2]: JSP Compilation
Hello Glenn, Do you know how do I unsubscribe from the list? Thursday, April 12, 2001, 3:01:58 PM, you wrote: GN [EMAIL PROTECTED] wrote: On Thu, 12 Apr 2001, Luise Massimo wrote: Hi all, i have a simple question for which i haven't found an answare by myself: why for the same JSP page tomcat generate a new java/class file in work dir for every modification ? Reloading issues. "Normal" reloading ( that is used for regular servlets ) is implemented by replacing the ClassLoader ( after you load a class with a class loader, you just can't load a newer version ). This creates a number of problems - all other servlets and classes must be reloaded, session objects and attributes must also be reloaded ( class loaders define separate namespaces, objects loaded with sibling loaders can't communicate ). Jasper ( and any other system that generates servlets ) has another option - to generate a new class name and use the old loader. Given that JSPs are typically modified many times this saves a lot of overhead. This is not an absolute requirement - it's easy to change jasper to use the "servlet" reloading mechanism ( unfortunately you can't use versioning on regular servlets - since the class name is fixed ). Costin GN Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer GN uses the .java/.class versioning system because it uses a URLClassLoader for GN each JSP page compiled into a servlet. That way if the page is recompiled GN the URLClassLoader for the JSP page itself can be dumped without affecting GN the rest of the Context. GN Regards, GN Glenn GN -- GN Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| GN MOREnet System Programming | * if iz ina coment. | GN Missouri Research and Education Network | */ | GN -- -- Best regards, Gazizmailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session PersistentManager.java
kief01/04/12 13:24:38
Modified:catalina/src/share/org/apache/catalina/session
PersistentManager.java
Log:
Fixed an error I made in applying Bip's patch which had neutered the
backup() method.
Revision ChangesPath
1.6 +12 -16
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/PersistentManager.java
Index: PersistentManager.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/PersistentManager.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- PersistentManager.java2001/04/12 18:18:57 1.5
+++ PersistentManager.java2001/04/12 20:24:36 1.6
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/PersistentManager.java,v
1.5 2001/04/12 18:18:57 kief Exp $
- * $Revision: 1.5 $
- * $Date: 2001/04/12 18:18:57 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/PersistentManager.java,v
1.6 2001/04/12 20:24:36 kief Exp $
+ * $Revision: 1.6 $
+ * $Date: 2001/04/12 20:24:36 $
*
*
*
@@ -106,7 +106,7 @@
* liLimit the number of active sessions kept in memory by
* swapping less active sessions out to disk./li
*
- * @version $Revision: 1.5 $
+ * @version $Revision: 1.6 $
* @author Kief Morris ([EMAIL PROTECTED])
*/
@@ -376,7 +376,7 @@
if (this.minIdleSwap == min)
return;
int oldMinIdleSwap = this.minIdleSwap;
-this.minIdleSwap = min;
+this.minIdleSwap = min;
support.firePropertyChange("minIdleSwap",
new Integer(oldMinIdleSwap),
new Integer(this.minIdleSwap));
@@ -471,8 +471,9 @@
/**
* Load any currently active sessions that were previously unloaded
- * to the appropriate persistence mechanism, if any. If persistence is not
- * supported, this method returns without doing anything.
+ * or backed up to the appropriate persistence mechanism, if any.
+ * If persistence is not supported, this method returns without doing
+ * anything.
*
* @exception ClassNotFoundException if a serialized class cannot be
* found during the reload
@@ -498,7 +499,6 @@
}
return;
-
}
String[] ids = store.keys();
@@ -700,7 +700,6 @@
if (isSessionStale(session, timeNow))
session.expire();
}
-
}
@@ -896,18 +895,15 @@
|| isSessionStale(session, System.currentTimeMillis()))
return;
+try {
+store.save(session);
+} catch (IOException e) {
+log(sm.getString
+("persistentManager.serializeError", session.getId(), e));
+throw e;
+}
+
}
-
-
-/**
- * Read the session in from Store, overriding the copy in
- * the Manager's memory.
- */
-//private void recover() throws IOException {
-
-// FIXME: Do something
-
-//}
/**
Re: JSP Compilation
Jon Stevens wrote: on 4/12/01 12:01 PM, "Glenn Nielsen" [EMAIL PROTECTED] wrote: Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer uses the .java/.class versioning system because it uses a URLClassLoader for each JSP page compiled into a servlet. That way if the page is recompiled the URLClassLoader for the JSP page itself can be dumped without affecting the rest of the Context. Regards, Glenn YES! -jon Are you feeling ok jon? Your resounding "YES!" above could be interpreted as support for JSP. ;-) Regards, Glenn -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | --
Re: JSP Compilation
on 4/12/01 1:25 PM, "Glenn Nielsen" [EMAIL PROTECTED] wrote: Are you feeling ok jon? Your resounding "YES!" above could be interpreted as support for JSP. ;-) Yea, I just feel bad for all the poor lusers out there that have to use JSP because Sun or someone else pushed it down their CTO's throat. :-) Here is my favorite quote today: On the Velocity list: I must say, Velocity has it ALL over JSP. I've converted several large, gnarly JSPs so far, and the Velocity code is so much cleaner and easy to follow. With a good "pull" context and Velocity macros, taglibs are passe IMO. :-) HTH. -scott :-) -jon
Sun Seeking Experts for New Java Certification!
on the 28/03/2001 there was a mail titled : Sun Seeking Experts for New Java Certification! I could not find it back in the archived, could someone re - send it to me ? thanks ;)
building mod_jk
In using the
jakarta-tomcat/src/native/mod_jk/apache1.3/build-unix.sh script to build
mod_jk, I notice it works only on linux.
It turns out that the version of find on Solaris doesn't have the
-printf option.
After some experimenting it looks like
# use "find" to pick the right include directories for current machine
JAVA_INCLUDE="`find ${JAVA_HOME}/include -type d -printf \"-I %p \"`"
|| echo "find failed, edit build-unix.sh source to fix"
should be replaced by:
JAVA_INCLUDE="`find ${JAVA_HOME}/include -type d -exec echo -I {} \;`"
|| echo "find failed, edit build-unix.sh source to fix"
This seems to work fine on both linux and solaris (and -exec is a
more standard option to find I believe).
Jason
--
Jason Novotny [EMAIL PROTECTED]
Home: (510) 549-0574Work: (510) 486-8662
NERSC Distributed Computing http://www-didc.lbl.gov
