That's what we're doing... it turned out that instead of using the
interface version Context, in one of our interfaces, I used
VelocityContext instead so it wasn't a simple matter to swap out a
serializable version of our own. Instead everything is iterated from
the context (before tools are added) and then serialized to disk.
We're still working on this and will very likely contribute it back.
Cheers,
J --
On Aug 29, 2008, at 9:59 PM, Christopher Schultz wrote:
Jason,
Jason Chodakowski wrote:
As for serializable objects, all of ours (or rather, everything we
put
in the context) is serializable. Part of this is just due to other
requirements - RMI and Hibernate for instance.
I think you are better off serializing your Context objects separate
from the context, and then creating a new Context and filling it with
your serialized data in order to display the templates outside of the
webapp/datasource environment.
Perhaps I should have asked the original question this way: does
everyone on this list do their own template editing, or do you have a
division between your web designers and java coders.
We just have the designers do the design, and have the engineers cut
up
the HTML wireframes into the appropriate templates. We try not to
have a
whole lot of design churn, so that helps tremendously. If you do
develop
something, please consider contributing it back to the community. I'm
sure that lots of folks will find it useful.
Good luck,
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
