2014-04-29 7:58 GMT+02:00 Gunnar Morling :
> 2014-04-29 0:21 GMT+02:00 Sanne Grinovero :
>
> Nice idea!
>> we could have each demo in a separate directory and put some
>> description for each in the root readme file.
>>
>
> +1
>
> But also the most polished demos, like if something evolves in bein
2014-04-29 0:21 GMT+02:00 Sanne Grinovero :
> Nice idea!
> we could have each demo in a separate directory and put some
> description for each in the root readme file.
>
+1
But also the most polished demos, like if something evolves in being
> extemely polished and well documented, should eventu
Nice idea!
we could have each demo in a separate directory and put some
description for each in the root readme file.
But also the most polished demos, like if something evolves in being
extemely polished and well documented, should eventually be promoted
for inclusion in http://www.jboss.org/jdf/
Hi Hardy,
I'd avoid a new configuration element.
I think we should strive at keeping the index small by default unless
there is a strong usability penalty, and I don't think this is a big
one.
Some power users pointed out that there are use cases in which having
the _id_ field of embedded relation
I should point out.. adding the additional named classes to the PAR also
leads to the test passing.
On Mon, Apr 28, 2014 at 4:56 PM, Steve Ebersole wrote:
> With my latest Scanner changes as outlined in the earlier email there is
> one failure in the HEM "packaged" tests that I simply cannot
With my latest Scanner changes as outlined in the earlier email there is
one failure in the HEM "packaged" tests that I simply cannot explain why it
was previously considered valid.
The test
is org.hibernate.jpa.test.packaging.PackagedEntityManagerTest#testCfgXmlPar.
The test builds a PAR (via Sh
Hi,
I started to look at HSEARCH-1494 [1] which deals with an unexpected exception
is thrown when @IndexedEmbedded is used.
Easiest to explain with an example:
@Entity
@Indexed
public class A {
@Id
@GeneratedValue
private long id;
@OneToOne
@IndexedEmbedd
On 28 Jan 2014, at 17:20, Steve Ebersole wrote:
> Almost done with this. We are much more aggressive about indexing stuff into
> Jandex now (which is a good thing) when we are not handed a Jandex Index.
>
> However, this does mean we need to be more careful in the case of JPA and
> exclude
+1
Martin Braun
martinbraun...@aol.com
www.github.com/s4ke
-Original Message-
From: Davide D'Alto
To: hibernate-dev
Sent: Mon, Apr 28, 2014 5:29 pm
Subject: Re: [hibernate-dev] GitHub repo for demo projects
+1
On Mon, Apr 28, 2014 at 4:03 PM, Brett Meyer wrote:
> +1 from me
+1
On Mon, Apr 28, 2014 at 4:03 PM, Brett Meyer wrote:
> +1 from me. I have several to contribute as well from various ORM
> presentations.
>
> https://github.com/brmeyer/HibernateDemos
>
> - Original Message -
> From: "Gunnar Morling"
> To: hibernate-dev@lists.jboss.org
> Sent: Monda
Almost done with this. We are much more aggressive about indexing stuff
into Jandex now (which is a good thing) when we are not handed a Jandex
Index.
However, this does mean we need to be more careful in the case of JPA and
exclude-non-listed-classes. ATM we drive annotations based on Jandex (a
+1 from me. I have several to contribute as well from various ORM
presentations.
https://github.com/brmeyer/HibernateDemos
- Original Message -
From: "Gunnar Morling"
To: hibernate-dev@lists.jboss.org
Sent: Monday, April 28, 2014 10:49:19 AM
Subject: [hibernate-dev] GitHub repo for dem
Hi,
Together with Sanne I've been creating a demo app which shows some features
of Hibernate OGM.
Right now this lives under my personal account on GitHub, but IMO it'd make
sense to move it somewhere under https://github.com/hibernate/ to make it
more visible, encourage re-use and contributions
13 matches
Mail list logo
