[Hibernate] RE: Becoming an official XDoclet module
Well, Gavin once requested commit access to xdoclet's cvs for the hibernate module. In that period of time we've been discussing an approach for handling new modules without the need to put them in xdoclet's cvs. Now I'm +1 on hibernate in xdoclet's core and opening cvs access for its maintainer. So if Gavin agrees too I can candidate you (or maybe Gavin himself, whomever you find more appropriate for this role). Ara. > -Original Message- > From: Joel Rosi-Schwartz [mailto:[EMAIL PROTECTED] > Sent: Friday, December 06, 2002 5:15 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Becoming an official XDoclet module > > I know that this has come up before in the forum and dev list, but I > think it is worth re-evaluation. I just did an experiment of adding the > hibernate module to the latest XDoclet cvs source. It took all of 5 > minutes to integrate the module into the Xdoclet build. The results were > as I expected; the build went smoothly and all of the documentation was > produced without any pain. So I am wondering if maintaining the > Hibernate module seperately is really worth the extra pain and effort > that is required. > > As I understand it the main consideration is not having a maintainer for > the module that has commit priviledges on the XDoclet project. I agree > that handling changes via patches is awkward. So what does it take to > get accepted as a module and as a commiter to the Xdoclet project? If I > had assurances that Gavin and Ara were both willing to give me a bit of > support as needed, I would be willing to take on being the maintainer. > > - joel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Java-based query evaluator
> I'm curious how feasible it would be to write a Java-based evaluator of > Hibernate queries, or at least leverage the existing parser code to gain > access to the abstract syntax tree. > > One possibility is that certain subsets of queries (most filters, I > think) could be run within the JVM, saving a db query. possible it can be a good optimization, I am not sure: if "SELECT * FROM TABLE" was executed in current session and all objects are in cache , execute query on session cache. It is possible to implement "If current query result will be subset of some query executed before ... ". But it is not trivial. Not all databases support standard sql, "NULL==NULL" can evalute to true on databases, possible it can be more problems. > > Also, a translator could allow Hibernate query language to be used with > other persistence engines (ok, this is not so compelling since Hibernate > is the best :) > > Thanks, > Chris > > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > hibernate-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Re: Becoming an official XDoclet module
Good, I am pleased that you support the proposition. It would be fine by me whoever the committer was; my goal is to have a viable module and I am willing to support that which ever way is deemed to be most appropriate. - joel Ara Abrahamian wrote: Well, Gavin once requested commit access to xdoclet's cvs for the hibernate module. In that period of time we've been discussing an approach for handling new modules without the need to put them in xdoclet's cvs. Now I'm +1 on hibernate in xdoclet's core and opening cvs access for its maintainer. So if Gavin agrees too I can candidate you (or maybe Gavin himself, whomever you find more appropriate for this role). Ara. -Original Message- From: Joel Rosi-Schwartz [mailto:[EMAIL PROTECTED]] Sent: Friday, December 06, 2002 5:15 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Becoming an official XDoclet module I know that this has come up before in the forum and dev list, but I think it is worth re-evaluation. I just did an experiment of adding the hibernate module to the latest XDoclet cvs source. It took all of 5 minutes to integrate the module into the Xdoclet build. The results were as I expected; the build went smoothly and all of the documentation was produced without any pain. So I am wondering if maintaining the Hibernate module seperately is really worth the extra pain and effort that is required. As I understand it the main consideration is not having a maintainer for the module that has commit priviledges on the XDoclet project. I agree that handling changes via patches is awkward. So what does it take to get accepted as a module and as a commiter to the Xdoclet project? If I had assurances that Gavin and Ara were both willing to give me a bit of support as needed, I would be willing to take on being the maintainer. - joel
[Hibernate] Becoming an official XDoclet module
I know that this has come up before in the forum and dev list, but I think it is worth re-evaluation. I just did an experiment of adding the hibernate module to the latest XDoclet cvs source. It took all of 5 minutes to integrate the module into the Xdoclet build. The results were as I expected; the build went smoothly and all of the documentation was produced without any pain. So I am wondering if maintaining the Hibernate module seperately is really worth the extra pain and effort that is required. As I understand it the main consideration is not having a maintainer for the module that has commit priviledges on the XDoclet project. I agree that handling changes via patches is awkward. So what does it take to get accepted as a module and as a commiter to the Xdoclet project? If I had assurances that Gavin and Ara were both willing to give me a bit of support as needed, I would be willing to take on being the maintainer. - joel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Re: [Opensymphony-developers] A Hibranate provider for OsUser?
Hi Joel! it would be great if you work on a security provider for osuser, but IMHO it would be good not to use a session bean for it. Then it would be also usable in pure servlet containers, for example resin. regards chris - Original Message - From: "Joel Rosi-Schwartz" <[EMAIL PROTECTED]> To: "Patrick Lightbody" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, December 05, 2002 10:08 PM Subject: Re: [Hibernate] Re: [Opensymphony-developers] A Hibranate provider for OsUser? > Patrick, > > Fine, I'll be happy to make this contribution. My plans are to use a > Session bean and have it retieve the the Hibernate SessionFactory via > JNDI. Does this suit your needs? One of the problems with integrating > Hibernate with OsUser is that Hibernate is so flexible and that there > are several applicable use cases. I have not really begun to explore how > to best design a provider such that it is easy to use in all them and I > would really appreciate any suggestion? > > - joel > > Patrick Lightbody wrote: > > >Joel, > >I don't think one has been created yet. If you could write one, I'll get it > >in CVS right away (I will need it very soon as well, so that'd be great if > >you could get it done). > > > >-Pat > > > >- Original Message - > >From: "Joel Rosi-Schwartz" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]>; > ><[EMAIL PROTECTED]>; > ><[EMAIL PROTECTED]> > >Sent: Thursday, December 05, 2002 4:31 AM > >Subject: [Opensymphony-developers] A Hibranate provider for OsUser? > > > > > > > > > >>Has anyone created a Hibernate provider for Open Symphony's OsUser > >>module that they are willing to share? If so I would very much like to > >>have a copy. If not I will put one together in the next few days and > >>share it back to the OsUser project. > >> > >>Thanks, > >>Joel > >> > >> > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > hibernate-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Java-based query evaluator
I'm curious how feasible it would be to write a Java-based evaluator of Hibernate queries, or at least leverage the existing parser code to gain access to the abstract syntax tree. One possibility is that certain subsets of queries (most filters, I think) could be run within the JVM, saving a db query. Also, a translator could allow Hibernate query language to be used with other persistence engines (ok, this is not so compelling since Hibernate is the best :) But really, the query language seems very clean and simple, and I believe has the potential to be useful in scenarios even outside of persistence. Kind of like JXPath, but more SQL-like. This way all the queries in my application could use the same language, regardless of whether there is an underlying database. I've looked at the cirrus.hibernate.query package and most of it is pretty generic, but there are some obvious places where the persistence stuff creeps in. Is it worth persuing reusing this code? If not, do you anticipate many changes to the query language going forward? Thanks, Chris --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
