|

»

[jira] Created: (TAP5-755) URL rewriting documentation contains an example that won't compile due to lack of a return value

View: New views

6 Messages — Rating Filter: Alert me

	[jira] Created: (TAP5-755) URL rewriting documentation contains an example that won't compile due to lack of a return value by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message URL rewriting documentation contains an example that won't compile due to lack of a return value ------------------------------------------------------------------------------------------------ Key: TAP5-755 URL: https://issues.apache.org/jira/browse/TAP5-755 Project: Tapestry 5 Issue Type: Bug Components: documentation Affects Versions: 5.1.0.5 Reporter: Robert Zeigler Priority: Minor In the documentation for url rewriting, the final example shows a rule which processes incoming and outgoing requests to re-map the name of pages as visible to the user. However, there is a chain of logic through the code in which there is no return value (context.isIncoming == false and context.getPageParameters() == null). The proper return value of the original request should be returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
	[jira] Assigned: (TAP5-755) URL rewriting documentation contains an example that won't compile due to lack of a return value by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/TAP5-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler reassigned TAP5-755: ----------------------------------- Assignee: Robert Zeigler > URL rewriting documentation contains an example that won't compile due to lack of a return value > ------------------------------------------------------------------------------------------------ > > Key: TAP5-755 > URL: https://issues.apache.org/jira/browse/TAP5-755 > Project: Tapestry 5 > Issue Type: Bug > Components: documentation > Affects Versions: 5.1.0.5 > Reporter: Robert Zeigler > Assignee: Robert Zeigler > Priority: Minor > > In the documentation for url rewriting, the final example shows a rule which processes incoming and outgoing requests to re-map the name of pages as visible to the user. > However, there is a chain of logic through the code in which there is no return value (context.isIncoming == false and context.getPageParameters() == null). The proper return value of the original request should be returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
	[jira] Closed: (TAP5-755) URL rewriting documentation contains an example that won't compile due to lack of a return value by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/TAP5-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler closed TAP5-755. ------------------------------- Resolution: Fixed Fix Version/s: 5.2 > URL rewriting documentation contains an example that won't compile due to lack of a return value > ------------------------------------------------------------------------------------------------ > > Key: TAP5-755 > URL: https://issues.apache.org/jira/browse/TAP5-755 > Project: Tapestry 5 > Issue Type: Bug > Components: documentation > Affects Versions: 5.1.0.5 > Reporter: Robert Zeigler > Assignee: Robert Zeigler > Priority: Minor > Fix For: 5.2 > > > In the documentation for url rewriting, the final example shows a rule which processes incoming and outgoing requests to re-map the name of pages as visible to the user. > However, there is a chain of logic through the code in which there is no return value (context.isIncoming == false and context.getPageParameters() == null). The proper return value of the original request should be returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
	[jira] Updated: (TAP5-755) URL rewriting documentation contains an example that won't compile due to lack of a return value by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/TAP5-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Zeigler updated TAP5-755: -------------------------------- Fix Version/s: (was: 5.2) 5.2.0.0 > URL rewriting documentation contains an example that won't compile due to lack of a return value > ------------------------------------------------------------------------------------------------ > > Key: TAP5-755 > URL: https://issues.apache.org/jira/browse/TAP5-755 > Project: Tapestry 5 > Issue Type: Bug > Components: documentation > Affects Versions: 5.1.0.5 > Reporter: Robert Zeigler > Assignee: Robert Zeigler > Priority: Minor > Fix For: 5.2.0.0 > > > In the documentation for url rewriting, the final example shows a rule which processes incoming and outgoing requests to re-map the name of pages as visible to the user. > However, there is a chain of logic through the code in which there is no return value (context.isIncoming == false and context.getPageParameters() == null). The proper return value of the original request should be returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
	[jira] Updated: (TAP5-755) URL rewriting documentation contains an example that won't compile due to lack of a return value by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/TAP5-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulrich Stärk updated TAP5-755: ------------------------------ Attachment: TAP5-755-5.1.txt patch against 5.1 branch > URL rewriting documentation contains an example that won't compile due to lack of a return value > ------------------------------------------------------------------------------------------------ > > Key: TAP5-755 > URL: https://issues.apache.org/jira/browse/TAP5-755 > Project: Tapestry 5 > Issue Type: Bug > Components: documentation > Affects Versions: 5.1.0.5 > Reporter: Robert Zeigler > Assignee: Robert Zeigler > Priority: Minor > Fix For: 5.2.0.0 > > Attachments: TAP5-755-5.1.txt > > > In the documentation for url rewriting, the final example shows a rule which processes incoming and outgoing requests to re-map the name of pages as visible to the user. > However, there is a chain of logic through the code in which there is no return value (context.isIncoming == false and context.getPageParameters() == null). The proper return value of the original request should be returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
	[jira] Updated: (TAP5-755) URL rewriting documentation contains an example that won't compile due to lack of a return value by JIRA jira@apache.org :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message [ https://issues.apache.org/jira/browse/TAP5-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Drobiazko updated TAP5-755: -------------------------------- Fix Version/s: 5.1.0.6 > URL rewriting documentation contains an example that won't compile due to lack of a return value > ------------------------------------------------------------------------------------------------ > > Key: TAP5-755 > URL: https://issues.apache.org/jira/browse/TAP5-755 > Project: Tapestry 5 > Issue Type: Bug > Components: documentation > Affects Versions: 5.1.0.5 > Reporter: Robert Zeigler > Assignee: Robert Zeigler > Priority: Minor > Fix For: 5.2.0.0, 5.1.0.6 > > Attachments: TAP5-755-5.1.txt > > > In the documentation for url rewriting, the final example shows a rule which processes incoming and outgoing requests to re-map the name of pages as visible to the user. > However, there is a chain of logic through the code in which there is no return value (context.isIncoming == false and context.getPageParameters() == null). The proper return value of the original request should be returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.