Re: OT - GrepCode
Igor, It looks like according to the Apache PRC policy, external links are allowed with a "nofollow" attribute. Does that help? Thanks, Vinayak Igor Vaynberg wrote: i use grepcode all the time and think its a great tool. personally i wouldnt mind putting a [search with grepcode] box on our page, but the site has to conform with apache rules and policies and im not sure how that plays in. martijn might be able to shed more light. -igor On Sun, Jun 28, 2009 at 5:12 PM, Vinayak Borkar wrote: Guys, I had sent a mail to this mailing list a few months ago about http://grepcode.com, a Java source code search engine. Over the last few months, we have added more repositories and more features -- for example, stack trace search. I was wondering if it would be a useful for users of the Wicket project to be able to search source code in the wicket family through a link on the main Wicket page. Please let me know your thoughts. Thanks, Vinayak - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
OT - GrepCode
Guys, I had sent a mail to this mailing list a few months ago about http://grepcode.com, a Java source code search engine. Over the last few months, we have added more repositories and more features -- for example, stack trace search. I was wondering if it would be a useful for users of the Wicket project to be able to search source code in the wicket family through a link on the main Wicket page. Please let me know your thoughts. Thanks, Vinayak - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page instantiated twice
Martijn, Ok. I set the getStatelessHint() to return false. Now I get java.lang.IllegalStateException: No SessionHandler or SessionManager What is the reason that wicket needs to instantiate the page twice? I can understand the second instantiation, but my guess is that the first instantiation is not to render the HTML. If I am correct about my analysis above, is there some way I can know that the instantiation does not need to populate all the components? Thanks, Vinayak Martijn Dashorst wrote: Your page is stateless, which is a holy grail for most to attend. Be happy :) Since it is stateless, Wicket has to construct the page with each request, until it is no longer stateless. If you have a form, override its getstatelesshint method and return false. Martijn On Tue, Mar 31, 2009 at 8:36 AM, Vinayak Borkar wrote: Jeremy, I did that. The first time it is at org.apache.wicket.request.target.component.BookmarkableListenerInterfaceRequestTarget.processEvents(BookmarkableListenerInterfaceRequestTarget.java:127) and the second time it is at org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.processEvents(BookmarkablePageRequestTarget.java:223) Does that help? Thanks, Vinayak Jeremy Thomerson wrote: Run it in debug mode, put a breakpoint in your constructor and see what's instantiating each. A lot of times it is your own code (a bad link, etc). -- Jeremy Thomerson http://www.wickettraining.com On Tue, Mar 31, 2009 at 1:30 AM, Vinayak Borkar wrote: Hello, I have a form that performs a search and shows a page with results. The result page also has the same form to do a repeat search. I noticed that the SearchPage is instantiated twice when I do a search from the form on the result page. Is there a way to make sure that does not happen? The search page ends up doing the search twice. Thanks, Vinayak - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page instantiated twice
Martijn, Does setting the statelessHint to false indicate that the form is stateful? In that case, would Wicket try to serialize the form? Thanks, Vinayak Martijn Dashorst wrote: Your page is stateless, which is a holy grail for most to attend. Be happy :) Since it is stateless, Wicket has to construct the page with each request, until it is no longer stateless. If you have a form, override its getstatelesshint method and return false. Martijn On Tue, Mar 31, 2009 at 8:36 AM, Vinayak Borkar wrote: Jeremy, I did that. The first time it is at org.apache.wicket.request.target.component.BookmarkableListenerInterfaceRequestTarget.processEvents(BookmarkableListenerInterfaceRequestTarget.java:127) and the second time it is at org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.processEvents(BookmarkablePageRequestTarget.java:223) Does that help? Thanks, Vinayak Jeremy Thomerson wrote: Run it in debug mode, put a breakpoint in your constructor and see what's instantiating each. A lot of times it is your own code (a bad link, etc). -- Jeremy Thomerson http://www.wickettraining.com On Tue, Mar 31, 2009 at 1:30 AM, Vinayak Borkar wrote: Hello, I have a form that performs a search and shows a page with results. The result page also has the same form to do a repeat search. I noticed that the SearchPage is instantiated twice when I do a search from the form on the result page. Is there a way to make sure that does not happen? The search page ends up doing the search twice. Thanks, Vinayak - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page instantiated twice
Jeremy, I did that. The first time it is at org.apache.wicket.request.target.component.BookmarkableListenerInterfaceRequestTarget.processEvents(BookmarkableListenerInterfaceRequestTarget.java:127) and the second time it is at org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.processEvents(BookmarkablePageRequestTarget.java:223) Does that help? Thanks, Vinayak Jeremy Thomerson wrote: Run it in debug mode, put a breakpoint in your constructor and see what's instantiating each. A lot of times it is your own code (a bad link, etc). -- Jeremy Thomerson http://www.wickettraining.com On Tue, Mar 31, 2009 at 1:30 AM, Vinayak Borkar wrote: Hello, I have a form that performs a search and shows a page with results. The result page also has the same form to do a repeat search. I noticed that the SearchPage is instantiated twice when I do a search from the form on the result page. Is there a way to make sure that does not happen? The search page ends up doing the search twice. Thanks, Vinayak - 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
Page instantiated twice
Hello, I have a form that performs a search and shows a page with results. The result page also has the same form to do a repeat search. I noticed that the SearchPage is instantiated twice when I do a search from the form on the result page. Is there a way to make sure that does not happen? The search page ends up doing the search twice. Thanks, Vinayak - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
OT: Code Search Engine for Java using wicket
Hello fellow Wicketeers, We have released a beta version of a code search engine for open source Java code, that uses Wicket v1.4. You could search for wicket by following the link: http://grepcode.com/search/?query=wicket Thanks for all the help you guys have been, with my wicket related problems. Any feedback would be appreciated. Thanks, Vinayak - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Static generation of pages from Wicket
James, We are planning to use Amazon S3 to host all static pages -- The idea is to create a CNAME to the vhost on S3. This way all pages get served from S3. How would I use the caching filter to do this? I have no way to intercept the request once it is made to S3. Thanks, Vinayak James Carman wrote: You could just introduce a caching filter in front of the pages, right? On Wed, Mar 4, 2009 at 12:54 PM, Vinayak Borkar wrote: Hello, What is the recommended technique for generation of pages (usually served by wicket in a web server), statically so that they can be served by say, a CDN. I want to use Wicket since its great for iterative development. However, all my pages are stateless and hence do not need to persist state on the server. In order to scale, I want to generate the pages in an offline stage and distribute them on a CDN. One option I have is to use wget to build the entire site statically. Is there a more "Wicket" approach to do this? What techniques would you suggest? Thanks, Vinayak - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Static generation of pages from Wicket
Hello, What is the recommended technique for generation of pages (usually served by wicket in a web server), statically so that they can be served by say, a CDN. I want to use Wicket since its great for iterative development. However, all my pages are stateless and hence do not need to persist state on the server. In order to scale, I want to generate the pages in an offline stage and distribute them on a CDN. One option I have is to use wget to build the entire site statically. Is there a more "Wicket" approach to do this? What techniques would you suggest? Thanks, Vinayak - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Stateless form action in Wicket
Hello, I am creating a page (say Page A) that contains a stateless form. The stateless form's action leads to page B. I observe that in Wicket, the form action is created so that the request is sent back to Page A (An instance of Page A is created when the form is submitted) and then it redirects to Page B. Is that correct ? If so, what is the reason for that? How do I get Wicket to create the form so that the action goes directly to Page B. i.e. Page A is NOT instantiated on the submission of the form. Thanks, Vinayak - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Passing simple data between java code and the template
Hi,
I have some Javascript code in one of my pages. I want to keep this JS
in the template file. However, this JS has a variable whose value is
derived from a page parameter.
For example,
Is there a way I can do something like, ${value} in the template file
and have the actual value be substituted by wicket?
What is the best practice to have simple values substituted in templates?
Thanks,
Vinayak
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Simple GET based stateless form
Stefan, What I see on your site is exactly the behaviour I wish to have. However, using the code you pasted, still gives me this as the end of my URL, the second time. searchForm1_hf_0=&..%2F..%2F..%2Fsearch%2Fwicket%3Ainterface%2F%3A0%3Asearch-bar%3AsearchForm%3A%3AIFormSubmitListener%3A%3A%2F=&query=jboss&%3Asubmit=Submit+Query I wonder what I am doing wrong. Thanks, Vinayak Stefan Lindner wrote: In the onSubmit method of your form place something like PageParameters p = new PageParameters(); // add your search parameters here getRequestCycle().setRequestTarget(new RedirectRequestTarget(urlFor(MySearchResults.class, p).toString())); Try out http://www.ai-online.info/abstracts/RefresherCourse, search for something and see the url to decide if you are looking for my solution. Thanks to Igor for the initial hint. -Ursprüngliche Nachricht- Von: Vinayak Borkar [mailto:[EMAIL PROTECTED] Gesendet: Montag, 17. November 2008 08:47 An: users@wicket.apache.org Betreff: Simple GET based stateless form Hi, I am trying to create a simple GET based stateless form to implement search. My code is broken up into two parts 1. A SearchPanel component that renders the form containing the text field 2. A SearchPage that renders the search results. The search page also has the SearchPanel component embedded in it so it would show a text field for the user to search again. The SearchPage page is mounted using the mountBookmarkablePage() call, so the URL for the search page is great the first time someone does a search. However, if a search is performed a second time from the form on the SearchPage, the URL for the new serach page has a bunch of extra wicket specific attributes. How do I make the URL seen in the second search as clean as the first? I am using wicket 1.4-m3 Thanks, Vinayak - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Simple GET based stateless form
Hi, I am trying to create a simple GET based stateless form to implement search. My code is broken up into two parts 1. A SearchPanel component that renders the form containing the text field 2. A SearchPage that renders the search results. The search page also has the SearchPanel component embedded in it so it would show a text field for the user to search again. The SearchPage page is mounted using the mountBookmarkablePage() call, so the URL for the search page is great the first time someone does a search. However, if a search is performed a second time from the form on the SearchPage, the URL for the new serach page has a bunch of extra wicket specific attributes. How do I make the URL seen in the second search as clean as the first? I am using wicket 1.4-m3 Thanks, Vinayak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
