Ian Roughley wrote:
So, you are saying that your preference would be to include no ajax
integration and leave the framework and let users integrate this as
required - either directly in the HTML or by creating custom themes?
/Ian
No, I definitely would love to see ajax support...I just think it needs
to be done right. Integrating DWR looks like it might get a bit messy.
Taking ideas from DWR, maybe even some of the code and/or the js libs,
and building the support directly into SAF2 would be a better option.
That way the look and feel of writing ajax enabled actions is the same
as writing other actions. This keeps the SAF2 code simple (e.g. you
don't need to worry about the glue holding together SAF2 and DWR
breaking when a new version of DWR comes out, developers don't need to
jump between the DWR codebase and SAF2 codebase) and will be easier for
users when configuring their apps (everything is configured in xwork.xml
or annotations, no dwr.xml, no servlet extra config in web.xml, etc.).
That's just my two cents, I know it's kind of reinventing the wheel but
I think it would definitely pay off in the end.
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
