You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by "David H. DeWolf" <dd...@apache.org> on 2007/01/26 04:46:13 UTC
[java-templates-plugin] TagSerializer vs TagHandler
In the sandbox's java templates plugin:
What is the intention of the TagSerializer interface? It looks as
though if XHTMLTagSerializer is simply modified to implement TagHandler
instead it can safely be removed. Is there an intention that's not yet
shown in the code, or is this a left over remnant?
Thanks,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [java-templates-plugin] TagSerializer vs TagHandler
Posted by Don Brown <mr...@twdata.org>.
The idea is to mark a class that will be converting the events to an
output stream, but is a logical role, not necessarily a technical one.
Don
David H. DeWolf wrote:
> In the sandbox's java templates plugin:
>
> What is the intention of the TagSerializer interface? It looks as
> though if XHTMLTagSerializer is simply modified to implement
> TagHandler instead it can safely be removed. Is there an intention
> that's not yet shown in the code, or is this a left over remnant?
>
> Thanks,
>
>
> David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org