lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Pannell <>
Subject RE: Why is Document final?
Date Fri, 23 Dec 2005 10:53:26 GMT

Yes, I can see why in this implementation it will not work.  However, what
about using the XMLEncoder instead of Serializable?  Using this method we
have both platform and class object independence.  That would solve it.


-----Original Message-----
From: Erik Hatcher []
Sent: 23 December 2005 11:31
Subject: Re: Why is Document final?

On Dec 23, 2005, at 5:00 AM, Steven Pannell wrote:
> Can someone please tell my why the Document class has no interface  
> and is
> final?

Primarily because Lucene controls the construction of Document  
instances returned from Hits.

> I want to create some documents that have some standard fields (eg:  
> creation
> date), and I don't want to keep repeating my code.  This way I  
> ensure some
> standard conventions in all my documents.

You could ensure this by writing a wrapping method or class that  
creates Documents for you.

> What's the reason behind this? What's the argument against making an
> interface and not having the document final?

How would Lucene reconstruct the Document instance from Hits using  
your own implementation?


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message