I've moved all issues in JIRA according to this thread.
Please move in/out as you wish in case you see something wrong.
I've opened (and worked on) some issues about suboptimal usage of
FieldSelector, related to work on FielCaches. Even without the
fieldcaches, this release is likely going to brin
On Wed, 16 Feb 2011 14:46:52 +0100, Emmanuel Bernard
wrote:
> We have targeted v 3.4 for end of march.
> What do you think of doing an Alpha1 within the next two weeks?
+1 Sounds good to me
> For reference, the list of todo we had for 3.4 is:
> - Faceting (hardy)
I will have some alpha mate
Oops, wrong train... Sorry about the noise :-)
On 02/16/2011 12:21 PM, Scott Marlow wrote:
> Its a minor change but I would like to make a small enhancement to
> EntityManager.unwrap(). I would like to support SessionFactory in case
> I want to use it later in AS7...
>
> Is this completely silly
Its a minor change but I would like to make a small enhancement to
EntityManager.unwrap(). I would like to support SessionFactory in case
I want to use it later in AS7...
Is this completely silly or just mildly silly? If creating a container
managed entity manager doesn't consume a database c
On 16 févr. 2011, at 16:19, Sanne Grinovero wrote:
> Hi,
> from my part I'd give priority to fieldcache and massindexer features.
> The benchmark was blocked by Infinispan issues, all solved yesterday.
> So now I'd like to shape the FieldCache feature:
> * Implicitly using it on classname and id
Hi,
from my part I'd give priority to fieldcache and massindexer features.
The benchmark was blocked by Infinispan issues, all solved yesterday.
So now I'd like to shape the FieldCache feature:
* Implicitly using it on classname and id
* looking how it could be convenient to enable wider usage on
