> > 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 >
Well, I don't think anyone wants to do it "wrong" ;-) This is like the issue with XWork in SAF 2. SAF 2 is still going to be built on XWork, like WebWork is, but you're just not going to have to SEE it. We could do the same with DWR. We can make the capabilities of DWR available without having to make you have a dwr.xml file, etc. What's more, with JDK5 and annotations, we could just let you tag your actions as @AjaxEndpoint or something (maybe @AjaxList for things that provide a type-ahead list, etc)? I'm still waiting to see how this plays out... I've been a big proponent of Dojo and built several Dojo widgets, but I understand that it can be tricky and not as easy to use as we'd all like. I think there'll be room for different strategies and implementations, and we'll figure it out as we go. --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=32216&messageID=62655#62655 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
