lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aruna Rawat" <>
Subject RE: Why is Document final?
Date Fri, 23 Dec 2005 11:08:23 GMT
Can u plz tell me if i have to ask any doubt so where should i mail.....

Aruna Rawat
(Software Engineer)
Patni Computer Systems,
Millennium Business Park,
Mahape, Navi Mumbai 400 710
Phone: 022-27783600, Ext: 1708

-----Original Message-----
From: Steven Pannell []
Sent: Friday, December 23, 2005 4:23 PM
To: ''
Subject: RE: Why is Document final?


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:
World-Wide Partnerships. World-Class Solutions.

This e-mail message may contain proprietary, confidential or legally
privileged information for the sole use of the person or entity to
whom this message was originally addressed. Any review, e-transmission
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you have received this e-mail in error
kindly delete  this e-mail from your records. If it appears that this
mail has been forwarded to you without proper authority, please notify
us immediately at and delete this mail. 

View raw message