lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marco Tedone" <>
Subject Re: [NEWBIE] Creating context-relative URLs with Tomcat + Struts
Date Wed, 10 Sep 2003 06:39:18 GMT
Jeff, that exactly what I'm realizing.

First of all I have been able to read the configuration file (by keeping an
instance of ModuleConfig at startup) and therefore to realize a mapping
between (action -> JSP). This has been only possible because even for simple
forwards I used the Struts ForwardAction. I also found the way to isolate:
protocol + server | web-app-context | action/jsp | Servlet mapping (.do /

In the meantime, I created a stateless session bean which has a method
which, given an environment variable as a String, returns the path to that
environment variable; therefore it will be quite simple to replace, let's
say, CATALINA_HOME with the information I isolated as mentioned above.

I'm going to create an entity bean (therefore a db table) with the isolated
information (i.e. protocol, context, and so on);
when user will run a search, and possibly Lucene will return to me the list
of system-relative JSPs, I'll substitute the system-path with the web-path,
by concatenating all the web-relative information stored in the database,
and instead of presenting to the user the list of links to JSPs, I'll show
him the list of links to actions.

There is still a major problem to solve; realize somehow the mapping between
actual content-matching JSPs and JSPs which define only Tiles 'define'
statements. The reason is that the JSPs mapped vs an action in the struts
configuration file are basically empty.

I'll have to work around it.


- Original Message ----- 
From: "Jeff Linwood" <>
To: "Lucene Users List" <>
Sent: Wednesday, September 10, 2003 6:40 AM
Subject: Re: [NEWBIE] Creating context-relative URLs with Tomcat + Struts

> Why don't you set the path field to be relative to whatever the base
> directory is that the administrator puts in?  So, you write the path
> field yourself, and just put in the relative link, like /index.jsp,
> /welcome.jsp, or whatever?  You can just use the relative link directly
> in your web application.
> The book chapter covers pulling content out of a database through a data
> access layer, so it's a little different than pulling files out of a
> file system, but most of the basics are the same.
> If the actual content is hidden behind wrapper JSP pages, Struts
> Actions, parameters, or whatever, the display code that writes the links
> out in the JSP page can reference a mapping like you said.  The hard
> part would be writing the mapping code, calling it should be easy.
> Hope this helps,
> Jeff
> Marco Tedone wrote:
> > Hi Jeff, DAMN!, two of the books I haven't got :) I bought Jakarta
> > from O'reilly and another one on JSP/Servlets/Web programming.
> >
> > I already wrote the user interfaces and the classes (I wrote a stateless
> > which performs both the indexing and the researching of the result) to
> > the search.
> >
> > My problem is another: as you'll certainly know, as I'm running on
> > my Tomcat home path is something similar to:
> >
> > D:\Tomcat\
> >
> >>From my web application (which is a J2EE application using Struts and
> > Tomcat) I ask the application administrator to specify the folder she
> > to index and the folder where she wants the results to be put (for
> > searches...) and the file extensions she wants to include.
> >
> > Now, the application generates the index without any problem. The
problem is
> > that the path to the files is:
> >
> > D:\Tomcat\webapps\myapp\web\.... (The list of indexed files) and not
> > something like:
> >
> >
> >
> >
> > ...And so on.
> >
> > Therefore, if the user runs a search, I feel myself ridicolous if I'm
> > to show her Windows path instead of web-relative paths. The reason for
> > is that I'm using the FileDocument class coming with the distribution,
> > write the "path" Field using the File.getPath() method.
> >
> > But there is another problem: because I'm using Tiles (a mean of
> > the actual web-content is contained in foo-body.jsp pages, which are not
> > directly accessible, because at least the user will access foo.jsp
> > basically contains only an include to the foo-body.jsp) but more likely
> > will perform a Struts Action.
> >
> > I'm thinking at the following possible solution:
> >
> > Defining somewhere (conf file?) a mapping between paths to JSPs
> > sensible content (i.e. referring to the above example foo-body.jsp. This
> > the path could remain system-relative) and URLs to Struts Action which
> > actually executable by simply clicking a link and which forward to those
> > JSPs. The user then will perform a search, my application will intercept
> > string representing the path to the document containing the information,
> > will search on the mapping file the mapping to the Struts action and
> > display to the user the latter link. Eventually the results can be
> > somewhere.
> >
> > What do you think about this possible solution?
> >
> > Marco
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message