This is required by the spec because:
- Performance - in the general case, saving the state for these is a waste
- Re-evaluation - if you've got, say, ${} EL expressions inside <f:verbatim>,
or any dynamically generated content from a tag, you'd better re-run the
JSP or you'll be showing stale content.
The second problem is important and cannot be resolved by changing
"transient" on f:verbatim.
Note that you've got other, likely bigger problems if you attempt to render
without re-executing the JSP:
- <c:if> will not re-execute, so if its condition has changed, ah well
- Resource bundles provided by <f:loadBundle> will not be available
- Any EL expressions evaluated inside tags will not re-evaluate
-- Adam
On 11/16/05, Volker Weber <[EMAIL PROTECTED]> wrote:
> Hi,
>
> i just came over a problem with verbatim tags in ajax enabled components.
> see:
> http://www.mail-archive.com/users%40myfaces.apache.org/msg12124.html
>
> The UIOutput components created for verbatim tags are not saved to state
> because there are explicitly set to transient.
>
> This makes it impossible to use verbatim tags in content of ajax components.
>
> Is there a spec reason for this, then we should have a tomahawk
> verbatim, or is this just because of performance?
>
> If not a spec reason this should be changed because seems to be a bug.
>
> Regards
> Volker
> --
> Don't answer to From: address!
> Mail to this account are droped if not recieved via mailinglist.
> To contact me direct create the mail address by
> concatenating my forename to my senders domain.
>
