page services

[Ittay Dror <it...@gmail.com>]

Hi,


What is the proper way to model a registry of services per page 
instance? What I mean is for a component to be able to locate a service 
that is registered with the current page and that affects the GUI.


An example of such a service exists today: the feedback panel. 
Session.get().getFeedbackMessages returns the service that components 
can use to add feedback messages. What I'm is for a way to model a 
similar service. Is Session#getMetaData the way to do it?


Thanks,

Ittay

-- 
--
Ittay



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: page services

[Igor Vaynberg <ig...@gmail.com>]

there are both session and component-level metadata that will allow
you to store any kind of data you want.

-igor

On Mon, Jan 26, 2009 at 7:29 AM, Ittay Dror <it...@gmail.com> wrote:
> Hi,
>
>
> What is the proper way to model a registry of services per page instance?
> What I mean is for a component to be able to locate a service that is
> registered with the current page and that affects the GUI.
>
>
> An example of such a service exists today: the feedback panel.
> Session.get().getFeedbackMessages returns the service that components can
> use to add feedback messages. What I'm is for a way to model a similar
> service. Is Session#getMetaData the way to do it?
>
>
> Thanks,
>
> Ittay
>
> --
> --
> Ittay
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org