AppFuseVelocity |
|
Your trail: |
Difference between
version 11
and
version 8:
At line 1 changed 1 line. |
__Part I:__: [Integrating Velocity into AppFuse|AppFuseVelocity] - A HowTo for adding the Velocity Templating engine to AppFuse applications for rendering views. |
__Part I:__ [Integrating Velocity into AppFuse|AppFuseVelocity] - A HowTo for adding the Velocity Templating engine to AppFuse applications for rendering views. |
At line 26 changed 1 line. |
[{Java2HtmlPlugin |
{{{ |
At line 32 changed 1 line. |
}] |
}}} |
At line 40 changed 1 line. |
<include name="*.jar" /> |
<include name="*.jar" /> |
At line 47 changed 1 line. |
<war |
<war |
At line 83 changed 1 line. |
</war> |
</war> |
At line 159 changed 1 line. |
I haven't got my head around where webdoclet looks for this yet. But basically if you forward out from an Action to anything matching the Velocity uri-pattern. The above tools will contain all the struts resources you'll need. They're embedded in the context as $key, for example $link, $errors, $form and so on. |
Change your XDoclet @struts.action-forwards to be something like the following: |
{{{ |
* @struts.action-forward name="edit" |
path="/path/to/template/.[vm/jst/whatever]" |
}}} |
At line 165 added 2 lines. |
The above tools will contain all the struts resources you'll need. They're embedded in the context as $key, for example $link, $errors, $form and so on. |
|
At line 169 added 2 lines. |
|
''This tutorial was written by [Cameron Gray|http://cameronsweblog.co.uk/page/cameron] - thanks Cameron!'' |
Back to AppFuseVelocity,
or to the Page History.
|