Forwarding to the forum since the devel list won't want this traffic but other users might: http://forum.hibernate.org/viewtopic.php?p=2218296
> -----Original Message----- > From: Douglas Fisher [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 07, 2004 4:52 PM > To: March, Andres > Subject: RE: hibernate-devel digest, Vol 1 #1119 - 12 msgs > > > Forgive me if the list is the right place for this, but a co-worker > forwarded this to me and I'm eager to get an answer. I may be > interested in your patch. > > What are the symptoms of your problem with OSCache in a cluster? > > We plugged it into Hibernate to replace SwarmCache. (We may be > experiencing a memory leak in SwarmCache.) We have no trouble starting > up with OSCache. It registers its oodles of Jchannels. Both nodes in > our cluster receive messages from each other. Everything seems fine, > BUT sometimes we will get OutOfMemoryExceptions. It doesn't always even > seem to be related to running our application. (By the way, Jprofiler > shows no obvious leaks with either cache provider.) I am not sure I can > pin the bad behaviour on the cache, and that's why I'm interested in > your symptoms. > > I'd like to hear more from you on this subject. I'm disappointed that > it isn't covered in more detail on the Hibernate site. > > > > > -----Original Message----- > From: Matt Dowell > Sent: Thursday, October 07, 2004 10:11 AM > To: Douglas Fisher > Subject: FW: hibernate-devel digest, Vol 1 #1119 - 12 msgs > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 06, 2004 7:01 PM > To: [EMAIL PROTECTED] > Subject: hibernate-devel digest, Vol 1 #1119 - 12 msgs > > Send hibernate-devel mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of hibernate-devel digest..." > > > Today's Topics: > > 1. what's wrong with JCA? (Igor Fedorenko) > 2. Re: what's wrong with JCA? (Emmanuel Bernard) > 3. ObjectFactory (Emmanuel Bernard) > 4. Re: what's wrong with JCA? (Gavin King) > 5. Re: ObjectFactory (Gavin King) > 6. Fix for OSCache clustering (March, Andres) > 7. Re: Fix for OSCache clustering (Emmanuel Bernard) > 8. Re: Fix for OSCache clustering (Gavin King) > 9. RE: Fix for OSCache clustering (March, Andres) > 10. some .legacy test failure (Emmanuel Bernard) > 11. Re: ObjectFactory (Emmanuel Bernard) > 12. Re: ObjectFactory (Gavin King) > > --__--__-- > > Message: 1 > Date: Wed, 06 Oct 2004 17:48:55 -0400 > From: Igor Fedorenko <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [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. > > > --__--__-- > > Message: 2 > Date: Wed, 06 Oct 2004 23:59:26 +0200 > From: Emmanuel Bernard <[EMAIL PROTECTED]> > To: Igor Fedorenko <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] > Subject: 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 > > > > --__--__-- > > Message: 3 > Date: Thu, 07 Oct 2004 00:23:14 +0200 > From: Emmanuel Bernard <[EMAIL PROTECTED]> > To: hibernate-devel <[EMAIL PROTECTED]> > Subject: [Hibernate] ObjectFactory > > Sun fixed the backward compatibility bug we had on > javax.nnaming.spi.ObjectFactory.getObjectInstance(Object, Name, Context, > > Hashtable); > by changing Hashtable<String, ?> 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 > > > > --__--__-- > > Message: 4 > Date: Thu, 07 Oct 2004 08:54:36 +1000 > From: Gavin King <[EMAIL PROTECTED]> > To: Igor Fedorenko <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] > Subject: 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 > > > > > --__--__-- > > Message: 5 > Date: Thu, 07 Oct 2004 08:55:04 +1000 > From: Gavin King <[EMAIL PROTECTED]> > To: Emmanuel Bernard <[EMAIL PROTECTED]> > CC: hibernate-devel <[EMAIL PROTECTED]> > Subject: 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<String, ?> 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 > > > > > --__--__-- > > Message: 6 > Date: Wed, 6 Oct 2004 15:57:29 -0700 > From: "March, Andres" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: [Hibernate] Fix for OSCache clustering > > This is a multi-part message in MIME format. > > ------_=_NextPart_001_01C4ABF7.DAE8BDAD > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > 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. =20 > > =20 > > 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. =20 > > =20 > > 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. > > =20 > > -dres. > > =20 > > ----------------------------------------- > > Andres March > > Platform - Apps Engineering > > Sony Online Entertainment > > desk: 858.577.3373 > > cell: 619.519.1519 > > =20 > > > ------_=_NextPart_001_01C4ABF7.DAE8BDAD > Content-Type: text/html; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" = > xmlns:w=3D"urn:schemas-microsoft-com:office:word" = > xmlns=3D"http://www.w3.org/TR/REC-html40";> > > <head> > <meta http-equiv=3DContent-Type content=3D"text/html; = > charset=3Dus-ascii"> > <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)"> > <style> > <!-- > /* Font Definitions */ > @font-face > {font-family:"Arial Narrow"; > panose-1:2 11 5 6 2 2 2 3 2 4;} > /* Style Definitions */ > p.MsoNormal, li.MsoNormal, div.MsoNormal > {margin:0in; > margin-bottom:.0001pt; > font-size:12.0pt; > font-family:"Times New Roman";} > a:link, span.MsoHyperlink > {color:blue; > text-decoration:underline;} > a:visited, span.MsoHyperlinkFollowed > {color:purple; > text-decoration:underline;} > span.EmailStyle17 > {mso-style-type:personal-compose; > font-family:Arial; > color:windowtext;} > @page Section1 > {size:8.5in 11.0in; > margin:1.0in 1.25in 1.0in 1.25in;} > div.Section1 > {page:Section1;} > --> > </style> > > </head> > > <body lang=3DEN-US link=3Dblue vlink=3Dpurple> > > <div class=3DSection1> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'>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. = > <o:p></o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'><o:p> </o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'>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. = > <o:p></o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'><o:p> </o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'>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.<o:p></o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'><o:p> </o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'>-dres.<o:p></o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = > style=3D'font-size:10.0pt; > font-family:Arial'><o:p> </o:p></span></font></p> > > <p class=3DMsoNormal><font size=3D2 face=3D"Arial Narrow"><span = > style=3D'font-size: > 10.0pt;font-family:"Arial = > Narrow"'>-----------------------------------------</span></font><o:p></o > := > p></p> > > <p class=3DMsoNormal><font size=3D2 face=3D"Arial Narrow"><span = > style=3D'font-size: > 10.0pt;font-family:"Arial Narrow"'>Andres = > March</span></font><o:p></o:p></p> > > <p class=3DMsoNormal><font size=3D2 face=3D"Arial Narrow"><span = > style=3D'font-size: > 10.0pt;font-family:"Arial Narrow"'>Platform - Apps = > Engineering</span></font><o:p></o:p></p> > > <p class=3DMsoNormal><font size=3D2 face=3D"Arial Narrow"><span = > style=3D'font-size: > 10.0pt;font-family:"Arial Narrow"'>Sony Online = > Entertainment</span></font><o:p></o:p></p> > > <p class=3DMsoNormal><font size=3D2 face=3D"Arial Narrow"><span = > style=3D'font-size: > 10.0pt;font-family:"Arial Narrow"'>desk: = > 858.577.3373</span></font><o:p></o:p></p> > > <p class=3DMsoNormal><font size=3D2 face=3D"Arial Narrow"><span = > style=3D'font-size: > 10.0pt;font-family:"Arial Narrow"'>cell: = > 619.519.1519</span></font><o:p></o:p></p> > > <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = > style=3D'font-size: > 12.0pt'><o:p> </o:p></span></font></p> > > </div> > > </body> > > </html> > > ------_=_NextPart_001_01C4ABF7.DAE8BDAD-- > > > --__--__-- > > Message: 7 > Date: Thu, 07 Oct 2004 01:05:01 +0200 > From: Emmanuel Bernard <[EMAIL PROTECTED]> > To: "March, Andres" <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] > Subject: 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 > > > > --__--__-- > > Message: 8 > Date: Thu, 07 Oct 2004 09:12:21 +1000 > From: Gavin King <[EMAIL PROTECTED]> > To: "March, Andres" <[EMAIL PROTECTED]> > 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 > > > > > --__--__-- > > Message: 9 > Subject: RE: [Hibernate] Fix for OSCache clustering > Date: Wed, 6 Oct 2004 16:22:52 -0700 > From: "March, Andres" <[EMAIL PROTECTED]> > To: "Gavin King" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > > 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 > =3D 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 > >=20 > > No, I'm not really interested in this patch. Entire assumption of > > Hibernate cache architecture is that we have various cache regions. > >=20 > > You will notice that we don't recommend OSCache to be used in a > cluster. > >=20 > > March, Andres wrote: > >=20 > > > 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 > > > > >=20 > >=20 > > -- > > Gavin King > > +61 410 534 454 > > +1 404 822 8349 > > callto://gavinking > >=20 > > Hibernate > > [EMAIL PROTECTED] > > http://hibernate.org > >=20 > > JBoss Inc > > [EMAIL PROTECTED] > > http://jboss.com > >=20 > > > > --__--__-- > > Message: 10 > Date: Thu, 07 Oct 2004 01:28:23 +0200 > From: Emmanuel Bernard <[EMAIL PROTECTED]> > To: hibernate-devel <[EMAIL PROTECTED]> > Subject: [Hibernate] some .legacy test failure > > Any reason why some test.legacy tests fail ? > > -- > Emmanuel Bernard > [EMAIL PROTECTED] > http://www.hibernate.org > > > > --__--__-- > > Message: 11 > Date: Thu, 07 Oct 2004 01:28:53 +0200 > From: Emmanuel Bernard <[EMAIL PROTECTED]> > To: hibernate-devel <[EMAIL PROTECTED]> > Subject: 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<String, ?> 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 > > > > --__--__-- > > Message: 12 > Date: Thu, 07 Oct 2004 10:00:01 +1000 > From: Gavin King <[EMAIL PROTECTED]> > To: Emmanuel Bernard <[EMAIL PROTECTED]> > CC: hibernate-devel <[EMAIL PROTECTED]> > Subject: 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<String, ?> 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 > > > > > > --__--__-- > > _______________________________________________ > hibernate-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > > > End of hibernate-devel Digest ------------------------------------------------------- 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
