Hi Hardy! because it's the key for the static weakhashmap for the
autoregistration of listeners, that would introduce a memory leak.
I had proposed to care for registration of listeners in other ways, don't
have the reference now from the phone (I'd +1 to remove the static
weakhashmap)
cheers,
San
Hi,
just wondering whether there is a reason why we don't expose the
configuration properties in SearchFactory?
I think we talked about this once, but I cannot remember exactly.
I noticed that the properties are now exposed in
StateSearchFactoryImplementor anyways. Maybe
we could push this al
you may want this :D
On Jul 9, 2010, at 10:34 PM, Steve Ebersole wrote:
> Ok, I'm fed up. I am tired of having to clean up spam comments on our
> blogs entries daily. I woke up this morning to 85 comments, the vast
> majority of them spam! And this is after cleaning up0 yesterday.
>
> So if
Well in core we never developed "trunk" on a "branch" :) But
essentially I moved everything by hand; every branch, every tag, etc.
You are not going to be able to maintain history in both place as far as
I know. I think the closest you would get would be to:
1) svn mv
https://svn.jboss.org/repos
Ok, I'm fed up. I am tired of having to clean up spam comments on our
blogs entries daily. I woke up this morning to 85 comments, the vast
majority of them spam! And this is after cleaning up0 yesterday.
So if someone knows how to make entries only commentable by *registered*
users, that would
Hi,
I know this is a long overdue, but i'm now creating
https://svn.jboss.org/repos/hibernate/tools/
and is trying to figure out how to make what were done in
https://svn.jboss.org/repos/hibernate/branches/Branch_3_2/HibernateExt/tools/
the new trunk (maintaing history etc.)
Is svn mv the onl
Hi,
I assume that if I were to run the hibernate tools tests against the same
database settings in hibernate core
there is a risk of midair collision on the database :)
So i'm interested in hearing who maintains/setup those databases so I could get
one setup
to run the hibernate tools test sui
>>
>> In terms of these other concerns, how about someone actually try
>> importing it and see if there are real, actual issues rather than us
>> discussing esoteric possibilities that there could maybe be some
>> more-or-less catastrophic problem importing them into eclipse ;)
>
> I'll see if I
