Hi,

Just to clarify the clarifications of the previous clarifications ;)

Hi,

Just to clarify the clarification :


> Finally, the licensing issue is either a

huge difference or a doesn't-matter depending on your

company's lawyers


and/or how you intend to distribute the application -- OJB is ASL Hibernate is LGPL.

Just remember to read of license faq which states that Hibernate can be used in any project commercially or not - and without

making your


project opened source!


I was about to say the LGPL is not as simple as that; but having just read
the License FAQ, I see that Hibernate have been very clear about how they
interpret the LGPL. All credit to the hibenate team for that ! I still think
that corporate lawyers may disagree with the "hibernate" interpretation.

Yes, we hear this sometimes. But we have not yet found a license that signals our intent better than LGPL - and we think that with our very clear statement on how it should be interpreted regarding Hibernate all should be safe. Geez - the core developers are using this stuff in commercial systems, so I think everyone will be pretty safe ;)

pretty much

needs to know the JNDI lookup for your DataSource in its

configuration).


ok - did not knew that. I seem to remember using OJB before without requiring
any kind of JNDI!?



Yes, you can do that (not use JNDI). Brian's just saying that with hibernate you (as a hibernate user) can create your own connection and give to hibernate to be used. With OJB, you have to do a bit more work to achieve the same gaol.

Ok.


/max

Cheers,

Charles.


___________________________________________________________
HPD Software Ltd. - Helping Business Finance Business
Email terms and conditions: www.hpdsoftware.com/disclaimer




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to