Re: Version Pages by default

2012-04-02 Thread Martin Grigorov
On Mon, Apr 2, 2012 at 6:37 AM, sudeivas sureshkumar@gmail.com wrote: I have made changes in the code to set all the parameters in the Session. Now the URL looks clean. http:///pageB?5 But in pageB's constructor after reading values from session I am not clearing it as we need those

Re: Version Pages by default

2012-04-02 Thread sudeivas
Now I am using IRequestMapper cryptoMapper = new CryptoMapper(getRootRequestMapper(), this); setRootRequestMapper(cryptoMapper); By this way the page parameters are encrypted. I hope it will not affect recreating the page from page mount when the page expiration happens. Also can you please

Re: Version Pages by default

2012-04-02 Thread Martin Grigorov
On Mon, Apr 2, 2012 at 6:28 PM, sudeivas sureshkumar@gmail.com wrote: Now I am using IRequestMapper cryptoMapper = new CryptoMapper(getRootRequestMapper(), this); setRootRequestMapper(cryptoMapper); By this way the page parameters are encrypted. I hope it will not affect recreating the

Re: Version Pages by default

2012-04-01 Thread Martin Grigorov
Using setResponsePage(Page) wont work. This will create url like: .../wicket/page?6 and there is no way to find what is the type of the page behind this url. Using setResponsePage(Class) the url will be .../pageB and this is what is needed to find out which Page implementation to use after session

Re: Version Pages by default

2012-04-01 Thread sudeivas
I have made changes in the code to set all the parameters in the Session. Now the URL looks clean. http:///pageB?5 But in pageB's constructor after reading values from session I am not clearing it as we need those values in the session. When the page expiration happens, when wicket tries to

Re: Version Pages by default

2012-03-31 Thread Martin Grigorov
On Sat, Mar 31, 2012 at 12:29 AM, sudeivas sureshkumar@gmail.com wrote: Thanks for the information. I am currently using wicket 1.5.3. I hope this applies to wicket-1.5.3 as well. Yes But in my case, everything works fine. But when our session management fails, then we run into the

Re: Version Pages by default

2012-03-31 Thread vineet semwal
for creation ,is it done like this in wicket if(page is creatable){ create}else{ throw pageexpiredexception} else there can be a loop of pageexpiredexception just curious.. On Sat, Mar 31, 2012 at 12:53 PM, Martin Grigorov mgrigo...@apache.org wrote: On Sat, Mar 31, 2012 at 12:29 AM, sudeivas

Re: Version Pages by default

2012-03-31 Thread vineet semwal
oh sorry corrected a bit On Sat, Mar 31, 2012 at 1:50 PM, vineet semwal vineetsemwal1...@gmail.com wrote: for creation ,is it done like this in wicket if(page is creatable){ create}else{ /*throw pageexpiredexception*/ redirect to error page } else there can be a loop of pageexpiredexception

Re: Version Pages by default

2012-03-31 Thread sudeivas
I believe the best solution for me is to update my project to the latest version of wicket, but still I am worried about the following issue, https://issues.apache.org/jira/browse/WICKET-4454 since lot of our code have nested components. Any idea when 1.5.6 will be released? (so that I can wait

Re: Version Pages by default

2012-03-31 Thread Martin Grigorov
On Sat, Mar 31, 2012 at 6:22 PM, sudeivas sureshkumar@gmail.com wrote: I believe the best solution for me is to update my project to the latest version of wicket, but still I am worried about the following issue, https://issues.apache.org/jira/browse/WICKET-4454 since lot of our code

Re: Version Pages by default

2012-03-31 Thread sudeivas
The problem in our application is there is no fixed path except for the home page. From the home page the user will navigate to a different page after clicking on a ajax link (we use setResponsePage(new PageB(Object x)). In Page B we have lot of widgets getting populated dynamically based on

Re: Version Pages by default

2012-03-31 Thread Martin Grigorov
You need to mount PageB with mountPage(/pageb, PageB.class) and use setResponsePage(PageB.class, parameters) 'parameters' should bring a key/value that will be used to create a proper objectX, e.g. a key which will be used to load an entity from DB. And there is no need to use AjaxLink if you

Re: Version Pages by default

2012-03-31 Thread sudeivas
This idea sounds good to me rather than just passing the whole JAVA object. But this raises an another question. Since I am just passing PageParameters to the page, in the beginning it will be a stateless page. But when I start using Ajax components inside the page, then it becomes a stateful page

Re: Version Pages by default

2012-03-31 Thread Martin Grigorov
On Sat, Mar 31, 2012 at 10:05 PM, sudeivas sureshkumar@gmail.com wrote: This idea sounds good to me rather than just passing the whole JAVA object. But this raises an another question. Since I am just passing PageParameters to the page, in the beginning it will be a stateless page. But when

Re: Version Pages by default

2012-03-30 Thread Martin Grigorov
Hi, Check the docs from 6.x: http://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=blob_plain;f=wicket-core/src/main/java/org/apache/wicket/settings/IPageSettings.java;hb=master On Fri, Mar 30, 2012 at 11:30 PM, sudeivas sureshkumar@gmail.com wrote: Hello,          I am just

Re: Version Pages by default

2012-03-30 Thread sudeivas
Thanks for the information. I am currently using wicket 1.5.3. I hope this applies to wicket-1.5.3 as well. But in my case, everything works fine. But when our session management fails, then we run into the following exceptions: PageExpiredException ComponentNotFoundException