Re: Back button problem in wicket
Hi, Thanks for the help... problem is solved.. i integrated spring and wicket.. but a new problem has come.. it is saying me to serialize the service class although it is not affecting the problem of back button if i don't serialize but still throwing an exception.. I don't wanna serialize my service class.. Please tell me what is the problem and how to solve it.. -- Thanks in advance -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Back-button-problem-in-wicket-tp3480260p3483270.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Back button problem in wicket
use spring bean On Fri, Apr 29, 2011 at 2:55 PM, madaan18 madaa...@gmail.com wrote: Hi, Thanks for the help... problem is solved.. i integrated spring and wicket.. but a new problem has come.. it is saying me to serialize the service class although it is not affecting the problem of back button if i don't serialize but still throwing an exception.. I don't wanna serialize my service class.. Please tell me what is the problem and how to solve it.. -- Thanks in advance -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Back-button-problem-in-wicket-tp3480260p3483270.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Back button problem in wicket
On Fri, Apr 29, 2011 at 12:31 PM, vineet semwal vineetsemwal1...@gmail.com wrote: use spring bean @vineet: Better use '@SpringBean' because it is not very clear what you mean ;-) @madaan18: show us some code so we can tell you for sure what the problem is On Fri, Apr 29, 2011 at 2:55 PM, madaan18 madaa...@gmail.com wrote: Hi, Thanks for the help... problem is solved.. i integrated spring and wicket.. but a new problem has come.. it is saying me to serialize the service class although it is not affecting the problem of back button if i don't serialize but still throwing an exception.. I don't wanna serialize my service class.. Please tell me what is the problem and how to solve it.. -- Thanks in advance -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Back-button-problem-in-wicket-tp3480260p3483270.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- thank you, regards, Vineet Semwal - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Back button problem in wicket
martin-g : heh yeah i realized it after hitting on submit but then i thought he will figure it out ,thanks :) - vineet semwal -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Back-button-problem-in-wicket-tp3480260p3483658.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Back button problem in wicket
Hi, what does your application/web server's log say? You should check it for some Wicket message or exception that could explain page expiration. Hey, I am new to wicket.. I was having problem of back button in wicket.. but it got solved when i made all the pages and service class serializable.. but when i integrated my project with spring configuration.. i again faced the problem of back button in my project.. why does it happen ??? is it because of spring or something else Back button problem : I am on page 1 go 2 page 2 , then using back button i go to page 1 then on clicking a button , i get page expired... Please reply soon.. I need it very urgent -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Back-button-problem-in-wicket-tp3480260p3480260.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Back button problem in wicket
Hi, It sounds like you use spring dependency injection directly, which will indeed cause serialization issues. Instead, use the wicket spring integration, which will inject serializable proxies. See https://cwiki.apache.org/WICKET/spring.html for more info. Bas Op 28-4-2011 8:36, schreef madaan18: Hey, I am new to wicket.. I was having problem of back button in wicket.. but it got solved when i made all the pages and service class serializable.. but when i integrated my project with spring configuration.. i again faced the problem of back button in my project.. why does it happen ??? is it because of spring or something else Back button problem : I am on page 1 go 2 page 2 , then using back button i go to page 1 then on clicking a button , i get page expired... Please reply soon.. I need it very urgent -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Back-button-problem-in-wicket-tp3480260p3480260.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Back button problem with form
I still don't get it. If I check another radio button and press submit it would still do a post from wicket right? -- View this message in context: http://www.nabble.com/Back-button-problem-with-form-tp17512965p17574963.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem with form
After some debugging I solved it in a ugly way. I used PropertyModel() for the form and when I pressed submit the object did'nt update in a correct manner. I think it has to do with that the object is in the session. When I used Model() instead it worked. -- View this message in context: http://www.nabble.com/Back-button-problem-with-form-tp17512965p17575290.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem with form
After some debugging I solved it in a ugly way. I used PropertyModel() for the form and when I pressed submit the object did'nt update in a correct manner. I think it has to do with that the object is in the session. Weird. Did you check that the target of the property model was the one you intended? It sounds like you might have been referring to a stale object. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem with form
On Thu, 29 May 2008, Marieke Vandamme wrote: I noticed the same behavior in firefox, but for me everything works fine in internet explorer. My form is not working with ajax, but with the standard submit. Is it browser specific or can I change the behavior in my code? Probably it depends on the browser cache settings, you might get it working consistently by adding proper caching headers. (to never cache the page after pressing back button). You can debug it by looking at whthe requests your browser produces. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations OyURL: http://www.ri.fi/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem
So you see the initial state instead of the latest ajax state? This is a browser problem, i believe ms is fixing that for ie in number 8. You can go around it by letting the backbutton always go to the server, look at configureResponse/setheaders of webpage an add nostore On 3/27/08, bhitai [EMAIL PROTECTED] wrote: Hi Igor thanks for the prompt reply..I'm trying to figure out how exactly to do that. This is because I have the following situation and I don't know where to apply the url coding strategy: 1. there are two pages, one is a menu and one detail page 2. menu page displays objects in a hierarchy - to drill down a category into sub-category and so on, when you click on it. 3. the application class loads the page MenuPage as the home page. 4. the home page displays items of the top level, adding AjaxBehavior on each item so when it is clicked, a drill-down operation is called on the corresponding menu item on the server. 5. the drill down operation basically loads the children of that item, recreates the menu panel on the page and adds that to the AjaxRequestTarget. 6. so now we have a brand new page content, which might have links to the DetailPage, which is a new page and will be reloaded. if the user now clicks on that link, he will be taken to the new page, and there begins the back button issue. When the user comes back he sees the contents as they appeared in step #4, that is the top level menu. Once you click on an a menu item just to test, that's where it blows up and gives the exception. Now I'm having trouble figuring out which page should be applied the coding strategy to. I am loading page A and page B both using setResponsePage(MenuPage.class) and setResponsePage(new DetailPage(id)). How do I introduce urls here, can you pls help a little bit? thanks jeff -- View this message in context: http://www.nabble.com/Back-button-problem-tp16313414p16319071.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem
Hi Igore
I have some code to share now. This is what I did:
in the constructor for the Application, I mount pages with hybridUrlCoding
strategy as suggested by you.
mount(new HybridUrlCodingStrategy(home, MenuPage.class));
mount(new HybridUrlCodingStrategy(product,
ProductDetailPage.class));
Now I can see different versions of pages being created unlike before..
However, the Ajax links I'm adding at various places are still showing the
old format..
On my menu page (that gets updated through AJAX) over and over, I create
menu items like this :
public class MenuFragment extends Fragment {
Listable item ;
public MenuFragment(String id, final Listable item, final
MenuPage page) {
super(id, fragment);
this.item = item;
setOutputMarkupId(true);
add(new Label(name, item.getName()));
add(new ExternalImage(img, item));
add(new AjaxEventBehavior(onclick) {
@Override
protected void onEvent(AjaxRequestTarget target) {
page.reload(item, target);
}
});
}
}
Is this the right approach? Or should I use some AjaxFallbackLink type of
object instead of adding a clikable behavior to a div? My Listable interface
basically has the primary key of the category, and Class name of the objects
to be loaded (this is what what I do in page.reload) for that category.
--
View this message in context:
http://www.nabble.com/Back-button-problem-tp16313414p16324501.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem
my suggestion is to make it work without ajax first, that way you know
everything is correctly setup. then add ajax into the mix.
-igor
On Thu, Mar 27, 2008 at 4:46 AM, bhitai [EMAIL PROTECTED] wrote:
Hi Igore
I have some code to share now. This is what I did:
in the constructor for the Application, I mount pages with hybridUrlCoding
strategy as suggested by you.
mount(new HybridUrlCodingStrategy(home, MenuPage.class));
mount(new HybridUrlCodingStrategy(product,
ProductDetailPage.class));
Now I can see different versions of pages being created unlike before..
However, the Ajax links I'm adding at various places are still showing the
old format..
On my menu page (that gets updated through AJAX) over and over, I create
menu items like this :
public class MenuFragment extends Fragment {
Listable item ;
public MenuFragment(String id, final Listable item, final
MenuPage page) {
super(id, fragment);
this.item = item;
setOutputMarkupId(true);
add(new Label(name, item.getName()));
add(new ExternalImage(img, item));
add(new AjaxEventBehavior(onclick) {
@Override
protected void onEvent(AjaxRequestTarget target) {
page.reload(item, target);
}
});
}
}
Is this the right approach? Or should I use some AjaxFallbackLink type of
object instead of adding a clikable behavior to a div? My Listable interface
basically has the primary key of the category, and Class name of the objects
to be loaded (this is what what I do in page.reload) for that category.
--
View this message in context:
http://www.nabble.com/Back-button-problem-tp16313414p16324501.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem
mount your pages using hybridurlcodingstrategy -igor On Wed, Mar 26, 2008 at 12:05 PM, bhitai [EMAIL PROTECTED] wrote: I am a new wicket user, and have been trying to develop an application for the past few weeks. What I initially did was to use some databinder API to fetch persistent objects, and heavily using AJAX to refresh parts of pages rather than reloads. Now I'm having an issue with back button. Let's say I'm on Page A. This page is refreshed thru AJAX calls many times and the original contents are long gone. Now I go to a new page, page B, and from there press back button. Now page A is present on the browser, but apparently its contents have been overwritten, since as soon as I do a back button, I get this exception : component XX not found on page A (basically XX is the component that was loaded the 1st time - and was later replaced by other components) The browser seems to be bringing up the html-based content of page A when it was loaded the 1st time around. Of course I have since over-written its contents through AJAX calls. Now how do we bring back a page that has been AJAX updated but not refreshed by the browser? thanks in advance, jeff -- View this message in context: http://www.nabble.com/Back-button-problem-tp16313414p16313414.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Back button problem
Hi Igor thanks for the prompt reply..I'm trying to figure out how exactly to do that. This is because I have the following situation and I don't know where to apply the url coding strategy: 1. there are two pages, one is a menu and one detail page 2. menu page displays objects in a hierarchy - to drill down a category into sub-category and so on, when you click on it. 3. the application class loads the page MenuPage as the home page. 4. the home page displays items of the top level, adding AjaxBehavior on each item so when it is clicked, a drill-down operation is called on the corresponding menu item on the server. 5. the drill down operation basically loads the children of that item, recreates the menu panel on the page and adds that to the AjaxRequestTarget. 6. so now we have a brand new page content, which might have links to the DetailPage, which is a new page and will be reloaded. if the user now clicks on that link, he will be taken to the new page, and there begins the back button issue. When the user comes back he sees the contents as they appeared in step #4, that is the top level menu. Once you click on an a menu item just to test, that's where it blows up and gives the exception. Now I'm having trouble figuring out which page should be applied the coding strategy to. I am loading page A and page B both using setResponsePage(MenuPage.class) and setResponsePage(new DetailPage(id)). How do I introduce urls here, can you pls help a little bit? thanks jeff -- View this message in context: http://www.nabble.com/Back-button-problem-tp16313414p16319071.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
