In the interest of moving forward with velocity (yuk, yuk..), I
apparently recind my apparent -1 that was apparently holding back the
apparent +1s. :)
David Kinnvall forwarded to me the latest rendition of DBResourceLoader,
and I am happy to do the work to get it in, to show my support. But
'work', I mean fix the build process so it's easy and safe for non-J2ee
users, and will put a smudge of documentation somewhere.
1) Can someone direct me to an example of how to use Ant to find j2ee
stuff? I tried to build DBResourceLoader, and we can all guess what
happened... :)
2) I think that it should go in
org.apache.velocity.runtime.resource.loader rather than o.a.v.app, but
since this contradicts what some have already agreed to, I assume we
should discuss this. My reason is that it is a loader, not an
application tool, and kinda low level. An app may have *no idea* that
it is the source of template content - contrast this with the
o.a.v.app.Velocity class, which is used by apps directly. An option is
something like o.a.v.j2ee.loader.DBResourceLoader, but again, lets
discuss? That would mean that we could drop things right in there as we
wished, and use <exclude o.a.v.j2ee.*> in ant to keep it out of a
nonj2ee build. Less maintenance on our end, and easy to find code?
On the tool project front, I stil believe 100% we should do this, but I
recognize that there isn't much support for it here in the Velocity
community. I will still keep battling though :)
Progress is being made on the Jakarta-Tools / Library / 'Rupert' front,
so maybe if there is interest later, some of us can participate in that
on the servlet tool front.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Velocity : it's not just a good idea. It should be the law.
http://jakarta.apache.org/velocity
