Ok. I will move this discussion to the users group.
I understand that it sounds reasonable to have a null check but the
important point is that it has broken backwards compatibility. Any thoughts
on that?
On Thu, May 8, 2014 at 7:07 PM, Steve Ebersole wrote:
> This list is for discussions about
On 8 Jan 2014, at 19:19, Steve Ebersole wrote:
> So a few follow ups question here.
>
> First, wrt @MessageLogger/@LogMessage versus @MessageBundle do we want to
> split these?
For what it’s worth, we do the split in Validator. I think I prefer it this
way, but have no strong
feeling about
So a few follow ups question here.
First, wrt @MessageLogger/@LogMessage versus @MessageBundle do we want to
split these? The cliff notes version is that @MessageBundle (and
@Message) is used to define parameterized messages for translation;
@MessageLogger/@LogMessage further says that resulting
For those that did not see the Scanning/Jandex Pull Request I sent earlier,
it includes some initial proofing along these lines.
Essentially I started creating a set of distinct, functional-based
MessageLoggers which log to dedicated categories per functional area.
Samples are by far the best way
This list is for discussions about the development of Hibernate, not for
usage discussions.
The behavior you describe sounds the most reasonable to me actually, tbh.
Also, generic code can (should, I'd argue) still do null checks...
On Thu, May 8, 2014 at 6:51 AM, amit shah wrote:
> We upgrad
http://blog.seecr.nl/2014/02/24/a-faster-join-for-solrlucene/
Just wanted to point out this article that talks about query time joins in
Lucene.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hiberna
We upgraded hibernate from 3.6.0 to 4.3.5 but the application fails if null
is passed to Session.evict()
The application passes null since the code is generic.
Are there any alternatives?
Thanks,
Amit.
___
hibernate-dev mailing list
hibernate-dev@lists.
