if it is a Stateful SessionBan you will have to create an EntityBean 
implementation with the same functionality. And then in the EJB's load() and 
store() you will have to serialize the array. Or if it is a CMP EJB, just 
declare the array as a persistent field.


mvh karl

On Wednesday 03 July 2002 16:39, Terry Steichen wrote:
> Karl,
>
> Just to clarify.  I have an application that runs searches as requested by
> users.  The application is persistent across multiple requests, so there's
> no problem creating it at startup.  And, given the application's
> persistence, there should be no problem storing it in memory to serve
> subsequent requests.  I just can't figure out how to modify the SearchBean
> code to do this.  I seemed like it would be simple, but try as I might,
> nothing has so far worked.
>
> Regards,
>
> Terry
>
>
> ----- Original Message -----
> From: "Karl Řie" <[EMAIL PROTECTED]>
> To: "Lucene Users List" <[EMAIL PROTECTED]>
> Sent: Wednesday, July 03, 2002 10:34 AM
> Subject: Re: SearchBean Persistence
>
> > if the array is of a serializable sort, just store it in a sql table !?!
> >
> > mvh karl řie
> >
> > On Wednesday 03 July 2002 16:22, Terry Steichen wrote:
> > > I'm using Peter's SearchBean code to sort search results.  It works
>
> fine,
>
> > > but it creates the sorting field array from scratch with every
>
> invocation
>
> > > (which takes on the order of a second or so to complete - each search
> > > itself takes about one tenth of that or less).  While I can conduct
>
> several
>
> > > searches in the same module, I can't figure out how to persist the
>
> sorting
>
> > > field array between invocations of the search module.
> > >
> > > Any advice on how to do this would be much appreciated.
> > >
> > > Regards,
> > >
> > > Terry
> >
> > --
> > To unsubscribe, e-mail:
>
> <mailto:[EMAIL PROTECTED]>
>
> > For additional commands, e-mail:
>
> <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to