On Aug 22, 2012, at 8:11 AM, Steve Ebersole wrote:
> Also, I think how you were expecting beforeMetadataProcessing to happen can't
> really happen, but I suspect it is the more direct way to port envers.
>
> I *think* what you were thinking is to have envers pass along its extra
> EntitySourc
Also, I think how you were expecting beforeMetadataProcessing to happen
can't really happen, but I suspect it is the more direct way to port envers.
I *think* what you were thinking is to have envers pass along its extra
EntitySource/EntityHierarchy stuff. You cannot just simply "add the
custo
I'm in the process of making these changes...
- Original Message -
> From: "Steve Ebersole"
> To: "Strong Liu"
> Cc: "Hibernate hibernate-dev"
> Sent: Tuesday, August 21, 2012 6:20:19 AM
> Subject: Re: [hibernate-dev] uniform the "Composite" and "Component"
>
> So then change them:)
>
Everyone else ok with this idea?
On Tue 21 Aug 2012 08:27:25 AM CDT, Steve Ebersole wrote:
> Not so concerned about shutdown situations.
>
> More, imagine a custom ConnectionProvider implementation provided by
> user. And the use case of upgrading that implementation "in flight".
> I think thats
Not so concerned about shutdown situations.
More, imagine a custom ConnectionProvider implementation provided by
user. And the use case of upgrading that implementation "in flight".
I think thats the OSGi use case. And not so sure Hibernate should be
implementing this self healing. I guess
On 08/20/2012 11:19 PM, Steve Ebersole wrote:
> This ties together a few different discussions that have been going on
> simultaneously on the mailing list that I think are all related.
>
> Right now to configure certain services (select one impl over another)
> users generally give the FQN for tha
So then change them:)
On 08/21/2012 03:15 AM, Strong Liu wrote:
> for example:
>
> /**
> * Models the notion of a component (what JPA calls an Embeddable).
> *
> * NOTE : Components are not currently really hierarchical. But that is a
> feature I want to add.
> *
> * @author Steve Ebe
Yes, thats what you said in the javadocs ;)
What I mean is that we have a use case for one of those. But not the
other. So why develop something that we do not have a use case for?
On Mon 20 Aug 2012 11:23:14 PM CDT, Strong Liu wrote:
> reuse the IntegratorService / ServiceLoader ?
>
> On Aug
for example:
/**
* Models the notion of a component (what JPA calls an Embeddable).
*
* NOTE : Components are not currently really hierarchical. But that is a
feature I want to add.
*
* @author Steve Ebersole
*/
public class Composite extends AbstractAttributeContainer {
org.hibernate.me
