
|
If you were logged in you would be able to see more operations.
|
|
|
WebWork
Created: 23/May/04 10:53 PM
Updated: 24/May/04 02:21 AM
|
|
| Component/s: |
Views
|
| Affects Version/s: |
2.1
|
| Fix Version/s: |
2.1
|
|
|
The current way the velocity directives work is borked.
Basically, I think they write directly to the response, instead of to the current Velocity controller writer. This means you can get strange sequences of output.
For example if you have something like:
a
#tag (foo)
b
You get
a
foo
b
which is what you'd expect (and why noone has discovered this before).
However if you're nesting directives, the output order is wrong, for example this:
#a
#tag(foo)
#end
produces output like this:
foo
a
end a
not like this:
a
foo
end a
|
|
Description
|
The current way the velocity directives work is borked.
Basically, I think they write directly to the response, instead of to the current Velocity controller writer. This means you can get strange sequences of output.
For example if you have something like:
a
#tag (foo)
b
You get
a
foo
b
which is what you'd expect (and why noone has discovered this before).
However if you're nesting directives, the output order is wrong, for example this:
#a
#tag(foo)
#end
produces output like this:
foo
a
end a
not like this:
a
foo
end a |
Show » |
| There are no comments yet on this issue.
|
|