I thought BSE was "Being So E___", but I could not think of a word starting with E that fit the context.
Bad School English? You write better than most of what I read here, on Slashdot, or even from ZDNet's "professionals". Many cannot spell or capitalize, and I have wasted much time figuring out what people were trying to say. I have no issues with your writing. --- I looked at: http://lenya.apache.org/1_2_x/components/search/lucene.html It is inconsistent. It is likely nobody sees the end of the ant commands because they extend past the screen. (It needs to be formatted better.) crawler-live.xconf vs. crawler.xconf: Use either filename, but be consistent with the ant command. I cannot think why someone would bother indexing the authoring area. "Oh, I just made a change, didn't publish it, and cannot remember where it is! (But I remember enough text for a successful search.)" I cannot imagine that happening often enough (or ever) to waste time setting up indexing of the authoring area. --- (I lied about not helping.) http://excalibur.apache.org/ Good Code. Smart Developers. Maybe. I could not find this code on the Excalibur website, so it was probably discarded. The code below was decompiled from the classes shipped in Lenya1.2.2. org.apache.avalon.excalibur.io.FileUtil public static String catPath(String lookupPath, String path) { int index = lookupPath.lastIndexOf("/"); String lookup = lookupPath.substring(0, index); String pth; for(pth = path; pth.startsWith("../"); pth = pth.substring(index)) { if(lookup.length() > 0) { index = lookup.lastIndexOf("/"); lookup = lookup.substring(0, index); } else { return null; } index = pth.indexOf("../") + 3; } return lookup + "/" + pth; } Twice they use lastIndexOf(), then immediately use the return value in substring without checking for -1 (not found). In C, this would cause weird memory errors. In Java, it throws an Exception. It would be caught if the programmers had a clue. Instead, the JRE complains and exits. English translation: Given lookupPath and path Remove after last "/" in lookupPath For every "../" at the beginning of path, remove it and after last "/" in lookupPath Return what remains of lookupPath and path. So ("a/b/c/d", "../../x") returns "a/x". If lookupPath does not have a slash, or there are more "../" in path than one less than the number of slashes in lookupPath, it crashes. This code is expecting slashes. I did not see any backslashes in your config to confuse it. Does your ant directory have 2 levels to go up? solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
