On 3/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Greetings --
Is there a document that explains the interaction and design expectations
when using AJAX/Dojo/S2?
As I understand it, the original goal was to make using the tags as
transparent as possible. For more ambitious uses of AJAX, it might be
better to use Dojo or YUI directly, and then use Struts actions as a
backend.
I have finally figured out how to make regions of
a page load asyncronously, and If I look at the DOM, all the elements are
there. However the elements do not show up in the browser unless I move my
DIV outside the FORM!
Yes, it's not usual for dynamic Ajax elements to appear only in the
DOM and not in the "show source" browser markup.
Also, are there any instructions regarding how the
struts.xml ties into the mix? For instance, what should the <result ...>
look like in the config file?
AFAIK, it should not look any different. An action is an action,
whether it is being called by Ajax or get/put. Some people use JSPs to
render output for Ajax requests, so the result might just point to a
JSP that renders a HTML snippet, plain text, or JSON. For a result,
there is also the new JSON plugin is designed to return JSON content
from any action
Right now my AjaxAction is simply
implementing the Action interface with an execute() and getZip() method.
getZip returns the Zip object that I hope to access via OGNL? I am looking
for a pattern that describes how the parts relate. I'm looking for a better
understanding of what the framework is expecting from me. and this link
didn't do it: http://struts.apache.org/2.x/docs/ajax.html
It's very possible that these use cases are out-of-scope for the
Struts tags. If the goal is tow work in the odd dynamic autocompleter
or the like, then the Ajax theme may be helpful. But, the Ajax tags
are not substitutes for full-blown Ajax implementations, like Dojo and
YUI.
If a project is going to use Ajax heavily, I'd suggest looking at Ajax Webparts
* http://javawebparts.sourceforge.net/
- HTH, Ted
<http://www.husted.com/ted/blog/>
--
Scott
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
