Closed GoogleCodeExporter closed 9 years ago
As a result of it's nature rest pages can't have children because they will be
shadowed by rest parameters.
Original comment by kinyelo@gmail.com
on 26 Nov 2010 at 9:14
Better way for setting page Restfull type would be additional field in
PageEntity and standard URL usage. (for search performance reasons)
Doing search from the end of URL will allow to have children pages working
properly.
Original comment by kinyelo@gmail.com
on 26 Nov 2010 at 9:38
Implemented.
Example of getting rest parameters:
page - /test
url - /test/alex/roma
In the Velocity:
$vosao.getRestParam(1) -> alex
$vosao.getRestParam(2) -> roma
$vosao.getRestParam(3) -> Java null
Original comment by kinyelo@gmail.com
on 26 Nov 2010 at 10:15
Wow, that looks great, Alex.
For completeness, do we want to include a getParam(string) to retrieve
conventional URL parameters by name? ($vosao.getParam('city'))
-Ted.
Original comment by ted.husted
on 27 Nov 2010 at 2:08
Actually we can access request parameters by
$request.getParameter("param_name"). I don't think we need to create alias
$vosao.getParam("param_name")
Original comment by kinyelo@gmail.com
on 28 Nov 2010 at 11:51
I listed all the other context objects/tools from
PageBusinessImpl.createContext, .addVelocityTools and .render, as TODO
items.
* http://staging.vosao.org/designer/doc/templates
Does that sound like the exhaustive list of context objects/tools
exposed by the core framework?
Are our plugins exposing any objects of their own (yet)?
-Ted.
Original comment by ted.husted
on 28 Nov 2010 at 2:25
Original issue reported on code.google.com by
kinyelo@gmail.com
on 26 Nov 2010 at 9:05