Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@apache.org Received: (qmail 80002 invoked from network); 29 Oct 2002 16:23:24 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Oct 2002 16:23:24 -0000 Received: (qmail 26527 invoked by uid 97); 29 Oct 2002 16:24:07 -0000 Delivered-To: qmlist-jakarta-archive-lucene-user@jakarta.apache.org Received: (qmail 26473 invoked by uid 97); 29 Oct 2002 16:24:04 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 26442 invoked by uid 98); 29 Oct 2002 16:24:03 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <399E1F52E73BD41194A800D0B74A08AB01E4DC8F@skipper.cincom.com> From: "Cox, Charlie" To: 'Lucene Users List' Subject: RE: Implement Lucene web-demo using Tomcat Date: Tue, 29 Oct 2002 11:20:38 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I reviewed the demo again(its been a while ;)) and it appears that the url(s) are relative to how you access the results page. Are you using http://server:8080/luceneweb/results.jsp to access the results page? if so, then try http://server/luceneweb/results.jsp - so that it goes though apache from the beginning and all your relative links should work. Charlie > -----Original Message----- > From: Brian Cuttler [mailto:brian@wadsworth.org] > Sent: Tuesday, October 29, 2002 9:29 AM > To: Lucene Users List > Subject: Re: Implement Lucene web-demo using Tomcat > > > > Charlie, > > The http://server:8080/luceneweb.war comes directly from the Lucene > demo howto. > > Its a java page that asks for a search string, number of entries > per page of output. > > The output pages contain page-summary information and URLs that are > of two parts, http://server:8080 - which I believe to be a result of > the server context, which is why I think I need to run the search > somehow from the server at port 80 (the apache server) rather than > the server at port 8080 (tomcat). > > The rest of the URL seems to be a result of the search of the > index file which I created via the Index demo java that also > came directly from the demo/howto. > > From what I can tell (also by running the Lucene indexsearch that > came with the software) the file paths are 100% correct, its 'just' > a matter of the java script providing an incorrect server identity. > > I've done NO coding at this level of the server. Everything we have > done on site is in the apache and tomcat config files. Plus running > a # java command to build the index of the file structure that is > being served by the apache server. > > > where do you get the URL? Is this a field you have stored > in lucene, or are > > you building the URL yourself? > > > > > -----Original Message----- > > > From: Brian Cuttler [mailto:brian@wadsworth.org] > > > Sent: Monday, October 28, 2002 4:12 PM > > > To: Lucene Users List > > > Cc: lucene-user@jakarta.apache.org > > > Subject: Re: Implement Lucene web-demo using Tomcat > > > > > > > > > > > > Peter, > > > > > > Not so much, no. > > > > > > http://server:8080/luceneweb.war > > > > > > It comes with the lucene package, I've not no other code there. > > > > > > I suspect I'm supposed to have some html code under > http://server:80 > > > and that the web connector code is supposed to take care of it but > > > I'm rather at a loss at that point. > > > > > > > Brian - > > > > > > > > But you are generating the links from your code and not > > > Lucene, right? > > > > So wouldn't this be just a modification to your code? > > > > > > > > Peter > > > > > > > > Brian Cuttler wrote: > > > > > > > > >Otis, > > > > > > > > > >I can access the web-page that implements the java based > > > > >search at the Tomcat port (port 8080). Inputting search > > > > >criteria pulls up the search hits, which are all valid > > > > >except for the server info, they give me host:8080 when > > > > >I really need host ( ie host:80). > > > > > > > > > >Putting the same java code - "luceneweb.war" under apache > > > > >server (port 80), well, it tries to display the java code > > > > >as text (looks like a hex dump of a binary). > > > > > > > > > > > > > > > > > > > >>Sounds like Tomcat/Apache config issue, which is > always a pain. > > > > >>Get the basic servlet working, and when you figure that > > > out your Lucene > > > > >>stuff should work, too. > > > > >>Make sure that the user that runs Tomcat can read the > index files. > > > > >> > > > > >>Otis > > > > >> > > > > >> > > > > >>--- Brian Cuttler wrote: > > > > >> > > > > >> > > > > >>>Tomcat and Lucene users, > > > > >>> > > > > >>>Hello, I am trying to implement the lucene search web demo > > > > >>>run under Tomcat 4.1.10, Lucene 1.2, Apache 1.3.27 on a > > > > >>>Solaris 8 system. > > > > >>> > > > > >>>I've been able to build the lucene index (I need to modify > > > > >>>the code to exclude *.txt, we only want to index the .htm > > > > >>>and .html files). > > > > >>> > > > > >>>I'm able to search the index with the command like Java code. > > > > >>> > > > > >>>I'm able to access the search web page that is placed into > > > > >>>the Tomcat webapps directory. > > > > >>> > > > > >>>However when I run the webapp from the tomcat server > (port 8080) > > > > >>>I get document url's of host:8080/index-results, which are > > > > >>>incorrect because the indexed pages are really under > > > > >>>host/index-results, > > > > >>>it, not part of that server. > > > > >>> > > > > >>>We believe that we've installed mod_webapp.so > correctly and that > > > > >>>the Apache server is talking to the Tomcat Server but I don't > > > > >>>know how to complete the task properly. > > > > >>> > > > > >>>We need to query a search web page on the primary server and > > > > >>>use mod_webapp.so to pass context to get proper results ? or > > > > >>>we need to modify the output to produce correct server > > > information > > > > >>>in the output URLs ? > > > > >>> > > > > >>> thanks > in advance, > > > > >>> > > > > >>> Brian > > > > >>> > > > > >>>--- > > > > >>> Brian R Cuttler > brian.cuttler@wadsworth.org > > > > >>> Computer Systems Support (v) 518 486-1697 > > > > >>> Wadsworth Center (f) 518 473-6384 > > > > >>> NYS Department of Health Help Desk 518 473-0773 > > > > >>> > > > > >>> > > > > >>> > > > > >>>-- > > > > >>>To unsubscribe, e-mail: > > > > >>> > > > > >>>For additional commands, e-mail: > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>__________________________________________________ > > > > >>Do you Yahoo!? > > > > >>Y! Web Hosting - Let the expert host your web site > > > > >>http://webhosting.yahoo.com/ > > > > >> > > > > >>-- > > > > >>To unsubscribe, e-mail: > > > > > > > >>For additional commands, e-mail: > > > > > > > >> > > > > >> > > > > >> > > > > > > > > > > > > > > >-- > > > > >To unsubscribe, e-mail: > > > > > > > >For additional commands, e-mail: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > > > > > For additional commands, e-mail: > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > > For additional commands, e-mail: > > > > > > -- > > To unsubscribe, e-mail: > > > For additional commands, e-mail: > > > > > > -- > To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: