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
> 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, s
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. S
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
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 PROTECTE
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
