Yes, but I figured that we have this other check for doc type of
of the document using the NetUI tags. The TemplatedURLFormatter
is the last step in the rewriting of URLs for our tags. That's
how I saw this as tag related. I could put this in the
PageFlowUtils class to expose it to other non tag us
I'm not sure I understand. This seems like it's actually not related
to tags at all. I would have thought that by default we write out
"&" and that it's a URL thing.
On 4/14/05, Carlin Rogers <[EMAIL PROTECTED]> wrote:
> Daryl,
>
> I'm making my changes for JIRA 509 and thought that I'd make so
Daryl,
I'm making my changes for JIRA 509 and thought that I'd make some
additional changes to what you've done for the encoding of '&' as
the "&" entity inside of a URL query.
I thought I'd move the testing for the existence and value of the
configuration in the beehive-netui-config file out of th