http://in.relation.to/Bloggers/HibernateCore400Alpha2Release
--
Steve Ebersole
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
http://in.relation.to/Bloggers/HibernateCore363Release
--
Steve Ebersole
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
I like it. I tried to do something generically in the AS7 JPA code to
have a protected bag of such things at the container EntityManager
level. Just keep in mind that AS will try to serialize the objects when
clustering.
See
https://github.com/jbossas/jboss-as/blob/master/jpa/src/main/java/o
yes as is indeed better.
On 6 avr. 2011, at 13:29, Steve Ebersole wrote:
> A phrase I see a lot here is "as":
>
> session.as( AuditReader.class ).someEnversSpecificMethod()
>
> or
>
> session.as( FullTextSession.class )...
>
>
> On 04/06/2011 06:26 AM, Adam Warski wrote:
>>
>> On Apr 6, 201
That looks indeed short and concise.
--Hardy
On Wed, 06 Apr 2011 13:29:44 +0200, Steve Ebersole
wrote:
> A phrase I see a lot here is "as":
>
> session.as( AuditReader.class ).someEnversSpecificMethod()
>
> or
>
> session.as( FullTextSession.class )...
___
On Apr 6, 2011, at 1:29 PM, Steve Ebersole wrote:
> A phrase I see a lot here is "as":
>
> session.as( AuditReader.class ).someEnversSpecificMethod()
>
> or
>
> session.as( FullTextSession.class )...
Sounds good.
And in fact it's the AuditReader/FullTextSessions that could have unwrap
method
A phrase I see a lot here is "as":
session.as( AuditReader.class ).someEnversSpecificMethod()
or
session.as( FullTextSession.class )...
On 04/06/2011 06:26 AM, Adam Warski wrote:
>
> On Apr 6, 2011, at 1:20 PM, Steve Ebersole wrote:
>
>> The phrase 'unwrap' might be a bit misleading there beca
On Apr 6, 2011, at 1:20 PM, Steve Ebersole wrote:
> The phrase 'unwrap' might be a bit misleading there because you may not be
> dealing with wrapped objects. But the idea itself is still solid I believe.
> Think of it more as a multi-directional cast
Right, the idea sounds good; so it would
The phrase 'unwrap' here might be a bit misleading because you may not
always be dealing with wrapped objects. But the idea itself is still
solid I believe. Think of it as a multi-directional cast; you can
up-cast as well as down-cast.
We do need to be very very very careful about stack overf
> FullTextSession ftSession = session.unwrap(FullTextSession.class);
> //the current approach is via some static helper method
> //FullTextSession ftSession = Search.getFullTextSession(session);
>
> That would mean that the integration point between HSearch and Hibernate
> would have an unwrap
>>> Like I said, I do not think that is enough as I think that if you get the
>>> connection, you also need the "transaction context" holding that connection.
>>> "transacvtion context" here is the TransactionCoordinator.
>>>
>>> session.sessionWithOptions().transactionContext().openSession()
>>
11 matches
Mail list logo
