Thanks Erik.
Not too sure my question was clear. What I'm trying to do is to create a
searchable reference info system (ie bunch of documentation...:-) that is
packaged into a warfile, dropped into a servlet container and run 'in place'
In other words, I can't have the index on the filesystem but instead, it's
prebuilt and packaged into the WAR file.
So at the moment, Lucene on seems to be able to access file system indexes
(via the FSDirectory) or RAM based indexes via the RAMDirectory (which I
understand has a few problems with arrayindexoutofbounds exceptions...)
What I was thinking about doing was twofold.
1) Modify the Directory classes so that they follow more of a decorator
pattern (as in Directory dir = new RAMDirectory(new XXXDirectory(new
FSDirectory()) instead of the manual initialisation code that I've found on
the list
(http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg00196.html)
and
2) Create a WARDirectory for *readonly* access to a pre-built index stored
in a WAR.
So, am I barking up the wrong tree?
Bye,
Les
-----Original Message-----
From: Erik Hatcher
To: 'Lucene Developers List'
Sent: 2/11/02 10:36 PM
Subject: Re: [SUBMIT] docweb demo app
----- Original Message -----
From: "Les Hughes" <leslie.hughes@rubus.com>
> 1) Thanks for the Ant task - that'll save me some time on the train
tomorrow
> ;-)
You're welcome!
> 2) Maybe I need to RTFM but does the index run straight out of the WAR
file?
> I was thinking about creating a WARDirectory to do this but if it's
possible
> some other way I'd be interested to hear.
The index is built when someone runs it manually from Lucene's CVS
directory
locally currently. The idea is that it will be incorporated into
distribution builds (perhaps as a separate download since its about a
2MB
WAR) in the future. What I patched doesn't make it automatically
happen...
that comes after there is lucene-dev signoff and it gets rolled into the
main distribution build dependency graph.
Erik
--
To unsubscribe, e-mail:
<mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:lucene-dev-help@jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>
Not too sure my question was clear. What I'm trying to do is to create a
searchable reference info system (ie bunch of documentation...:-) that is
packaged into a warfile, dropped into a servlet container and run 'in place'
In other words, I can't have the index on the filesystem but instead, it's
prebuilt and packaged into the WAR file.
So at the moment, Lucene on seems to be able to access file system indexes
(via the FSDirectory) or RAM based indexes via the RAMDirectory (which I
understand has a few problems with arrayindexoutofbounds exceptions...)
What I was thinking about doing was twofold.
1) Modify the Directory classes so that they follow more of a decorator
pattern (as in Directory dir = new RAMDirectory(new XXXDirectory(new
FSDirectory()) instead of the manual initialisation code that I've found on
the list
(http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg00196.html)
and
2) Create a WARDirectory for *readonly* access to a pre-built index stored
in a WAR.
So, am I barking up the wrong tree?
Bye,
Les
-----Original Message-----
From: Erik Hatcher
To: 'Lucene Developers List'
Sent: 2/11/02 10:36 PM
Subject: Re: [SUBMIT] docweb demo app
----- Original Message -----
From: "Les Hughes" <leslie.hughes@rubus.com>
> 1) Thanks for the Ant task - that'll save me some time on the train
tomorrow
> ;-)
You're welcome!
> 2) Maybe I need to RTFM but does the index run straight out of the WAR
file?
> I was thinking about creating a WARDirectory to do this but if it's
possible
> some other way I'd be interested to hear.
The index is built when someone runs it manually from Lucene's CVS
directory
locally currently. The idea is that it will be incorporated into
distribution builds (perhaps as a separate download since its about a
2MB
WAR) in the future. What I patched doesn't make it automatically
happen...
that comes after there is lucene-dev signoff and it gets rolled into the
main distribution build dependency graph.
Erik
--
To unsubscribe, e-mail:
<mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:lucene-dev-help@jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>