Re: [Hibernate] some .legacy test failure

That is very strange... Emmanuel Bernard wrote: HSQLDB Default hibernate.properties Gavin King wrote: On what database? Emmanuel Bernard wrote: Any reason why some test.legacy tests fail ? -- Gavin King +61 410 534 454 +1 404 822 8349 callto://gavinking Hibernate [EMAIL PROTECTED] http://hiberna

Re: [Hibernate] some .legacy test failure

HSQLDB Default hibernate.properties Gavin King wrote: On what database? Emmanuel Bernard wrote: Any reason why some test.legacy tests fail ? -- Emmanuel Bernard [EMAIL PROTECTED] http://www.hibernate.org --- This SF.net email is sponsored by: IT

Re: [Hibernate] some .legacy test failure

On what database? Emmanuel Bernard wrote: Any reason why some test.legacy tests fail ? -- Gavin King +61 410 534 454 +1 404 822 8349 callto://gavinking Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] http://jboss.com ---

Re: [Hibernate] ObjectFactory

Thanks! Emmanuel Bernard wrote: done Gavin King wrote: Drop it :) Emmanuel Bernard wrote: Sun fixed the backward compatibility bug we had on javax.nnaming.spi.ObjectFactory.getObjectInstance(Object, Name, Context, Hashtable); by changing Hashtable to HashTable We now have 2 options: - keep the jdk

Re: [Hibernate] ObjectFactory

done Gavin King wrote: Drop it :) Emmanuel Bernard wrote: Sun fixed the backward compatibility bug we had on javax.nnaming.spi.ObjectFactory.getObjectInstance(Object, Name, Context, Hashtable); by changing Hashtable to HashTable We now have 2 options: - keep the jdk15 hack I did in the build proce

[Hibernate] some .legacy test failure

Any reason why some test.legacy tests fail ? -- Emmanuel Bernard [EMAIL PROTECTED] http://www.hibernate.org --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of t

RE: [Hibernate] Fix for OSCache clustering

Just to clarify this does not eliminate the regions. It just corrects the way the provider implemented them. You can put and flush into the region. You can set different refresh periods and cron policies per region. You just cannot set a separate capacity. Oscache groups sort of = hibernate regi

Re: [Hibernate] Fix for OSCache clustering

No, I'm not really interested in this patch. Entire assumption of Hibernate cache architecture is that we have various cache regions. You will notice that we don't recommend OSCache to be used in a cluster. March, Andres wrote: I have a patch for the OSCache classes that are part of hibernate to

Re: [Hibernate] ObjectFactory

Drop it :) Emmanuel Bernard wrote: Sun fixed the backward compatibility bug we had on javax.nnaming.spi.ObjectFactory.getObjectInstance(Object, Name, Context, Hashtable); by changing Hashtable to HashTable We now have 2 options: - keep the jdk15 hack I did in the build process and gain a more rob

Re: [Hibernate] Fix for OSCache clustering

March, Andres wrote: I have a patch for the OSCache classes that are part of hibernate to fix the issues with clustering when using this provider. If you were not aware, the cluster listener is set up in oscache per cache instance. Since the provider was creating a cache for each region, it wo

[Hibernate] Fix for OSCache clustering

I have a patch for the OSCache classes that are part of hibernate to fix the issues with clustering when using this provider.  If you were not aware, the cluster listener is set up in oscache per cache instance.  Since the provider was creating a cache for each region, it would fail in a cl

Re: [Hibernate] what's wrong with JCA?

I guess JCA is *really* meant for managing resources, which Hibernate is not. Personally I think JMX is a more elegant solution... Igor Fedorenko wrote: Hello, I have a general question about usability of Hibernate JCA adapter. As far as I can tell, current adapter code has not changed much from

[Hibernate] ObjectFactory

Sun fixed the backward compatibility bug we had on javax.nnaming.spi.ObjectFactory.getObjectInstance(Object, Name, Context, Hashtable); by changing Hashtable to HashTable We now have 2 options: - keep the jdk15 hack I did in the build process and gain a more robust implementation (generics usage)

Re: [Hibernate] what's wrong with JCA?

Use the user forum, you'll have better feedback on real life use of JCA Igor Fedorenko wrote: Hello, I have a general question about usability of Hibernate JCA adapter. As far as I can tell, current adapter code has not changed much from the prototype-grade code submitted almost two years ago. Th

[Hibernate] what's wrong with JCA?

Hello, I have a general question about usability of Hibernate JCA adapter. As far as I can tell, current adapter code has not changed much from the prototype-grade code submitted almost two years ago. That makes me suspect that it is not being really used. And apparently JBoss decided not to us