[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 use JCA in favour to special HAR/SAR implementation. So I wonder if there is something fundamentally wrong with JCA? Or maybe current implementation has not reached necessary level of maturity to be usable? Regards, Igor PS: sorry if this is a wrong place to ask this kind of questions. --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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. That makes me suspect that it is not being really used. And apparently JBoss decided not to use JCA in favour to special HAR/SAR implementation. So I wonder if there is something fundamentally wrong with JCA? Or maybe current implementation has not reached necessary level of maturity to be usable? Regards, Igor PS: sorry if this is a wrong place to ask this kind of questions. --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- 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 them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[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) - drop it a gain simplicity and unique distribution I'm +1 for dropping it, any comments ? -- 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 them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 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 use JCA in favour to special HAR/SAR implementation. So I wonder if there is something fundamentally wrong with JCA? Or maybe current implementation has not reached necessary level of maturity to be usable? Regards, Igor PS: sorry if this is a wrong place to ask this kind of questions. --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- 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 --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[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 clustered configuration because unless you are running a supercomputer you cannot start up that many JChannels. The cache per region only allows one to specify capacity per region. Expiry policy (the real advantage of OSCache) is specified per entry. Basically I modified the provider to create only a single cache administrator. Because of limitations in OSCache the administrator can only have 1 cache (but I plan to change this in the future). Again all we lose is the ability to specify capacity per region. OSCache does have the idea of groups which allow it to flush a region. So the question is, do you want this patch? I already have changes I had to make to 2.1 that you guys have told me you will not integrate. So if you don’t want it I don’t really care. Just trying to help. -dres. - Andres March Platform - Apps Engineering Sony Online Entertainment desk: 858.577.3373 cell: 619.519.1519
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 would fail in a clustered configuration because unless you are running a supercomputer you cannot start up that many JChannels. The cache per region only allows one to specify capacity per region. Expiry policy (the real advantage of OSCache) is specified per entry. Basically I modified the provider to create only a single cache administrator. Because of limitations in OSCache the administrator can only have 1 cache (but I plan to change this in the future). Again all we lose is the ability to specify capacity per region. OSCache does have the idea of groups which allow it to flush a region. So the question is, do you want this patch? I already have changes I had to make to 2.1 that you guys have told me you will not integrate. So if you don’t want it I don’t really care. Just trying to help. I'm not confident, I'll let Gavin choose about your order by improvement. -dres. - Andres March Platform - Apps Engineering Sony Online Entertainment desk: 858.577.3373 cell: 619.519.1519 -- 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 them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 robust implementation (generics usage) - drop it a gain simplicity and unique distribution I'm +1 for dropping it, any comments ? -- 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 --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 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 clustered configuration because unless you are running a supercomputer you cannot start up that many JChannels. The cache per region only allows one to specify capacity per region. Expiry policy (the real advantage of OSCache) is specified per entry. Basically I modified the provider to create only a single cache administrator. Because of limitations in OSCache the administrator can only have 1 cache (but I plan to change this in the future). Again all we lose is the ability to specify capacity per region. OSCache does have the idea of groups which allow it to flush a region. So the question is, do you want this patch? I already have changes I had to make to 2.1 that you guys have told me you will not integrate. So if you don’t want it I don’t really care. Just trying to help. -dres. - Andres March Platform - Apps Engineering Sony Online Entertainment desk: 858.577.3373 cell: 619.519.1519 -- 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 --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 regions. I did notice that you did not recommend using OSCache in a cluster and when I asked why no one spoke up. Now I know that the provider implementation did not fit the design (however flawed) of oscache. Clustered invalidation is a real need but that is not oscache's only advantage. I really like the treecache but it is just not there yet for us and, I expect, others as well. > -Original Message- > From: Gavin King [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 06, 2004 4:12 PM > To: March, Andres > Cc: [EMAIL PROTECTED] > Subject: 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 > > 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 clustered configuration because unless you are running > > a supercomputer you cannot start up that many JChannels. The cache per > > region only allows one to specify capacity per region. Expiry policy > > (the real advantage of OSCache) is specified per entry. > > > > Basically I modified the provider to create only a single cache > > administrator. Because of limitations in OSCache the administrator can > > only have 1 cache (but I plan to change this in the future). Again all > > we lose is the ability to specify capacity per region. OSCache does > > have the idea of groups which allow it to flush a region. > > > > So the question is, do you want this patch? I already have changes I > > had to make to 2.1 that you guys have told me you will not integrate. > > So if you don't want it I don't really care. Just trying to help. > > > > -dres. > > > > - > > > > Andres March > > > > Platform - Apps Engineering > > > > Sony Online Entertainment > > > > desk: 858.577.3373 > > > > cell: 619.519.1519 > > > > > -- > 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 > --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[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 them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 process and gain a more robust implementation (generics usage) - drop it a gain simplicity and unique distribution I'm +1 for dropping it, any comments ? -- 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 them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 jdk15 hack I did in the build process and gain a more robust implementation (generics usage) - drop it a gain simplicity and unique distribution I'm +1 for dropping it, any comments ? -- 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 --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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 Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
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://hibernate.org JBoss Inc [EMAIL PROTECTED] http://jboss.com --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
