Well not being this very urgent I'm going to create two JIRAs, on it,
one for the norms, and one for possibly changing the storage of the
optional field.
just wanted to mention it as while debugging I found it surprising behaviour.
*But* your last sentence got me a weird idea.
Nowadays if you hav
2011/3/15 Emmanuel Bernard :
>
> On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
>
>> I guess we should prevent the indexing of ids in secondary elements?
>
> If the associated element is an entity, it's perfectly valid to index its id
> and query by it
>
> //return all books when the author's i
On 15 mars 2011, at 18:24, Emmanuel Bernard wrote:
>
> On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
>
>> I guess we should prevent the indexing of ids in secondary elements?
>
> If the associated element is an entity, it's perfectly valid to index its id
> and query by it
>
> //return a
On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
> I guess we should prevent the indexing of ids in secondary elements?
If the associated element is an entity, it's perfectly valid to index its id
and query by it
//return all books when the author's id is 2
"author.id:2"
_
2011/3/15 Emmanuel Bernard :
> Are you talking about JPA entities (with @Entity and @Id or mere mortal POJOs?
I got a bit confused for the reasons of your question, so I made some tests.
The index state reported in the previous email was about annotation
mapped entities, I repeated
the same test o
For the idea files yeah I had to do all sort of fiddling to make sure it finds
all source, including generated one.
I have annotation processing disabled.
On Mar 15, 2011, at 10:55 AM, Hardy Ferentschik wrote:
> Hi,
>
> did you rebuild the idea configuration files - 'gradle idea'
> Steve and I
Right. I forgot to mentioned this. That is what I did as well.
On Tue, 15 Mar 2011 12:45:44 +0100, Steve Ebersole
wrote:
> Actually the thing that seemed to work for me was to explicitly enable
> AnnotationProccessors on the intellij compiler, but to tell it an
> explicit
> empty list of pro
Actually the thing that seemed to work for me was to explicitly enable
AnnotationProccessors on the intellij compiler, but to tell it an explicit
empty list of processors to perform.
On Tuesday, March 15, 2011, at 04:55 am, Hardy Ferentschik wrote:
> Hi,
>
> did you rebuild the idea configurati
Are you talking about JPA entities (with @Entity and @Id or mere mortal POJOs?
On 14 mars 2011, at 21:26, Sanne Grinovero wrote:
> Hello,
> while debugging I just noticed that having a two entities scenario like
>
> @Indexed class Book {
> Long id;
> @IndexedEmbedded Nation bublishedFirstIn;
> }
Hi,
did you rebuild the idea configuration files - 'gradle idea'
Steve and I had similar issues after opening master in idea with the new
logging stuff.
I would guess that the annotation processor goes wild.
What helped for me was to re-create the idea config files and then go
through
all the
Got around it increasing javac compiler mem from 128mb to 256mb. I wonder where
this default comes from?
On Mar 15, 2011, at 10:48 AM, Galder Zamarreño wrote:
> Guys,
>
> What the heck is up with master? I import it into IntelliJ, run the compiler
> and I get an OOME compiling!
>
> See attach
Guys,
What the heck is up with master? I import it into IntelliJ, run the compiler
and I get an OOME compiling!
See attached screenshot. As you can see IntelliJ has enough memory.
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
__
12 matches
Mail list logo
