On Mon, Aug 11, 2008 at 9:40 AM, Lorenzo Bolzani <[EMAIL PROTECTED]> wrote:
> So you are saying that wicket does not provide a standard way for page
> configuration.
> So I'll develop a custom solution based on spring or on property files.
there is no one-way-fits-all way of configuring pages, thi
2008/8/11 Igor Vaynberg <[EMAIL PROTECTED]>:
> then have your page look it up itself from the spring context using
> some registry
>
> class mypage extends webpage {
> @SpringBean private PageConfigRegistry registry;
>
> public mypage() {
>mydata data=(mydata)registry.getdatafor(getclass());
>>>>> spring)? I found nothing about this in the docs.
>>>>> In this way I could pass in the ref name (device1 or device2) and make
>>>>> it work with an explicit spring context lookup (no injection
ther words I need two instances of the same page configured in two
>>>>> different ways.
>>>>> Is this possibile? How can I pass in the parameters (with or without
>>>>> spring)? I found nothing about this in the docs.
>>>>> In th
>>
>>>> Thanks for any suggestions.
>>>>
>>>>
>>>> Bye
>>>>
>>>> Lorenzo
>>>>
>>>> -
>>>> To unsubscribe, e-ma
of the two different parameters.
>>>
>>> Thanks for any suggestions.
>>>
>>>
>>> Bye
>>>
>>> Lorenzo
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTE
Hi Igor, I tried your suggestion and it works but looks like a
workaround more than a solution.
I have many pages that need some configuration. This is server side
configuration, for example how often a page should refresh itself.
I tryed to pass in these parameters as PageParameters but in this w
well normally you would just do
class monitorpage extends webpage {
public monitorpage(string deviceid) {
.. do whatever with deviceid
}
}
if you need your pages to be bookmarkable then just use
class monitorpage extends webpage {
public monitorpage(pageparameters params) {
string
Hi all, I have a page to monitor the status of a remote device.
The page just stay there and refresh automatically to display the actual state.
The problem is that I need to have to distinct pages to monitor two
distinct devices.
My ideal approach would be to define two pages in spring, something
