Laurie Harper wrote:
Nope, Dave nailed it. Re-read the requirement I described. The point is to avoid using actions to load the data and pass it to the view. If you re-read my description of what I mean by 'push' vs. 'pull' rather than simply saying the terms mean something different it might help.
I think somebody mentioned this before, but I'll reiterate: you might want to think about something like Jython server pages or wrangling something Jython-esque into a custom tag body, etc. which would give you a full-on language that doesn't require compilation.
If you provide reasonable hooks into your system from objects dropped in the app/session/request this might be a convenient way to support the functionality you want.
That said, I'd feel like I had a "safer" system if things were handled via XML configs etc. rather than code, which can be risky. It depends on who your target audience is (sort of the "languages for the masses" vs. "languages for smart people" argument) and how much you trust 'em :)
I was able to accomplish a LOT in a short amount of time by doing a fair amount of work in Jython and making Jython code loadable from a DB: we didn't have access to the production system, so making any quick "tweaks" was out of the question. Since it was the developers that were playing with the most dynamic code bits we could expose a lot of functionality without fear of somebody (purposefully or accidentally) doing the Wrong Thing. Your situation might be different, but it's an idea.
I think I'll drop the topic now, before this degrades into a flame fest.
Wuss!!! ;) *lol* Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
