Re: Problems in solrJ trunk

Thank you Lucas, You caught my point nicely and even got a clearer idea of what to do. Sorry Solr Dev Team, but I don't there is any reasonable excuse for making such an argument interface vs abstract class as they are complements and don't have the same role in OOP. Anyways, Solr is a great app.

Re: Problems in solrJ trunk

Exactly, And adding the methods in the abstract class in the minor releases, and in the interface in major releases. []s, Lucas Lucas Frare A. Teixeira [EMAIL PROTECTED] Tel: +55 11 3660.1622 - R3018 Alexander Ramos Jardim escreveu: Well, There is a simple cas

Re: Problems in solrJ trunk

having to go into this discussion again. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: Alexander Ramos Jardim <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Monday, June 9, 2008 3:19:36 PM > Subject: Re: Probl

Re: Problems in solrJ trunk

Well, There is a simple case here. I tried to update SolrJ to use the last one and got the application selected for test broke. So, I developed an alternative interface for SolrServer and a wrapper to CommonsHttpSolrServer. Altered my aoolication to use it and everything is working nice. When you

Re: Problems in solrJ trunk

solrj was not released in 1.2, so the change is not incompatible... The rationalle for abstract class vs interface is more to do with usage and future maintenance. If SolrServer is an interface and solr 1.4 adds methods, there is no way to make it backwards compatible -- as an abstract cla