Description
...
Note |
---|
Be sure to setup the page containing this tag to be Configured for AJAX |
Parameters
...
While this tag can be used with the simple theme, xhtml theme, and others, it is really designed to work best with the ajax theme. We recommend reading the ajax a template documentation for more details.
Parameters
...
...
Examples
Wiki Markup |
---|
{snippet:id=example1|lang=xml|javadoc=true|url=com.opensymphony.webwork.components.Href} |
Wiki Markup |
---|
{snippet:id=exampledescription1|javadoc=true|url=com.opensymphony.webwork.components.Href} |
Wiki Markup |
---|
{snippet:id=example2|lang=xml|javadoc=true|url=com.opensymphony.webwork.components.Href} |
Wiki Markup |
---|
{snippet:id=exampledescription2|javadoc=true|url=com.opensymphony.webwork.components.Href} |
Wiki Markup |
---|
{snippet:id=example3|lang=xml|javadoc=true|url=com.opensymphony.webwork.components.Href} |
Nested Elements
The remote A tag supports nested param elements. <ww:param name="" value=""/>
Handling Results
- Currently the remote a will try to evaluate the results as JavaScript. So the action defined in href should return a javascript snippet that will be executed upon return. Th
- The afterLoading method is called after the the above javascript gets evaluated. The afterLoading javascript does not currrently have access to the returned data.
Note | ||
---|---|---|
| ||
Remember that if you want your results to be executed... and your using sitemesh... you must NOT decorate the request w/ sitemesh. |
Usage
To get started, use the head tag and the ajax theme. See ajax head template for more information. Then look at the usage details for the ajax a template.
If you want to use additional parameters in your s:a the best practice is to use a s:url to create your url and then leverage this url into your s:a tag. This is done by creating a s:url and specifying an id attribute.. like "testUrlId" in this example. Then in the s:a tag reference this id in the href attribute via " %{testUrlId}"
...