that now.
Cheers,
Dick
- Original Message -
From: Hani Suleiman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, November 15, 2003 9:15 PM
Subject: [OS-webwork] velocity ui tags
I've managed to get the velocity UI tags working decently in webwork
1.3, this means
.
Cheers,
Dick
- Original Message -
From: Hani Suleiman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, November 15, 2003 9:15 PM
Subject: [OS-webwork] velocity ui tags
I've managed to get the velocity UI tags working decently in webwork
1.3, this means that a requestdispatcher
I've managed to get the velocity UI tags working decently in webwork
1.3, this means that a requestdispatcher is not used anymore for the ui
components. It's about 10x faster than the old way, but for me on Orion
at least, it's the same speed as using the jsp ui components.
I'm enclosing a
I've checked an alternate format for rendering the WebWork2 ui tags from
Velocity. My hope is to migrate to this new style and deprecate (then
remove) the current $ui style for rendering.
Previously, the following JSP tags
ui:textfield label=mylabel name=myname value=myvalue/
would be
PROTECTED]
Subject: [OS-webwork] velocity ui tags redux
I've checked an alternate format for rendering the WebWork2 ui tags
from
Velocity. My hope is to migrate to this new style and deprecate
(then
remove) the current $ui style for rendering.
Previously, the following JSP tags
When I wrote ui tags for velocity back around 1.2, I used a directive for
each tag (#textfield, #hidden, etc), which is still the format that I
prefer. The problem I ran into (and why I've never committed anything to
CVS) was dealing with parameters, and dealing with directives having to be
either
