lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guilherme Barile <...@prosoma.com.br>
Subject RE: Lucene & EJBs
Date Mon, 26 May 2003 13:37:16 GMT
You could use lucene as an alternative to realtinal databases (for
documents).
I have something in mind that could run on a j2ee server, with
distributed objects and all that stuff.

gui

On Sun, 2003-05-25 at 11:07, Lichtner, Guglielmo wrote:
> I think I missed the reason why it is now necessary to retrofit Lucene
> into an EJB model. EJB is designed for certain uses. What are you planning
> to use this for?
> 
> -----Original Message-----
> From: Edgar Poce [mailto:edgarpoce@hotmail.com]
> Sent: Saturday, May 24, 2003 3:40 PM
> To: Lucene Users List
> Subject: Re: Lucene & EJBs
> 
> 
> I am using Lucene in an EJB environment but I didn't test it thoroughly. I
> am new in both technologies, so it wouldn't be strange I made a wrong
> approach.
> 
> Stateless Session Bean: IndexWriter
> Stateless Session Bean: IndexReader
> EntityBean: IndexInformation
> 
> IndexInformation has the location for accessing the index based on a key.
> IndexReader makes the queries with the location set in IndexInformation.
> IndexWriter writes a new index in a different location ([indexKey]+[time]),
> it doesn't overwrite the old one, so there is no lock problem. When it
> finishes the index, it sets a new location in IndexInformation and new
> queries are made against the new Index. IndexWriter also waits x time  and
> tries to delete the old index (just in case it is in use by an IndexReader
> started before the completion of the new index).
> 
> I guess it is wrong beacuse It accesses the filesystem but It could be
> solved with a jdbc storage.
> 
> Please let me know if it is obvious it will stop working soon.
> 
> Edgar
> 
> ----- Original Message ----- 
> From: "Eric Jain" <Eric.Jain@isb-sib.ch>
> To: "Lucene Users List" <lucene-user@jakarta.apache.org>
> Sent: Friday, May 23, 2003 5:42 AM
> Subject: Re: Lucene & EJBs
> 
> 
> > > Managing the update notification and
> > > reindexing in the writer is the problem.
> >
> > My current solution is to have all updates done through a JMX MBean.
> > This MBean is also responsible for (re)binding an IndexReader to JNDI at
> > startup and after updating.
> >
> > A JCA wrapper would allow things such as whether or not the current
> > operation is being executed in a transaction to be passed on to such a
> > Lucene MBean - certainly useful if you intend to modify the index from
> > an EJB. Of course you would still have to implement the rollback
> > function yourself...
> >
> >
> > --
> > Eric Jain
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org


Mime
View raw message