Am 23.08.13 00:16, schrieb Martijn Dashorst:
On Thu, Aug 22, 2013 at 11:42 PM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote:
On Thu, Aug 22, 2013 at 2:04 PM, Martijn Dashorst
<martijn.dasho...@gmail.com> wrote:
still need
pageparameters to carry those params forward in bookmarkablelink, etc.
Not necessarily: the API is still under construction. It is the
intention to remove the need for PageParameters altogether in the API.
I also prefer removing instead of wrapping it around the now code.. But:
sometimes you need a functionality where you simply pass unknown page
parameters some of your bookmarkablelinks. So there is no need to access
this functionality with the PageParameters-api, but there is a need to
have such kind of functionality.
IMHO these page parameter stuff is something like page<->external state
conversion. And is think the JAX-RS way is only one part of the game.
(Btw i don't like magic:) So i would prefer not to use
annotation-based-injection-something.)
We should reuse the conversion infrastructure we have to convert one
parameter into one value/attribute of the what-ever-mapped page state.
But in the end there should be one object/type for an state of an page.
Michael:)
