Re: wicket + jsessionid and 302 issues
Hi, I figured more detailed config info would be helpful. I want my production app to be accessible via https only. The connection is SSL to our Apache load balancer which is then http to our Tomcat7 instance. The Tomcat 7 connector is default: Just not sure how to config the web.xml or if my tomcat config needs changing. Thanks, Jason On 11/12/14, 1:40 PM, Jason Novotny wrote: Hi wicketeers, I was hoping to get rid of the jsessionid that appears in the browsewr bar when running my wicket app under Tomcat 7, and I added the following to web.xml: 30 COOKIE However, now in production we get all these 302 redirects which are causing an infinite recursion. What is the best way to handle this? I also found a wiki page https://cwiki.apache.org/confluence/display/WICKET/SEO+-+Search+Engine+Optimization but wasn't sure if this also applied to using Wicket 6. Thanks, Jason - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicket + jsessionid and 302 issues
Hi wicketeers, I was hoping to get rid of the jsessionid that appears in the browsewr bar when running my wicket app under Tomcat 7, and I added the following to web.xml: 30 COOKIE However, now in production we get all these 302 redirects which are causing an infinite recursion. What is the best way to handle this? I also found a wiki page https://cwiki.apache.org/confluence/display/WICKET/SEO+-+Search+Engine+Optimization but wasn't sure if this also applied to using Wicket 6. Thanks, Jason - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: form submit / parameters sometimes missing
Huh, good idea... I didn't think about that. Ok, but I dont always miss my last parameters. I also miss randomly in the middle. So, its not a case of truncation at the end. And its POST, not GET. Shouldnt be a problem... Patrick Am 12.11.2014 13:51, schrieb Sven Meier: > Url length exceeded? > > http://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers > > > Sven > > On 11/12/2014 11:32 AM, Patrick Davids wrote: >> ormdd_hf_0= >> &tabs:components:3:attributeComponent:form:pibiChoice=0 >> &tabs:components:3:attributeComponent:form:di17:statebottom=OK >> &tabs:components:3:attributeComponent:form:di16:statebottom=OK >> &tabs:components:3:attributeComponent:form:di15:statebottom=OK >> &tabs:components:3:attributeComponent:form:di14:statebottom=OK >> &tabs:components:3:attributeComponent:form:di13:statebottom=OK >> &tabs:components:3:attributeComponent:form:di12:statebottom=OK >> &tabs:components:3:attributeComponent:form:di11:statebottom=OK >> &tabs:components:3:attributeComponent:form:di21:statetop=OK >> &tabs:components:3:attributeComponent:form:di22:statetop=OK >> &tabs:components:3:attributeComponent:form:di23:statetop=OK >> &tabs:components:3:attributeComponent:form:di24:statetop=OK >> &tabs:components:3:attributeComponent:form:di25:statetop=OK >> &tabs:components:3:attributeComponent:form:di26:statetop=OK >> &tabs:components:3:attributeComponent:form:di27:statetop=OK >> &tabs:components:3:attributeComponent:form:di47:statebottom=OK >> &tabs:components:3:attributeComponent:form:di46:statebottom=OK >> &tabs:components:3:attributeComponent:form:di45:statebottom=OK >> &tabs:components:3:attributeComponent:form:di44:statebottom=OK >> &tabs:components:3:attributeComponent:form:di43:statebottom=OK >> &tabs:components:3:attributeComponent:form:di42:statebottom=OK >> &tabs:components:3:attributeComponent:form:di41:statebottom=OK >> &tabs:components:3:attributeComponent:form:di31:statetop=OK >> &tabs:components:3:attributeComponent:form:di32:statetop=OK >> &tabs:components:3:attributeComponent:form:di33:statetop=OK >> &tabs:components:3:attributeComponent:form:di34:statetop=OK >> >> formdd_hf_0=&tabs:components:4:attributeComponent:form:pibiChoice=0 >> &tabs:components:4:attributeComponent:form:di17:statebottom=OK >> &tabs:components:4:attributeComponent:form:di16:statebottom=OK >> &tabs:components:4:attributeComponent:form:di15:statebottom=OK >> &tabs:components:4:attributeComponent:form:di14:statebottom=OK >> &tabs:components:4:attributeComponent:form:di13:statebottom=OK >> &tabs:components:4:attributeComponent:form:di12:statebottom=OK >> &tabs:components:4:attributeComponent:form:di11:statebottom=OK >> &tabs:components:4:attributeComponent:form:di21:statetop=OK >> &tabs:components:4:attributeComponent:form:di22:statetop=OK >> &tabs:components:4:attributeComponent:form:di23:statetop=OK >> &tabs:components:4:attributeComponent:form:di24:statetop=OK >> &tabs:components:4:attributeComponent:form:di25:statetop=OK >> &tabs:components:4:attributeComponent:form:di26:statetop=OK >> &tabs:components:4:attributeComponent:form:di27:statetop=OK >> &tabs:components:4:attributeComponent:form:di47:statebottom=OK >> &tabs:components:4:attributeComponent:form:di46:statebottom=OK >> &tabs:components:4:attributeComponent:form:di45:statebottom=OK >> &tabs:components:4:attributeComponent:form:di44:statebottom=OK >> &tabs:components:4:attributeComponent:form:di43:statebottom=OK >> &tabs:components:4:attributeComponent:form:di42:statebottom=OK >> &tabs:components:4:attributeComponent:form:di41:statebottom=OK >> &tabs:components:4:attributeComponent:form:di31:statetop=OK >> &tabs:components:4:attributeComponent:form:di32:statetop=OK >> &tabs:components:4:attributeComponent:form:di33:statetop=OK >> &tabs:components:4:attributeComponent:form:di34:statetop=OK >> &tabs:components:4:attributeComponent:form:di35:statetop=OK >> &tabs:components:4:attributeComponent:form:di36:statetop=OK >> &tabs:components:4:attributeComponent:form:di37:statetop=OK > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Mit freundlichen Grüßen, Patrick Davids nuboLOGIC GmbH & Co. KG Kieler Str. 103-107 • 25474 Bönningstedt Tel.: +49 40 228539 732 Email: patrick.dav...@nubologic.com http://www.nubologic.com Handelsregister: HRA6819 Pi | Amtsgericht Pinneberg Geschäftsführung der Verwaltungsgesellschaft Daniel Fraga Zander HRB10145Pi | Amtsgericht Pinneberg - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Let AbstractMarkupParser be a bit more non-strict
Hi, AFAIK you cannot tell Wicket's default parser to run in non-strict mode. But you can register your own IMarkupFilter that will be used before the markup is passed to the parser. There you can fix the markup however you find appropriate. See org.apache.wicket.markup.parser.filter.OpenCloseTagExpander and other classes in the same package for inspiration. See org.apache.wicket.markup.parser.filter.HtmlProblemFinder javadoc for demo code how to setup it. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Nov 12, 2014 at 3:19 PM, Christian Smolka < christian.smo...@etecture.de> wrote: > Hi everybody! > > I have a problem with the AbstractMarkupParser. > > My application uses a HTML template to nest itself into a given web > site. This template is been pulled from a CMS. Sometimes, this CMS does > not return 100% compliant HTML5, although the doctype claims it. > Recently it returned an empty data attribute without the equal sign and > the quotes (so it was just instead of data="">). This made the Wicket application to crash, because it > wasn't able to parse the template. > > Is there any way to tell Wicket to "overlook" such minor HTML problems? > > Tanks in advace > Christian > >
Let AbstractMarkupParser be a bit more non-strict
Hi everybody! I have a problem with the AbstractMarkupParser. My application uses a HTML template to nest itself into a given web site. This template is been pulled from a CMS. Sometimes, this CMS does not return 100% compliant HTML5, although the doctype claims it. Recently it returned an empty data attribute without the equal sign and the quotes (so it was just instead of ). This made the Wicket application to crash, because it wasn't able to parse the template. Is there any way to tell Wicket to "overlook" such minor HTML problems? Tanks in advace Christian 0x1FB15F8A.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: form submit / parameters sometimes missing
Url length exceeded? http://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers Sven On 11/12/2014 11:32 AM, Patrick Davids wrote: ormdd_hf_0= &tabs:components:3:attributeComponent:form:pibiChoice=0 &tabs:components:3:attributeComponent:form:di17:statebottom=OK &tabs:components:3:attributeComponent:form:di16:statebottom=OK &tabs:components:3:attributeComponent:form:di15:statebottom=OK &tabs:components:3:attributeComponent:form:di14:statebottom=OK &tabs:components:3:attributeComponent:form:di13:statebottom=OK &tabs:components:3:attributeComponent:form:di12:statebottom=OK &tabs:components:3:attributeComponent:form:di11:statebottom=OK &tabs:components:3:attributeComponent:form:di21:statetop=OK &tabs:components:3:attributeComponent:form:di22:statetop=OK &tabs:components:3:attributeComponent:form:di23:statetop=OK &tabs:components:3:attributeComponent:form:di24:statetop=OK &tabs:components:3:attributeComponent:form:di25:statetop=OK &tabs:components:3:attributeComponent:form:di26:statetop=OK &tabs:components:3:attributeComponent:form:di27:statetop=OK &tabs:components:3:attributeComponent:form:di47:statebottom=OK &tabs:components:3:attributeComponent:form:di46:statebottom=OK &tabs:components:3:attributeComponent:form:di45:statebottom=OK &tabs:components:3:attributeComponent:form:di44:statebottom=OK &tabs:components:3:attributeComponent:form:di43:statebottom=OK &tabs:components:3:attributeComponent:form:di42:statebottom=OK &tabs:components:3:attributeComponent:form:di41:statebottom=OK &tabs:components:3:attributeComponent:form:di31:statetop=OK &tabs:components:3:attributeComponent:form:di32:statetop=OK &tabs:components:3:attributeComponent:form:di33:statetop=OK &tabs:components:3:attributeComponent:form:di34:statetop=OK formdd_hf_0=&tabs:components:4:attributeComponent:form:pibiChoice=0 &tabs:components:4:attributeComponent:form:di17:statebottom=OK &tabs:components:4:attributeComponent:form:di16:statebottom=OK &tabs:components:4:attributeComponent:form:di15:statebottom=OK &tabs:components:4:attributeComponent:form:di14:statebottom=OK &tabs:components:4:attributeComponent:form:di13:statebottom=OK &tabs:components:4:attributeComponent:form:di12:statebottom=OK &tabs:components:4:attributeComponent:form:di11:statebottom=OK &tabs:components:4:attributeComponent:form:di21:statetop=OK &tabs:components:4:attributeComponent:form:di22:statetop=OK &tabs:components:4:attributeComponent:form:di23:statetop=OK &tabs:components:4:attributeComponent:form:di24:statetop=OK &tabs:components:4:attributeComponent:form:di25:statetop=OK &tabs:components:4:attributeComponent:form:di26:statetop=OK &tabs:components:4:attributeComponent:form:di27:statetop=OK &tabs:components:4:attributeComponent:form:di47:statebottom=OK &tabs:components:4:attributeComponent:form:di46:statebottom=OK &tabs:components:4:attributeComponent:form:di45:statebottom=OK &tabs:components:4:attributeComponent:form:di44:statebottom=OK &tabs:components:4:attributeComponent:form:di43:statebottom=OK &tabs:components:4:attributeComponent:form:di42:statebottom=OK &tabs:components:4:attributeComponent:form:di41:statebottom=OK &tabs:components:4:attributeComponent:form:di31:statetop=OK &tabs:components:4:attributeComponent:form:di32:statetop=OK &tabs:components:4:attributeComponent:form:di33:statetop=OK &tabs:components:4:attributeComponent:form:di34:statetop=OK &tabs:components:4:attributeComponent:form:di35:statetop=OK &tabs:components:4:attributeComponent:form:di36:statetop=OK &tabs:components:4:attributeComponent:form:di37:statetop=OK - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Please give some guidance with ExternalLink and Events
Hi, I'm trying to close a modal after an external link action, (the external link resides in the modal) the code: If I change the event to 'onclick', the modal closes before link's activation. :( thanks in advance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Please-give-some-guidance-with-ExternalLink-and-Events-tp4668378.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: Wicke website makeover time?
On Wed, Nov 12, 2014 at 11:23 AM, Chris Colman wrote: > Some of those look very nice indeed. How were they created? Just Keynote (a presentation tool for the Mac). > It sounds like people have been toying with this for a long time. Yup. > Perhaps it never happened because we wanted to go from the current site > to mega awesome in one single step - which was always too much effort. Not really, but if you change the styling you want to fix the copywriting as well. Some of the copy on our site is as old as Wicket. > I think a multi phase approach might have more chance of success - as I > said in my immediate previous post if we could live with jekyll source > for phase one (even though it may not be ideal) then we can keep most of > the current content source 'as is' and simply choose a decent modern > Bootstrap CSS template to re-render it in to deliver the best 'bang for > buck' possible at this early stage. Bootstrap would be too standard and anonymous and would ultimately be a ball and chain. A little .less and responsiveness can easily be achieved without going bootstrap. > Or does Jekyll have a fairly fixed translator that provides little > customizability? Jekyll is fully customizable. It's just a translator from markdown to HTML with templates and includes. Martijn - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Wicke website makeover time?
This looks like it could be useful: http://jekyllbootstrap.com/ They have autowired all the necessary Liquid template stuff to make generation of a bootstrap styled site from jekyll source a breeze. Maybe it's worth having a play with it using the current wicket site's jekyll source? -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Wednesday, 12 November 2014 9:11 PM To: users@wicket.apache.org Subject: Re: Wicke website makeover time? On Wed, Nov 12, 2014 at 11:58 AM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > Several attempts at a refresh have been done but they all strand in two > things: > > - time to actually do something with a design that is received > enthusiastically > - copywriting the website, especially the front page > > For example I tend to doodle in keynote for ideas of a new web site > look and my latest thing is actually going back to our roots (at > http://wicket.sourceforge.net/1.2): > > http://imgur.com/D74s1dj > http://imgur.com/UFxgSRI,jHawnst#0 > http://imgur.com/UFxgSRI,jHawnst#1 > > I think it looks awesome but lack currently the time to actually do > something more with it other than have it in keynote. > > There are some hurdles to consider: > - website technology (currently jekyll, but asciidoctor might be a > better future candidate, especially for the reference guide) > > - svn pub sub, I guess there's git pub sub but am not sure if/how that > works > There was a discussion at infra@ the other day about this: David Nalley (Infra team leader): In a word, no. Technically, I am sure we could build it, but we won't. We use svnpubsub to keep the ~250 websites we have to manage a relatively sane process. Moving some sites to git makes that far more complicated. --David On Mon, Nov 10, 2014 at 2:07 AM, Tomer Shiran wrote: > I have a follow-up question. Is it possible to use git to publish the > website as opposed to svn? We use git for the project's source code, so that > would be convenient. But this should not stop us. It is easy to create our own shell script that copies the Asciidoctor output to another folder (the site svn working directory) and commit it. We can add it to the release.sh script. - how to publish the site (currently generate, svn commit, but if > guide is part of our build (to enable live, compiling examples) how > does that integrate in the site workflow... > > Martijn > > > On Wed, Nov 12, 2014 at 9:21 AM, Martin Grigorov > wrote: > > Hi, > > > > > > On Wed, Nov 12, 2014 at 9:45 AM, Chris Colman < > chr...@stepaheadsoftware.com> > > wrote: > > > >> Hi fellow wicketeers! > >> > >> We all know that Wicket has to be the most awesome and productive Java > >> UI framework around but I am worried when I point new clients to the > >> Wicket website because it's look and feel is possibly a little dated or > >> '2007ish style'. > >> > >> I feel like the look and feel of the Wicket website doesn't do justice > >> to the full awesomeness that we all know wicket has. > >> > >> We all know that, using the wicket Java UI framework it's possible to > >> create websites with *any* look and feel but unfortunately many clients > >> don't have this same technical awareness and see the website for Wicket, > >> a framework for building web applications in Java, and assume that the > >> Wicket website itself is an example of the type of webapp/website you'll > >> end up with if you build it with Wicket - which we all know is not the > >> case: we're building awesome AJAX enabled, modern, sexy Bootstrap > >> templated webapps in Wicket. > >> > >> A few years ago someone had produced a prototype of a refurbished Wicket > >> website that looked really quite nice but it never was deployed to the > >> live server for some reason. > > > > > > I guess you mean https://github.com/dashorst/wicket-site. > > > > > >> > >> These days I think most developers know that it's fairly easy to make a > >> great, modern looking website using one of the many Bootstrap > >> customizations (eg., Bootswatch). > >> > >> First question: > >> > >> Does anyone else think a wicket website makeover is overdue (or are most > >> people happy with the current look and feel)? > >> > > > > I do! > > But I am not capable of doing it myself because I am not an artist. > > I don't have this kind of imagination to create something pretty. > > Functional - yes, but not pretty :( > > > > Recently I've had a conversation with a client about this topic. (They > use > > Wicket Bootstrap) > > > > Me (explaining why Wicket Bootstrap is not a module of Apache Wicket > > distro): > > > > Today Bootstrap is the hype. Tomorrow something else will be > > This is the main reason why WB hasn't been merged as a sub project of > > Apache Wicket itself. > > > > > > The client: > > > > Agreed, and I think the strategy of Wicket is fine for experienced web > > developers. > > > > However, for every experienced developer, I assume there are 10 novices > > trying out
form submit / parameters sometimes missing
Hi all, I have a strange behavior when submitting a form via Ajax. Sometimes some form fields are just missing. As I can see Wicket serializes the form and posts data to the server. Using FireBug I had a look at the posted data. The data looks like this (see below). The second post request is ok, the first one misses some parameters. In this exmaple its di35, di36, di37. I am not able to reproduce this savely for e.g. a fix set of parameters. It's just random. Can anyone help? I am out of ideas... Thanx a lot and best regards Patrick formdd_hf_0= &tabs:components:3:attributeComponent:form:pibiChoice=0 &tabs:components:3:attributeComponent:form:di17:statebottom=OK &tabs:components:3:attributeComponent:form:di16:statebottom=OK &tabs:components:3:attributeComponent:form:di15:statebottom=OK &tabs:components:3:attributeComponent:form:di14:statebottom=OK &tabs:components:3:attributeComponent:form:di13:statebottom=OK &tabs:components:3:attributeComponent:form:di12:statebottom=OK &tabs:components:3:attributeComponent:form:di11:statebottom=OK &tabs:components:3:attributeComponent:form:di21:statetop=OK &tabs:components:3:attributeComponent:form:di22:statetop=OK &tabs:components:3:attributeComponent:form:di23:statetop=OK &tabs:components:3:attributeComponent:form:di24:statetop=OK &tabs:components:3:attributeComponent:form:di25:statetop=OK &tabs:components:3:attributeComponent:form:di26:statetop=OK &tabs:components:3:attributeComponent:form:di27:statetop=OK &tabs:components:3:attributeComponent:form:di47:statebottom=OK &tabs:components:3:attributeComponent:form:di46:statebottom=OK &tabs:components:3:attributeComponent:form:di45:statebottom=OK &tabs:components:3:attributeComponent:form:di44:statebottom=OK &tabs:components:3:attributeComponent:form:di43:statebottom=OK &tabs:components:3:attributeComponent:form:di42:statebottom=OK &tabs:components:3:attributeComponent:form:di41:statebottom=OK &tabs:components:3:attributeComponent:form:di31:statetop=OK &tabs:components:3:attributeComponent:form:di32:statetop=OK &tabs:components:3:attributeComponent:form:di33:statetop=OK &tabs:components:3:attributeComponent:form:di34:statetop=OK formdd_hf_0=&tabs:components:4:attributeComponent:form:pibiChoice=0 &tabs:components:4:attributeComponent:form:di17:statebottom=OK &tabs:components:4:attributeComponent:form:di16:statebottom=OK &tabs:components:4:attributeComponent:form:di15:statebottom=OK &tabs:components:4:attributeComponent:form:di14:statebottom=OK &tabs:components:4:attributeComponent:form:di13:statebottom=OK &tabs:components:4:attributeComponent:form:di12:statebottom=OK &tabs:components:4:attributeComponent:form:di11:statebottom=OK &tabs:components:4:attributeComponent:form:di21:statetop=OK &tabs:components:4:attributeComponent:form:di22:statetop=OK &tabs:components:4:attributeComponent:form:di23:statetop=OK &tabs:components:4:attributeComponent:form:di24:statetop=OK &tabs:components:4:attributeComponent:form:di25:statetop=OK &tabs:components:4:attributeComponent:form:di26:statetop=OK &tabs:components:4:attributeComponent:form:di27:statetop=OK &tabs:components:4:attributeComponent:form:di47:statebottom=OK &tabs:components:4:attributeComponent:form:di46:statebottom=OK &tabs:components:4:attributeComponent:form:di45:statebottom=OK &tabs:components:4:attributeComponent:form:di44:statebottom=OK &tabs:components:4:attributeComponent:form:di43:statebottom=OK &tabs:components:4:attributeComponent:form:di42:statebottom=OK &tabs:components:4:attributeComponent:form:di41:statebottom=OK &tabs:components:4:attributeComponent:form:di31:statetop=OK &tabs:components:4:attributeComponent:form:di32:statetop=OK &tabs:components:4:attributeComponent:form:di33:statetop=OK &tabs:components:4:attributeComponent:form:di34:statetop=OK &tabs:components:4:attributeComponent:form:di35:statetop=OK &tabs:components:4:attributeComponent:form:di36:statetop=OK &tabs:components:4:attributeComponent:form:di37:statetop=OK - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Wicke website makeover time?
Some of those look very nice indeed. How were they created? It sounds like people have been toying with this for a long time. Perhaps it never happened because we wanted to go from the current site to mega awesome in one single step - which was always too much effort. I think a multi phase approach might have more chance of success - as I said in my immediate previous post if we could live with jekyll source for phase one (even though it may not be ideal) then we can keep most of the current content source 'as is' and simply choose a decent modern Bootstrap CSS template to re-render it in to deliver the best 'bang for buck' possible at this early stage. Or does Jekyll have a fairly fixed translator that provides little customizability? -Original Message- From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com] Sent: Wednesday, 12 November 2014 8:58 PM To: users@wicket.apache.org Subject: Re: Wicke website makeover time? Several attempts at a refresh have been done but they all strand in two things: - time to actually do something with a design that is received enthusiastically - copywriting the website, especially the front page For example I tend to doodle in keynote for ideas of a new web site look and my latest thing is actually going back to our roots (at http://wicket.sourceforge.net/1.2): http://imgur.com/D74s1dj http://imgur.com/UFxgSRI,jHawnst#0 http://imgur.com/UFxgSRI,jHawnst#1 I think it looks awesome but lack currently the time to actually do something more with it other than have it in keynote. There are some hurdles to consider: - website technology (currently jekyll, but asciidoctor might be a better future candidate, especially for the reference guide) - svn pub sub, I guess there's git pub sub but am not sure if/how that works - how to publish the site (currently generate, svn commit, but if guide is part of our build (to enable live, compiling examples) how does that integrate in the site workflow... Martijn On Wed, Nov 12, 2014 at 9:21 AM, Martin Grigorov wrote: > Hi, > > > On Wed, Nov 12, 2014 at 9:45 AM, Chris Colman > wrote: > >> Hi fellow wicketeers! >> >> We all know that Wicket has to be the most awesome and productive Java >> UI framework around but I am worried when I point new clients to the >> Wicket website because it's look and feel is possibly a little dated or >> '2007ish style'. >> >> I feel like the look and feel of the Wicket website doesn't do justice >> to the full awesomeness that we all know wicket has. >> >> We all know that, using the wicket Java UI framework it's possible to >> create websites with *any* look and feel but unfortunately many clients >> don't have this same technical awareness and see the website for Wicket, >> a framework for building web applications in Java, and assume that the >> Wicket website itself is an example of the type of webapp/website you'll >> end up with if you build it with Wicket - which we all know is not the >> case: we're building awesome AJAX enabled, modern, sexy Bootstrap >> templated webapps in Wicket. >> >> A few years ago someone had produced a prototype of a refurbished Wicket >> website that looked really quite nice but it never was deployed to the >> live server for some reason. > > > I guess you mean https://github.com/dashorst/wicket-site. > > >> >> These days I think most developers know that it's fairly easy to make a >> great, modern looking website using one of the many Bootstrap >> customizations (eg., Bootswatch). >> >> First question: >> >> Does anyone else think a wicket website makeover is overdue (or are most >> people happy with the current look and feel)? >> > > I do! > But I am not capable of doing it myself because I am not an artist. > I don't have this kind of imagination to create something pretty. > Functional - yes, but not pretty :( > > Recently I've had a conversation with a client about this topic. (They use > Wicket Bootstrap) > > Me (explaining why Wicket Bootstrap is not a module of Apache Wicket > distro): > > Today Bootstrap is the hype. Tomorrow something else will be > This is the main reason why WB hasn't been merged as a sub project of > Apache Wicket itself. > > > The client: > > Agreed, and I think the strategy of Wicket is fine for experienced web > developers. > > However, for every experienced developer, I assume there are 10 novices > trying out Wicket and if you don't steer novice users towards a HTML/CSS > framework to use with Wicket to create great looking apps, most of them > will be disappointed and wander off elsewhere. > > > More or less he said the same as you ! But I think he meant Wicket Examples > instead of http://wicket.apache.org/ > > >> If the answer is yes then please continue reading: >> >> Any chance some people are interested in offering time to perform a >> Wicket website makeover? >> > > I'll be glad to help with infrastructure, testing, fixing issues, etc. ! > > >> >> Some questions for the site maintainers - >> >> >> Are
RE: Wicke website makeover time?
Wicket examples are in the same styling as the website so yes, the same logic applies to them also - actually probably even more so as they really are 'examples of what a wicket app might look like' - which is a bit sad when, with a bit of Bootstrap and nice fonts, they can look so much more awesome. I'll check out jekyllrb. Ideally if we can change the generator and leave the jekyll source largely untouched for phase 1 then we avoid the effort of porting any content over to a new input format. Maybe a phase 2 could look at switching to a different input format if jekyll has issues/limitations. Regards, Chris -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Wednesday, 12 November 2014 7:21 PM To: users@wicket.apache.org Subject: Re: Wicke website makeover time? Hi, On Wed, Nov 12, 2014 at 9:45 AM, Chris Colman wrote: > Hi fellow wicketeers! > > We all know that Wicket has to be the most awesome and productive Java > UI framework around but I am worried when I point new clients to the > Wicket website because it's look and feel is possibly a little dated or > '2007ish style'. > > I feel like the look and feel of the Wicket website doesn't do justice > to the full awesomeness that we all know wicket has. > > We all know that, using the wicket Java UI framework it's possible to > create websites with *any* look and feel but unfortunately many clients > don't have this same technical awareness and see the website for Wicket, > a framework for building web applications in Java, and assume that the > Wicket website itself is an example of the type of webapp/website you'll > end up with if you build it with Wicket - which we all know is not the > case: we're building awesome AJAX enabled, modern, sexy Bootstrap > templated webapps in Wicket. > > A few years ago someone had produced a prototype of a refurbished Wicket > website that looked really quite nice but it never was deployed to the > live server for some reason. I guess you mean https://github.com/dashorst/wicket-site. > > These days I think most developers know that it's fairly easy to make a > great, modern looking website using one of the many Bootstrap > customizations (eg., Bootswatch). > > First question: > > Does anyone else think a wicket website makeover is overdue (or are most > people happy with the current look and feel)? > I do! But I am not capable of doing it myself because I am not an artist. I don't have this kind of imagination to create something pretty. Functional - yes, but not pretty :( Recently I've had a conversation with a client about this topic. (They use Wicket Bootstrap) Me (explaining why Wicket Bootstrap is not a module of Apache Wicket distro): Today Bootstrap is the hype. Tomorrow something else will be This is the main reason why WB hasn't been merged as a sub project of Apache Wicket itself. The client: Agreed, and I think the strategy of Wicket is fine for experienced web developers. However, for every experienced developer, I assume there are 10 novices trying out Wicket and if you don't steer novice users towards a HTML/CSS framework to use with Wicket to create great looking apps, most of them will be disappointed and wander off elsewhere. More or less he said the same as you ! But I think he meant Wicket Examples instead of http://wicket.apache.org/ > If the answer is yes then please continue reading: > > Any chance some people are interested in offering time to perform a > Wicket website makeover? > I'll be glad to help with infrastructure, testing, fixing issues, etc. ! > > Some questions for the site maintainers - > > > Are the current web pages: > 1. Generated from any tool via XLST or anything? > The code is hosted at https://svn.apache.org/repos/asf/wicket/common/site/trunk. We use http://jekyllrb.com/ to generate static HTML files. It is simple and fast. > 2. Served from a content management system? > No. > 3. Just static pages edited directly in HTML? > Yes. 4. Served as a Wicket app? (would be awesome!) > No. Apache Infrastructure team doesn't allow usage of dynamically generated stuff because this leads of the higher maintenance cost. > > I guess the answer to these determines the quickest way possible to a > refurbished website if Wicketeers agree that is appropriate. > > Could we hook together a simple system that actually uses a very simple > Wicket app itself to host the pages? Eg., provide page content in some > wiki style text format and have a simple Wicket page class that > interprets this and outputs formatted content? > No. See above. > > Aside: We have actually built a content management system for > editing/hosting websites using Wicket but it's proprietary and I don't > think Apache would approve of an Apache site being served by a > proprietary content management system so that's probably not an option. > We don't mind hosting it if they didn't mind but I'm thinking that's not > going to be ap
Re: Could not clear select2Choice component model value.
It is in my TODO list...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Nov 11, 2014 at 6:29 PM, Maxim Solodovnik
wrote:
> Hello Martin,
>
> I know you are busy man ..., but, were you able to take a look at this
> issue? :)
>
> On 22 October 2014 11:23, Maxim Solodovnik wrote:
>
> > It seems like script generated in renderInitializationScript should be
> > added to AjaxRequestTarget on every Ajax update ...
> >
> > On 21 October 2014 17:09, Maxim Solodovnik wrote:
> >
> >> Here it is:
> >> https://github.com/solomax/WicketSelect2Clear
> >>
> >> somehow in this example nothing works as expected :(
> >> I tried 2 different approaches, correct new value arrives to the page
> >> (according to "wicket debug") but select2 is not being updated :(
> >>
> >> On 21 October 2014 13:23, Martin Grigorov wrote:
> >>
> >>> Hi Maxim,
> >>>
> >>> Please prepare a quickstart at GitHub and I'll take a look.
> >>>
> >>> Martin Grigorov
> >>> Wicket Training and Consulting
> >>> https://twitter.com/mtgrigorov
> >>>
> >>> On Fri, Oct 17, 2014 at 5:42 PM, Maxim Solodovnik <
> solomax...@gmail.com>
> >>> wrote:
> >>>
> >>> > Martin,
> >>> >
> >>> > I have forked select2, unfortunately I'm still not sure how to fix
> the
> >>> > issue :(
> >>> > "Clean link" is added to the form and select data is being restored
> >>> from
> >>> > requestParameters :(
> >>> >
> >>> > On 13 October 2014 19:06, Martin Grigorov
> >>> wrote:
> >>> >
> >>> > > Maxim,
> >>> > >
> >>> > > Feel free to fork it! I.e. move it to WicketStuff.
> >>> > >
> >>> > > Martin Grigorov
> >>> > > Wicket Training and Consulting
> >>> > > https://twitter.com/mtgrigorov
> >>> > >
> >>> > > On Thu, Oct 9, 2014 at 8:53 PM, Maxim Solodovnik <
> >>> solomax...@gmail.com>
> >>> > > wrote:
> >>> > >
> >>> > > > Additionally select2 seems to need to be forked to wicketstuff to
> >>> be
> >>> > > fixed,
> >>> > > > should I do this?
> >>> > > >
> >>> > > > On 10 October 2014 00:49, Maxim Solodovnik >
> >>> > wrote:
> >>> > > >
> >>> > > > > @Paul, @Martin
> >>> > > > >
> >>> > > > > Select2Choice sets back its value
> >>> > > > > to getWebRequest().getRequestParameters().getParameterNames()
> >>> > > > > in renderInitializationScript method [1]
> >>> > > > > It seems like JS code like: $("#country1").select2("data",
> >>> null); can
> >>> > > be
> >>> > > > > executed on clear input, but this seems to be workaround
> >>> > > > >
> >>> > > > > I'm not sure why [1] method is used to get value, maybe you can
> >>> > suggest
> >>> > > > > correct way of fixing this?
> >>> > > > >
> >>> > > > >
> >>> > > > > [1]
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> https://github.com/ivaynberg/wicket-select2/blob/master/wicket-select2/src/main/java/com/vaynberg/wicket/select2/Select2Choice.java#L62
> >>> > > > >
> >>> > > > > On 9 October 2014 16:39, MadasamySankarapandian <
> >>> > > madas...@mcruncher.com>
> >>> > > > > wrote:
> >>> > > > >
> >>> > > > >> Thanks Maxim Solodovnik.
> >>> > > > >>
> >>> > > > >> On Thu, Oct 9, 2014 at 12:33 PM, Maxim Solodovnik <
> >>> > > solomax...@gmail.com
> >>> > > > >
> >>> > > > >> wrote:
> >>> > > > >>
> >>> > > > >> > I also noticed this issue in our project,
> >>> > > > >> > Will try to take a look at it
> >>> > > > >> >
> >>> > > > >> > On 9 October 2014 07:33, MadasamySankarapandian <
> >>> > > > madas...@mcruncher.com
> >>> > > > >> >
> >>> > > > >> > wrote:
> >>> > > > >> >
> >>> > > > >> > > Thankyou very much for yours reply.
> >>> > > > >> > >
> >>> > > > >> > > I call formComponent.clearInput() in my ClearFormVisitor
> >>> class.
> >>> > > But
> >>> > > > It
> >>> > > > >> > does
> >>> > > > >> > > not work.
> >>> > > > >> > > I have created issue-96
> >>> > > > >> > >
> in
> >>> > > > >> > wicket-select2
> >>> > > > >> > > project.
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > > On Wed, Oct 8, 2014 at 12:13 AM, Maxim Solodovnik <
> >>> > > > >> solomax...@gmail.com>
> >>> > > > >> > > wrote:
> >>> > > > >> > >
> >>> > > > >> > > > Done, thanks for pointing this out
> >>> > > > >> > > >
> >>> > > > >> > > > On 7 October 2014 23:08, Paul Bors
> wrote:
> >>> > > > >> > > >
> >>> > > > >> > > > > Can you update this issue then?
> >>> > > > >> > > > >
> >>> > > > >> > > > > https://github.com/ivaynberg/wicket-select2/issues/93
> >>> > > > >> > > > >
> >>> > > > >> > > > > On Tue, Oct 7, 2014 at 12:00 PM, Maxim Solodovnik <
> >>> > > > >> > > solomax...@gmail.com>
> >>> > > > >> > > > > wrote:
> >>> > > > >> > > > >
> >>> > > > >> > > > > > we recently moved this component to wicketstuff:
> >>> > > > >> > > > > >
> >>> > > > >> > > > > >
> >>> > > > >> > > > >
> >>> > > > >> > > >
> >>> > > > >> > >
> >>> > > > >> >
> >>> > > > >>
> >>> > > >
> >>> > >
> >>> >
> >>>
> https://github.com/wicketstuff/core/tree/master/jdk-1.7-parent/select2-parent
> >>> >
Re: Wicke website makeover time?
On Wed, Nov 12, 2014 at 11:58 AM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > Several attempts at a refresh have been done but they all strand in two > things: > > - time to actually do something with a design that is received > enthusiastically > - copywriting the website, especially the front page > > For example I tend to doodle in keynote for ideas of a new web site > look and my latest thing is actually going back to our roots (at > http://wicket.sourceforge.net/1.2): > > http://imgur.com/D74s1dj > http://imgur.com/UFxgSRI,jHawnst#0 > http://imgur.com/UFxgSRI,jHawnst#1 > > I think it looks awesome but lack currently the time to actually do > something more with it other than have it in keynote. > > There are some hurdles to consider: > - website technology (currently jekyll, but asciidoctor might be a > better future candidate, especially for the reference guide) > > - svn pub sub, I guess there's git pub sub but am not sure if/how that > works > There was a discussion at infra@ the other day about this: David Nalley (Infra team leader): In a word, no. Technically, I am sure we could build it, but we won't. We use svnpubsub to keep the ~250 websites we have to manage a relatively sane process. Moving some sites to git makes that far more complicated. --David On Mon, Nov 10, 2014 at 2:07 AM, Tomer Shiran wrote: > I have a follow-up question. Is it possible to use git to publish the > website as opposed to svn? We use git for the project's source code, so that > would be convenient. But this should not stop us. It is easy to create our own shell script that copies the Asciidoctor output to another folder (the site svn working directory) and commit it. We can add it to the release.sh script. - how to publish the site (currently generate, svn commit, but if > guide is part of our build (to enable live, compiling examples) how > does that integrate in the site workflow... > > Martijn > > > On Wed, Nov 12, 2014 at 9:21 AM, Martin Grigorov > wrote: > > Hi, > > > > > > On Wed, Nov 12, 2014 at 9:45 AM, Chris Colman < > chr...@stepaheadsoftware.com> > > wrote: > > > >> Hi fellow wicketeers! > >> > >> We all know that Wicket has to be the most awesome and productive Java > >> UI framework around but I am worried when I point new clients to the > >> Wicket website because it's look and feel is possibly a little dated or > >> '2007ish style'. > >> > >> I feel like the look and feel of the Wicket website doesn't do justice > >> to the full awesomeness that we all know wicket has. > >> > >> We all know that, using the wicket Java UI framework it's possible to > >> create websites with *any* look and feel but unfortunately many clients > >> don't have this same technical awareness and see the website for Wicket, > >> a framework for building web applications in Java, and assume that the > >> Wicket website itself is an example of the type of webapp/website you'll > >> end up with if you build it with Wicket - which we all know is not the > >> case: we're building awesome AJAX enabled, modern, sexy Bootstrap > >> templated webapps in Wicket. > >> > >> A few years ago someone had produced a prototype of a refurbished Wicket > >> website that looked really quite nice but it never was deployed to the > >> live server for some reason. > > > > > > I guess you mean https://github.com/dashorst/wicket-site. > > > > > >> > >> These days I think most developers know that it's fairly easy to make a > >> great, modern looking website using one of the many Bootstrap > >> customizations (eg., Bootswatch). > >> > >> First question: > >> > >> Does anyone else think a wicket website makeover is overdue (or are most > >> people happy with the current look and feel)? > >> > > > > I do! > > But I am not capable of doing it myself because I am not an artist. > > I don't have this kind of imagination to create something pretty. > > Functional - yes, but not pretty :( > > > > Recently I've had a conversation with a client about this topic. (They > use > > Wicket Bootstrap) > > > > Me (explaining why Wicket Bootstrap is not a module of Apache Wicket > > distro): > > > > Today Bootstrap is the hype. Tomorrow something else will be > > This is the main reason why WB hasn't been merged as a sub project of > > Apache Wicket itself. > > > > > > The client: > > > > Agreed, and I think the strategy of Wicket is fine for experienced web > > developers. > > > > However, for every experienced developer, I assume there are 10 novices > > trying out Wicket and if you don’t steer novice users towards a HTML/CSS > > framework to use with Wicket to create great looking apps, most of them > > will be disappointed and wander off elsewhere. > > > > > > More or less he said the same as you ! But I think he meant Wicket > Examples > > instead of http://wicket.apache.org/ > > > > > >> If the answer is yes then please continue reading: > >> > >> Any chance some people are interested in offering time to perform a > >> Wicket website
Re: Wicke website makeover time?
Several attempts at a refresh have been done but they all strand in two things: - time to actually do something with a design that is received enthusiastically - copywriting the website, especially the front page For example I tend to doodle in keynote for ideas of a new web site look and my latest thing is actually going back to our roots (at http://wicket.sourceforge.net/1.2): http://imgur.com/D74s1dj http://imgur.com/UFxgSRI,jHawnst#0 http://imgur.com/UFxgSRI,jHawnst#1 I think it looks awesome but lack currently the time to actually do something more with it other than have it in keynote. There are some hurdles to consider: - website technology (currently jekyll, but asciidoctor might be a better future candidate, especially for the reference guide) - svn pub sub, I guess there's git pub sub but am not sure if/how that works - how to publish the site (currently generate, svn commit, but if guide is part of our build (to enable live, compiling examples) how does that integrate in the site workflow... Martijn On Wed, Nov 12, 2014 at 9:21 AM, Martin Grigorov wrote: > Hi, > > > On Wed, Nov 12, 2014 at 9:45 AM, Chris Colman > wrote: > >> Hi fellow wicketeers! >> >> We all know that Wicket has to be the most awesome and productive Java >> UI framework around but I am worried when I point new clients to the >> Wicket website because it's look and feel is possibly a little dated or >> '2007ish style'. >> >> I feel like the look and feel of the Wicket website doesn't do justice >> to the full awesomeness that we all know wicket has. >> >> We all know that, using the wicket Java UI framework it's possible to >> create websites with *any* look and feel but unfortunately many clients >> don't have this same technical awareness and see the website for Wicket, >> a framework for building web applications in Java, and assume that the >> Wicket website itself is an example of the type of webapp/website you'll >> end up with if you build it with Wicket - which we all know is not the >> case: we're building awesome AJAX enabled, modern, sexy Bootstrap >> templated webapps in Wicket. >> >> A few years ago someone had produced a prototype of a refurbished Wicket >> website that looked really quite nice but it never was deployed to the >> live server for some reason. > > > I guess you mean https://github.com/dashorst/wicket-site. > > >> >> These days I think most developers know that it's fairly easy to make a >> great, modern looking website using one of the many Bootstrap >> customizations (eg., Bootswatch). >> >> First question: >> >> Does anyone else think a wicket website makeover is overdue (or are most >> people happy with the current look and feel)? >> > > I do! > But I am not capable of doing it myself because I am not an artist. > I don't have this kind of imagination to create something pretty. > Functional - yes, but not pretty :( > > Recently I've had a conversation with a client about this topic. (They use > Wicket Bootstrap) > > Me (explaining why Wicket Bootstrap is not a module of Apache Wicket > distro): > > Today Bootstrap is the hype. Tomorrow something else will be > This is the main reason why WB hasn't been merged as a sub project of > Apache Wicket itself. > > > The client: > > Agreed, and I think the strategy of Wicket is fine for experienced web > developers. > > However, for every experienced developer, I assume there are 10 novices > trying out Wicket and if you don’t steer novice users towards a HTML/CSS > framework to use with Wicket to create great looking apps, most of them > will be disappointed and wander off elsewhere. > > > More or less he said the same as you ! But I think he meant Wicket Examples > instead of http://wicket.apache.org/ > > >> If the answer is yes then please continue reading: >> >> Any chance some people are interested in offering time to perform a >> Wicket website makeover? >> > > I'll be glad to help with infrastructure, testing, fixing issues, etc. ! > > >> >> Some questions for the site maintainers - >> >> >> Are the current web pages: >> 1. Generated from any tool via XLST or anything? >> > > The code is hosted at > https://svn.apache.org/repos/asf/wicket/common/site/trunk. > We use http://jekyllrb.com/ to generate static HTML files. It is simple and > fast. > > >> 2. Served from a content management system? >> > > No. > > >> 3. Just static pages edited directly in HTML? >> > > Yes. > > 4. Served as a Wicket app? (would be awesome!) >> > > No. Apache Infrastructure team doesn't allow usage of dynamically generated > stuff because this leads of the higher maintenance cost. > > >> >> I guess the answer to these determines the quickest way possible to a >> refurbished website if Wicketeers agree that is appropriate. >> >> Could we hook together a simple system that actually uses a very simple >> Wicket app itself to host the pages? Eg., provide page content in some >> wiki style text format and have a simple Wicket page class th
Re: Wicke website makeover time?
Hi, On Wed, Nov 12, 2014 at 9:45 AM, Chris Colman wrote: > Hi fellow wicketeers! > > We all know that Wicket has to be the most awesome and productive Java > UI framework around but I am worried when I point new clients to the > Wicket website because it's look and feel is possibly a little dated or > '2007ish style'. > > I feel like the look and feel of the Wicket website doesn't do justice > to the full awesomeness that we all know wicket has. > > We all know that, using the wicket Java UI framework it's possible to > create websites with *any* look and feel but unfortunately many clients > don't have this same technical awareness and see the website for Wicket, > a framework for building web applications in Java, and assume that the > Wicket website itself is an example of the type of webapp/website you'll > end up with if you build it with Wicket - which we all know is not the > case: we're building awesome AJAX enabled, modern, sexy Bootstrap > templated webapps in Wicket. > > A few years ago someone had produced a prototype of a refurbished Wicket > website that looked really quite nice but it never was deployed to the > live server for some reason. I guess you mean https://github.com/dashorst/wicket-site. > > These days I think most developers know that it's fairly easy to make a > great, modern looking website using one of the many Bootstrap > customizations (eg., Bootswatch). > > First question: > > Does anyone else think a wicket website makeover is overdue (or are most > people happy with the current look and feel)? > I do! But I am not capable of doing it myself because I am not an artist. I don't have this kind of imagination to create something pretty. Functional - yes, but not pretty :( Recently I've had a conversation with a client about this topic. (They use Wicket Bootstrap) Me (explaining why Wicket Bootstrap is not a module of Apache Wicket distro): Today Bootstrap is the hype. Tomorrow something else will be This is the main reason why WB hasn't been merged as a sub project of Apache Wicket itself. The client: Agreed, and I think the strategy of Wicket is fine for experienced web developers. However, for every experienced developer, I assume there are 10 novices trying out Wicket and if you don’t steer novice users towards a HTML/CSS framework to use with Wicket to create great looking apps, most of them will be disappointed and wander off elsewhere. More or less he said the same as you ! But I think he meant Wicket Examples instead of http://wicket.apache.org/ > If the answer is yes then please continue reading: > > Any chance some people are interested in offering time to perform a > Wicket website makeover? > I'll be glad to help with infrastructure, testing, fixing issues, etc. ! > > Some questions for the site maintainers - > > > Are the current web pages: > 1. Generated from any tool via XLST or anything? > The code is hosted at https://svn.apache.org/repos/asf/wicket/common/site/trunk. We use http://jekyllrb.com/ to generate static HTML files. It is simple and fast. > 2. Served from a content management system? > No. > 3. Just static pages edited directly in HTML? > Yes. 4. Served as a Wicket app? (would be awesome!) > No. Apache Infrastructure team doesn't allow usage of dynamically generated stuff because this leads of the higher maintenance cost. > > I guess the answer to these determines the quickest way possible to a > refurbished website if Wicketeers agree that is appropriate. > > Could we hook together a simple system that actually uses a very simple > Wicket app itself to host the pages? Eg., provide page content in some > wiki style text format and have a simple Wicket page class that > interprets this and outputs formatted content? > No. See above. > > Aside: We have actually built a content management system for > editing/hosting websites using Wicket but it's proprietary and I don't > think Apache would approve of an Apache site being served by a > proprietary content management system so that's probably not an option. > We don't mind hosting it if they didn't mind but I'm thinking that's not > going to be approved. > > > Regards, > Chris >
