[ http://issues.apache.org/jira/browse/BEEHIVE-838?page=all ]
Nathan Jantz closed BEEHIVE-838:
--------------------------------
Verified as of svn 239233. I did the following steps to verify the fix:
1) edit Formatter.java in
trunk/netui/test/webapps/urlTemplates/urlTemplates/WEB-INF/src/formatter/
and change the last line from
return template.format();
to
return template.format(false);
2) edit the beehive-url-template-config.xml file in
trunk/netui/test/webapps/urlTemplates/urlTemplates/WEB-INF/
and add some arbitrary tokens to the jpf-action template.
Something like {url:j838test}.
Then build/deploy/start the tomcat server and go to the formatter test.
http://localhost:8080/urlTemplates/formatter/
Look at the page source and see what the anchors are for the actions. The href
written out to the page should include your arbitrary token.
3) Set the Formatter.java method back to the return template.format() signature
and build and redeploy
the arbitrary {url:j838test} token should now be removed from the URLs when
viewing source of the generated HTML page. format() has the same behavior as
format(true).
Closing issue.
> Add a toString(boolean) method to support optional cleanup of unknown tokens
> in URLTemplate class.
> --------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-838
> URL: http://issues.apache.org/jira/browse/BEEHIVE-838
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: v1m1
> Environment: All
> Reporter: Subbu Allamaraju
> Assignee: Nathan Jantz
> Fix For: V1
> Attachments: j838-patch.txt, j838-patch2.txt
>
> The toString() method in URLTemplate supposedly (I've not tested yet) removes
> unknown tokens. We have some use cases where URLs are prepared in multiple
> passes with each pass filling some tokens only known at that pass. In between
> these passes, URLs are passed as strings and not as URLTemplate objects, and
> hence we need to way to tell URLTemplate to not cleanup unknown tokens.
> A method like toString(boolean unsetTokens) would solve our use case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
