That's an interesting approach, though I think a much more complicated
solution than I need. My objective isn't to allow clients to script
actions or otherwise modify their behaviour, but to make that
unnecessary. This approach would certainly allow one to provide much
more power if that were needed though.
L.
Frank W. Zammetti wrote:
Rather than pollute the view (if one chooses to perceive it that way...
I'm staying away from that debate!), why not introduce some sort of
scripting engine into the mix? I'm not really sure precisely where
because I don't know your project, but I say this based on your comment:
"True, at development time. But it's a lot easier if you don't *have* the
source code to the model or rest of the system."
Think of something like Microsoft Excel... you don't have access to the
source code obviously, but it exposes are rather rich object model that
you can manipulate through scripting. This lets you customize the app in
essence in just about any way you want without needing the source. It
also is arguably better architecturally than allowing someone to alter the
dialog resources of the app (not a perfect analogy I realize, but
hopefully close enough to get the point across).
There is the scripted Actions project specifically for Struts, there's
Jelly that might be applicable, the BSF, etc.
Something along those lines is almost tailor-made for the "the client
needs to modify our product in some way" situation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
