Hi All
I have been looking at the Hibernate Search codebase and I am very keen to
help out. I have noticed some small changes I would like to purpose (very
small) and I hope I don't offend anyone by mentioning these.
1) Remove cyclic reference in JmsBackEndQueueProcessor and
JmsBackEndQueueProce
Hi,
On Fri, 23 Oct 2009 16:47:48 +0200, Amin Mohammed-Coleman
wrote:
> I have been looking at the Hibernate Search codebase and I am very keen
> to help out.
Great. Help is always welcome :)
> 1) Remove cyclic reference in JmsBackEndQueueProcessor and
> JmsBackEndQueueProcessorFactory. I
Hi, welcome,
2)
I didn't need it so far, but it seems reasonable to provide this access.
Out of curiosity, what are you needing it for?
Seems a bit weird that nobody asked before.
3)
Nice, but because of a problem in namespaces with compass I guess
you're not using their implementation of Lucene
Steve,
Thanks for the follow-up. I am using Windows XP and have direct access
to the Internet (or so I think). My connection is a physical line into
my router and out through my cable. I can check out from Apache and
java.net just fine. I will see about the proxy option like Darryl
Miles said and
I'm looking into this as it's blocking way too much other stuff,
it's not hard to implement but is having me puzzled about usability.
Basically I'm planning to throw an exception when different entities
are defining a different Similarity while sharing the same index.
This case is obvious:
@Entit
Hello,
On 23 oct. 09, at 16:47, Amin Mohammed-Coleman wrote:
> Hi All
>
> I have been looking at the Hibernate Search codebase and I am very
> keen to
> help out. I have noticed some small changes I would like to purpose
> (very
> small) and I hope I don't offend anyone by mentioning these.
Summary, I would be happy with a beta release soon if we can work on
updating the documentation.
On 21 oct. 09, at 20:12, Sanne Grinovero wrote:
> Hi Emmanuel,
> had a chat with Navin today, he was pinging me about HSEARCH-397. He
> is needing that for the Infinispan release.
> This issue was p
Warnings are useless IMO, I would raise an exception if you find
inconsistencies.
Doesn't a similarity configuration exist at the index (property) level
already? If not, I agree, this would make more sense to me.
On 23 oct. 09, at 19:52, Sanne Grinovero wrote:
> I'm looking into this as it's
2009/10/23 Emmanuel Bernard :
[..]
>>
>> Mutual dependency: so Infinispan is needing a Search release, and
>> Search an Infinispan release? It's about a submodule from the one
>> depending on the core of the other, still we should release at least a
>> beta to make a deployment possible, or have In
No Similarity is not being read from configuration files, just the annotations.
Current behaviour already throws an exception if two/more entities
from the same class hierarchy define a different Similarity, but in
this case it's considered acceptable to define it once for all
involved types;
actua
Hi All
Thank you for your valuable feedback.
I agree that the Spring integration should actually be done on the Spring
side. To be honest I have been somewhat annoyed with Spring and agree that
putting Spring into the Hibernate Search isn't probably a good idea. It
makes sense for Spring to be d
11 matches
Mail list logo
