Re: Page Expired with Google Analytics Tracking Code
Hi, I tested the page and could localize the following error: page expired: http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm This means. The error occurs, when I make another search via my search form which is a normal Form with a textfield and a submit button. But, when I change the keyword in the URL (represented as q=KEYWORD parameter), the search works without the error. It seems, that the Form throws the error when the Google Analytics Code is in the header. Any idea how I can solve that problem? Andre On Fri, 06 Apr 2012 19:36:28 +0200 Bas Gooren b...@iswd.nl wrote: Hi Andre, No, we have been using the tracking code for years with wicket (1.3, 1.4 and 1.5) with 0 issues. I'm certain your Page expired error is caused by something else. From your description it sounds like your search results page is stateful, but no longer available when you perform a new search. That can happen for a variety of reasons. What usually happens to narrow the problem down is to strip the page as far as possible, and see if it works. Incrementally add components until it breaks again and you will have found the culprit. Another possibility is that you have non-standard settings for wicket session (page) management. But my guess is that this is not the case. Kind regards, Bas Op 6-4-2012 19:25, schreef Andre Schütz: Hello, did nobody have the same problem with the new Google Analytics code? I added the code directly into the .html file of my WebPage class. Andre On Thu, 5 Apr 2012 14:54:50 +0200 Andre Schützwic...@faustas.de wrote: Hello, we added the actual Google Analytics Tracking Code into our Wicket application. The code is rendered on every single page directly before the closing/head tag. Our problem is the following: Page 1 with search box - search for something Page 2 is a search site where the search request is done Page 3 is the result page, where the search result is presented We do: Page 1 - search for something Page 2 appears and shows search progress Page 3 appears and displays the results Page 3 has a search box and we start another search -- Page expired error Any ideas why this happens and how we can stop that? Thanks, Andre -- Andre Schützwic...@faustas.de - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Andre Schütz wic...@faustas.de - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: reloading of HTML and classes
I don't use ReloadingWicketFilter, but have pretty good luck reloading changed HTML and classes by simply running in debug mode in my IDE. With -Dwicket.configuration=development and running under the debugger, I can redeploy changes with reload changed classes (command+F9 in Intellij on OSX; I assume there's something similar for Eclipse.) It doesn't work if you've changed something deep in the app's startup (like say WicketApplication), but covers about 90% of my needs. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/reloading-of-HTML-and-classes-tp4537542p4539448.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: Page Expired with Google Analytics Tracking Code
Hi, I would suggest the following: 1) add a very simple test page: TestPage extends WebPage, which only has the search form on it (nothing else!) 2) see if that works multiple times in a row 3) if that works, add your google analytics code 4) repeat steps 1-2 In other words: eliminitate all other dependencies, so you can test (in isolation) if the google analytics code (or the component you've wrapped it in) is really the issue you are facing. You say that everything works ok when you add the query parameter for the search. Having that parameter means you have a form with method=get? That, to me, would indicate you can make the form stateless, which should prevent your search from redirecting to a stateful url. (The /wicket/page start of the url indicates a stateful page). But please start with steps 1-4 above to make sure you are looking in the right place for the cause of your PageExpiredException. Bas Op 7-4-2012 14:04, schreef Andre Schütz: Hi, I tested the page and could localize the following error: page expired: http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm This means. The error occurs, when I make another search via my search form which is a normal Form with a textfield and a submit button. But, when I change the keyword in the URL (represented as q=KEYWORD parameter), the search works without the error. It seems, that the Form throws the error when the Google Analytics Code is in the header. Any idea how I can solve that problem? Andre On Fri, 06 Apr 2012 19:36:28 +0200 Bas Goorenb...@iswd.nl wrote: Hi Andre, No, we have been using the tracking code for years with wicket (1.3, 1.4 and 1.5) with 0 issues. I'm certain your Page expired error is caused by something else. From your description it sounds like your search results page is stateful, but no longer available when you perform a new search. That can happen for a variety of reasons. What usually happens to narrow the problem down is to strip the page as far as possible, and see if it works. Incrementally add components until it breaks again and you will have found the culprit. Another possibility is that you have non-standard settings for wicket session (page) management. But my guess is that this is not the case. Kind regards, Bas Op 6-4-2012 19:25, schreef Andre Schütz: Hello, did nobody have the same problem with the new Google Analytics code? I added the code directly into the .html file of my WebPage class. Andre On Thu, 5 Apr 2012 14:54:50 +0200 Andre Schützwic...@faustas.de wrote: Hello, we added the actual Google Analytics Tracking Code into our Wicket application. The code is rendered on every single page directly before the closing/head tag. Our problem is the following: Page 1 with search box - search for something Page 2 is a search site where the search request is done Page 3 is the result page, where the search result is presented We do: Page 1 - search for something Page 2 appears and shows search progress Page 3 appears and displays the results Page 3 has a search box and we start another search -- Page expired error Any ideas why this happens and how we can stop that? Thanks, Andre -- Andre Schützwic...@faustas.de - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: reloading of HTML and classes
Eclipse in debug mode indeed allows for some limited reloading of classes, but JRebel does a good job and my explicit HTML code seems to work as well. I still need to test it thoroughly. But none of Wicket's regular tools seem to work and that amazes me. Tom - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 1.5 Wicket Enclosure
Hi, After creating the EnclosureContainer, add the following call : container.setRenderBodyOnly(false); In the EnclosureContainer's constructor, this is actually set to true which means that the HTML tag is not part of the rendered markup if the Enclosure is not visible on first render. When made visible afterwards via Ajax, Wicket js cannot find the tag to replace with the enclosure's content. In my opinion, this is a bug and a JIRA issue should be created. On 07/04/2012 1:46 AM, Douglas Ferguson wrote: Is this expected behavior? Is there a workaround? On Apr 5, 2012, at 6:58 PM, Douglas Ferguson wrote: I just found a different between 1.4 and 1.5 with regards to wicket enclosure. If you have a component in a wicket enclosure (say a feedback panel) and you set it visible false. Then subsequently try to set it visible true, wicket 1.5 will not be able to make it reappear. 1.4 had no problem with this. I get this in the debugger console: ERROR: Wicket.Ajax.Call.processComponent: Component with id [[id3]] was not found while trying to perform markup update. Make sure you called component.setOutputMarkupId(true) on the component whose markup you are trying to update. Douglas - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page Expired with Google Analytics Tracking Code
Thank you for the answer, I will try your 4 steps. Just as information. When you say, that I can make the form stateless, do you talk about the StatelessForm class? Andre On Sat, 07 Apr 2012 16:06:15 +0200 Bas Gooren b...@iswd.nl wrote: Hi, I would suggest the following: 1) add a very simple test page: TestPage extends WebPage, which only has the search form on it (nothing else!) 2) see if that works multiple times in a row 3) if that works, add your google analytics code 4) repeat steps 1-2 In other words: eliminitate all other dependencies, so you can test (in isolation) if the google analytics code (or the component you've wrapped it in) is really the issue you are facing. You say that everything works ok when you add the query parameter for the search. Having that parameter means you have a form with method=get? That, to me, would indicate you can make the form stateless, which should prevent your search from redirecting to a stateful url. (The /wicket/page start of the url indicates a stateful page). But please start with steps 1-4 above to make sure you are looking in the right place for the cause of your PageExpiredException. Bas Op 7-4-2012 14:04, schreef Andre Schütz: Hi, I tested the page and could localize the following error: page expired: http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm This means. The error occurs, when I make another search via my search form which is a normal Form with a textfield and a submit button. But, when I change the keyword in the URL (represented as q=KEYWORD parameter), the search works without the error. It seems, that the Form throws the error when the Google Analytics Code is in the header. Any idea how I can solve that problem? Andre On Fri, 06 Apr 2012 19:36:28 +0200 Bas Goorenb...@iswd.nl wrote: Hi Andre, No, we have been using the tracking code for years with wicket (1.3, 1.4 and 1.5) with 0 issues. I'm certain your Page expired error is caused by something else. From your description it sounds like your search results page is stateful, but no longer available when you perform a new search. That can happen for a variety of reasons. What usually happens to narrow the problem down is to strip the page as far as possible, and see if it works. Incrementally add components until it breaks again and you will have found the culprit. Another possibility is that you have non-standard settings for wicket session (page) management. But my guess is that this is not the case. Kind regards, Bas Op 6-4-2012 19:25, schreef Andre Schütz: Hello, did nobody have the same problem with the new Google Analytics code? I added the code directly into the .html file of my WebPage class. Andre On Thu, 5 Apr 2012 14:54:50 +0200 Andre Schützwic...@faustas.de wrote: Hello, we added the actual Google Analytics Tracking Code into our Wicket application. The code is rendered on every single page directly before the closing/head tag. Our problem is the following: Page 1 with search box - search for something Page 2 is a search site where the search request is done Page 3 is the result page, where the search result is presented We do: Page 1 - search for something Page 2 appears and shows search progress Page 3 appears and displays the results Page 3 has a search box and we start another search -- Page expired error Any ideas why this happens and how we can stop that? Thanks, Andre -- Andre Schützwic...@faustas.de - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Andre Schütz wic...@faustas.de - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page Expired with Google Analytics Tracking Code
Yes. Op 7-4-2012 20:37, schreef Andre Schütz: Thank you for the answer, I will try your 4 steps. Just as information. When you say, that I can make the form stateless, do you talk about the StatelessForm class? Andre On Sat, 07 Apr 2012 16:06:15 +0200 Bas Goorenb...@iswd.nl wrote: Hi, I would suggest the following: 1) add a very simple test page: TestPage extends WebPage, which only has the search form on it (nothing else!) 2) see if that works multiple times in a row 3) if that works, add your google analytics code 4) repeat steps 1-2 In other words: eliminitate all other dependencies, so you can test (in isolation) if the google analytics code (or the component you've wrapped it in) is really the issue you are facing. You say that everything works ok when you add the query parameter for the search. Having that parameter means you have a form with method=get? That, to me, would indicate you can make the form stateless, which should prevent your search from redirecting to a stateful url. (The /wicket/page start of the url indicates a stateful page). But please start with steps 1-4 above to make sure you are looking in the right place for the cause of your PageExpiredException. Bas Op 7-4-2012 14:04, schreef Andre Schütz: Hi, I tested the page and could localize the following error: page expired: http://localhost:8080/wicket/page?7-1.IFormSubmitListener-resultsContent-searchPanel-searchForm This means. The error occurs, when I make another search via my search form which is a normal Form with a textfield and a submit button. But, when I change the keyword in the URL (represented as q=KEYWORD parameter), the search works without the error. It seems, that the Form throws the error when the Google Analytics Code is in the header. Any idea how I can solve that problem? Andre On Fri, 06 Apr 2012 19:36:28 +0200 Bas Goorenb...@iswd.nl wrote: Hi Andre, No, we have been using the tracking code for years with wicket (1.3, 1.4 and 1.5) with 0 issues. I'm certain your Page expired error is caused by something else. From your description it sounds like your search results page is stateful, but no longer available when you perform a new search. That can happen for a variety of reasons. What usually happens to narrow the problem down is to strip the page as far as possible, and see if it works. Incrementally add components until it breaks again and you will have found the culprit. Another possibility is that you have non-standard settings for wicket session (page) management. But my guess is that this is not the case. Kind regards, Bas Op 6-4-2012 19:25, schreef Andre Schütz: Hello, did nobody have the same problem with the new Google Analytics code? I added the code directly into the .html file of my WebPage class. Andre On Thu, 5 Apr 2012 14:54:50 +0200 Andre Schützwic...@faustas.dewrote: Hello, we added the actual Google Analytics Tracking Code into our Wicket application. The code is rendered on every single page directly before the closing/headtag. Our problem is the following: Page 1 with search box -search for something Page 2 is a search site where the search request is done Page 3 is the result page, where the search result is presented We do: Page 1 -search for something Page 2 appears and shows search progress Page 3 appears and displays the results Page 3 has a search box and we start another search --Page expired error Any ideas why this happens and how we can stop that? Thanks, Andre -- Andre Schützwic...@faustas.de - 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: reloading of HTML and classes
Hi,
The HTML part is covered if your IDE copies HTML files to the
deployment directory when you save them. Wicket will then pick up this
change and reload the corresponding pages. This works for existing
markup but not for new markup that was missing.
The Java classes part can only be handled with debugging, JRebel or a
complete re-deployment. There is no hot-deployment of individual
classes in GlassFish (I don't know whether any other server supports
this). However GlassFish has session preservation so the re-deploy
process is seamless. To further speed up the deployment, one can copy
most libraries (including Wicket) into the GlassFish domain's lib dir
instead of copying them on every deployment.
The Deploy on Save feature is only useful for mini applications - it
is too slow.
Bernard
On Fri, 06 Apr 2012 16:48:11 +0200, you wrote:
I've been fighting this for the past two days, but I'm not succeeding. I'm
using Wicket 1.5.5 on GlassFish 3.1.2 and that runs without a problem. I have
configured
filter-classorg.apache.wicket.protocol.http.ReloadingWicketFilter/filter-class
to reload the classes, but that is not working. The only way to reload the
class file is by using JRebel.
Also Wicket reports that it runs in DEVELOPMENT mode, but it is not reloading
the HTML files. In an attempting to resolve that I explicitely configured
getResourceSettings().setDefaultCacheDuration(Duration.ONE_SECOND);
but that does not make a difference. The only way I can get it to work
somewhat, is to add my own ResourceFinder directly on the src folder:
getResourceSettings().setResourceFinder(new IResourceFinder()
{
@Override
public IResourceStream find(Class? clazz, String pathname)
{
File f = new File(C:/Documents and Settings/User/My
Documents/s2m/sources/components/service/src/main/java/ + pathname);
if (f.exists())
{
return new FileResourceStream( f );
}
return null;
}
});
getResourceSettings().setUseDefaultOnMissingResource(true);
But still the source are not reloaded reliably. I figure if the cache expires,
a new call to the resource finder should be done, correct?
Is there any debugging of these autoreload features, so I can see what Wicket
is doing?
Tom
-
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
Wicket and Menu support
Wicket is a great product and I really hope that I do not offend any one by my question. Indeed this may be due to my lack of information. What I want to know is why does not Wicket 'core' supports menu and other items necessary to develop a website? I have to search for YUI wicket, wicket-stuff, and wicket-extensions, which are some what phantom like websites. After some research I find that the code I am looking for is not even supported any more. The kind developer has moved on to other stuff. So what is the qualification for you to include a control(?) into the Wicket 'core'? What is the suggested way to handle stuff like this? Thanks. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Menu-support-tp4540516p4540516.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: Wicket and Menu support
IMHO, Wicket as the largest number of out of the box components of all the frameworks that i know. For such things as menus, are they not 'ulli' that have been styled the way you want.. I think the key thing is ... if you are not familiar with HTML and CSS, you may not like wicket. Because if leaves writting html and styling the elements to you. Josh. On Sun, Apr 8, 2012 at 8:19 AM, msalman mohammad_sal...@yahoo.com wrote: Wicket is a great product and I really hope that I do not offend any one by my question. Indeed this may be due to my lack of information. What I want to know is why does not Wicket 'core' supports menu and other items necessary to develop a website? I have to search for YUI wicket, wicket-stuff, and wicket-extensions, which are some what phantom like websites. After some research I find that the code I am looking for is not even supported any more. The kind developer has moved on to other stuff. So what is the qualification for you to include a control(?) into the Wicket 'core'? What is the suggested way to handle stuff like this? Thanks. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Menu-support-tp4540516p4540516.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: Wicket and Menu support
Well you are right that I am not good with html and css. As I say I have been forced to do GUI work - kicking and screaming. Well, I think I am OK with html but this CSS thing leaves me very frustrated. I thought that the idea behind Wicket is to take care of these things for Java programmers. I would appreciate if some basic form of menu is made part of wicket core. BTW, thanks for the ULli hint. Thanks. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Menu-support-tp4540516p4540539.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
