From: Joel Rosi-S. <Joe...@Et...> - 2002-12-07 22:01:11
|
I have been looking over the existing OsUser providers and considering the best approach for creating a hibernate provider. There are a two issues I would like to have some feedback on. First off I think that it will be worth the effort to keep it as architecturally generic as possible. Towards that end I am considering using the properties that are passed into the Provider's init() to retrieve a JNDI name for the SessionFactory. Is this sufficiently generic for most user's or does it have to be even more flexible? Second, I am a bit concerned at the usage of the PropertySetManager for storing the user's profile. My first consideration is that it does not fit neatly into the architecture of the applications that I plan to use this for. I could get over that one and would not mind terribly creating two version; one that used the PropertSetManager and one that stored the data directly in my application's objects. What I have a hard time buying into is the extra work to create the Hibernate Propertyset implementation. If I am not mistaken Gavin expressed willingness to do that some time back if someone else did... Did that ever get done? If not is someone willing to bite off that part of this task? - joel |
From: Patrick L. <pli...@ci...> - 2002-12-11 17:31:52
|
Joel, I believe that Justin Stepka (correct me if I'm wrong, Justin) has written a Hibernate PropertySet implementation. -Pat ----- Original Message ----- From: "Joel Rosi-Schwartz" <Joe...@Et...> To: <ope...@li...>; "hibernate list" <hib...@li...> Cc: "Patrick Lightbody" <pli...@ci...>; "Gavin King" <ga...@ap...>; "Mike Cannon-Brookes" <mi...@at...> Sent: Saturday, December 07, 2002 2:01 PM Subject: Details of hibernate provider for OsUser > I have been looking over the existing OsUser providers and considering > the best approach for creating a hibernate provider. There are a two > issues I would like to have some feedback on. > > First off I think that it will be worth the effort to keep it as > architecturally generic as possible. Towards that end I am considering > using the properties that are passed into the Provider's init() to > retrieve a JNDI name for the SessionFactory. Is this sufficiently > generic for most user's or does it have to be even more flexible? > > Second, I am a bit concerned at the usage of the PropertySetManager for > storing the user's profile. My first consideration is that it does not > fit neatly into the architecture of the applications that I plan to use > this for. I could get over that one and would not mind terribly creating > two version; one that used the PropertSetManager and one that stored the > data directly in my application's objects. What I have a hard time > buying into is the extra work to create the Hibernate Propertyset > implementation. If I am not mistaken Gavin expressed willingness to do > that some time back if someone else did... Did that ever get done? If > not is someone willing to bite off that part of this task? > > - joel |
From: Patrick L. <pli...@ci...> - 2002-12-11 17:34:36
|
(resend, the first attempt went to the wrong list) Joel, I believe that Justin Stepka (correct me if I'm wrong, Justin) has written a Hibernate PropertySet implementation. -Pat ----- Original Message ----- From: "Joel Rosi-Schwartz" <Joe...@Et...> To: <ope...@li...>; "hibernate list" <hib...@li...> Cc: "Patrick Lightbody" <pli...@ci...>; "Gavin King" <ga...@ap...>; "Mike Cannon-Brookes" <mi...@at...> Sent: Saturday, December 07, 2002 2:01 PM Subject: Details of hibernate provider for OsUser > I have been looking over the existing OsUser providers and considering > the best approach for creating a hibernate provider. There are a two > issues I would like to have some feedback on. > > First off I think that it will be worth the effort to keep it as > architecturally generic as possible. Towards that end I am considering > using the properties that are passed into the Provider's init() to > retrieve a JNDI name for the SessionFactory. Is this sufficiently > generic for most user's or does it have to be even more flexible? > > Second, I am a bit concerned at the usage of the PropertySetManager for > storing the user's profile. My first consideration is that it does not > fit neatly into the architecture of the applications that I plan to use > this for. I could get over that one and would not mind terribly creating > two version; one that used the PropertSetManager and one that stored the > data directly in my application's objects. What I have a hard time > buying into is the extra work to create the Hibernate Propertyset > implementation. If I am not mistaken Gavin expressed willingness to do > that some time back if someone else did... Did that ever get done? If > not is someone willing to bite off that part of this task? > > - joel |