My other belief, and one that is paramount in my own open source
project, is that a framework/toolkit always _should_ employ these
philosophies to support its user base and the other framework
communities that depend on it, if the solution is relatively trivial.

It is, IMHO, a good framework's responsibility to perform these tasks
to make lives easier for the masses. I think Hibernate does this
exceptionally well, and I'm assuming (hoping!) my proposal is in line
with this philosophy...

Cheers,

Les

On Thu, Jun 19, 2008 at 5:42 PM, Les Hazlewood <les@(protected):
> I agree with you Chris, it does better simulate it. But Hibernate has
> always been deployable outside of a container. Shouldn't it retain
> that philosophy in its code base as well, architecting flexible
> approaches that work seamlessly both in a JEE container and out?
>
> That's my belief...
>
> On Thu, Jun 19, 2008 at 5:39 PM, Chris Bredesen <cbredesen@(protected):
>> joël Winteregg wrote:
>>>
>>> I also had the same issue which was fixed using an update of the
>>> transaction manager I use (Bitronix 1.3). A light JNDI server is now
>>> embedded in it...
>>
>> This is an alternative that I've discussed with others off list. IMHO, this
>> better simulates the in-container JTA environment.
>>
>> -Chris
>>
>>
>

_______________________________________________
hibernate-dev mailing list
hibernate-dev@(protected)
https://lists.jboss.org/mailman/listinfo/hibernate-dev