Well. To all this time...
Hi Emmanuel,
> You lost me :)
> Could you write some code, maybe in a gist.github.com ?
I think I just expressed it overcomplicated. All I was talking about why
I use the QueryBean Interface. It is (currently) needed for hand written
queries like this:
publi
On 3 Jan 2014, at 22:22, Emmanuel Bernard wrote:
>>> - I don't think annotations are the best way to express queries but you
>>> probably
>>> have your reasons, so let's discuss them :)
>> Why? I think it's not hard to read an you have the query right with your
>> ParameterWrapper-class which
On 4 Jan 2014, at 10:24, Martin Braun wrote:
> Uhm. I totally forgot to add this functionality in my rewrite (I have
> rewritten most of the code last weekend)
> and I implemented a way to pass parameters into QueryTypes. You can even pass
> parameters that are dynamically
> determined by stat
... forgot to send it to all again.
> That would be cool
-> Next E-Mail
> I have to say that his boggles my mind. You have to do a lot of mind work and
> jumping forward and backward to put things
> together. I guess we can agree that this is not a silver bullet which makes
> writing querie
2014/2/3 Emmanuel Bernard
>
>
> > On 3 févr. 2014, at 15:21, Sanne Grinovero wrote:
> >
> >> On 3 February 2014 13:33, Emmanuel Bernard
> wrote:
> >> Hum, with the fact that this object now points to metadata, I wonder if
> >> we should force EhCache, Map and Infinispan to have their own versio
On Tue 2014-02-04 4:24, Martin Braun wrote:
> /**
>* @return a custom sort object or null
>*/
> public Sort getSort();
>
>
> or how to facet, etc...
>
>
> I want for this stuff to move to annotations (maybe) because I don't really
> like
> the fact that I have to i
Hi Steve,
Regarding Configuration, is there an example somewhere which shows how a
session factory is to be bootstrapped using the new approach?
Thanks,
--Gunnar
2014/1/31 Steve Ebersole
> As we transition to 5.0 we have to make a lot of decisions wrt API/SPI
> methods that are no longer r
