hi all,

i would like to use seqhilo to generate id with hibernate 3.0. the document says the following:

Unfortunately, you can't use hilo when supplying your own Connection to Hibernate. When Hibernate is using an application server datasource to obtain connections enlisted with JTA, you must properly configure the hibernate.transaction.manager_lookup_class.

i am not sure what it means by "supplying your own connection". i am using spring to set up a dbcp datasource and then use spring's LocalSessionFactoryBean and HibernateTransactionManager to set up transaction interceptors. i guess i am not using jta in this case. nor am i using any jndi datasource. would it count as "supplying your own connection"? can someone enlighten me on this?

thanks in advance.

seqhilo is not hilo, this restriction does not apply

thanks for the reply. my bad, didn't notice the constraint on "hilo" only.

still curious, what exactly does "supply your own transaction" mean? and why is that a constraint for hilo generator?

many thanks.

If you are using a Connection pool you are not supplying your own connections. This only applies if you use SessionFactory.openSession(connection) or the like.

[quote="weiqingh"]thanks for the reply. my bad, didn't notice the constraint on "hilo" only.

still curious, what exactly does "supply your own transaction" mean? and why is that a constraint for hilo generator?

/quote]

Hibernate needs a separate Transaction(and hence use some connection) to get the next hi value from a Hilo table and use that as the identifier for your entity. if you are supplying Connections(and hence not fed through a Connection pool), Hibernate would not be able to get any connections in this case.