Re: Twitter poll result 2
Hi Francois, I'm glad to read such a clear and smart analysis. I agree with you at 100%. Buzz is something we definitely lack of. We should improve our examples and write more articles on Wicket. I've also noted that Vaadin people have increased the amount of the "buzz" lately. For Vaadin it's easier since they have a commercial company behind it, and it seems to m they have joined the forces with other commercial entities (like JRebel and people behind jOOQ), but this is just my impression. After the ApacheCon I hope to find the time to write more on DZone about Wicket. I also think that it's important to work against some misconceptions that Wicket might have in dev community (for example, the idea that it is a stateful-only framework). At least this is what i will try to do at ApacheCon. Andrea. On 01/11/2016 11:44, Francois Meillet wrote: Hi, Following Tobias Soloschenko thread about the Twitter poll result I think we should focus on who who don't know Wicket. People who don't like Wicket, the unhappy users, will not come back. Only 34% of the respondents know what is Apache Wicket. Put another way 66% don't ever know what is Wicket. A) Apache Wicket's Adoption —— Adoption (software or any good) has 2 channels : buzz and word of mouth. For many authors word of mouth (WOM) influence 50% of the acquisition decision. So to increase Wicket Adoption we have 2 choices : 1) Wicket buzz) The buzz channel is done via articles, conferences (ApacheCon), meetup, social network (twitter). The superbe Wicket's website welcome everyone who wants to adopt Wicket. How the 50% of the 66% who don't know Wicket could be targeted ? By increasing the buzz. We can increase the buzz by more articles in which we could give specific examples where Wicket has strong value, write beautiful small examples to demonstrate the beauty of our beloved framework (this is what Vaadin has been doing since few months ), nice conference's coverage (ApacheCon video on youtube) By improving its impact using redundancy. Mentioning Wicket'skills on dev's social network profile (linkedin) ! (very few do it) is one example. By retweeting, by mentioning Wicket more often, 2) Word of Mouth) (WOM) Word of Mouth is the passing of information from person to person by oral communication (Wikipedia) WOM is the second channel, with an equal importance for Wicket Adoption. Word of Mouth is made of by the developers and project managers feedbacks. A lot has been done, through a nice and complete user guide to make the learning curve easier. if I think we should focus on who who don't know Wicket, I think we must hava a clear understanding why developers don't like Wicket. Understanding the difficulties and dislikes is very important. And should be done without affect. B) Difficulties and dislikes: —— In many projects, developers start writing few pages, using the examples. Most of the time developers have difficulties understanding models, and while trying to implement the functionalities that have to be done for yesterday, they still do not masterise theirs models, and do not pay attention to their codes. They just do not have time for these 2 tasks. They have to deliver. Bugs will be fixed after. They do copy and paste to implement first functionalities, and after few weeks, the code is so messy that you start thinking at the servlet / jsp … ! The style of coding we can find in the Wicket Examples is used to write ugly classes. In many places I have seen pages with more than few thousand lines. No one wants to read it before lunch time or a friday afternoon ! And as in any corporation, developers attempt to name a culprit. From outside the developer's corporation. Guess what ? This is the time Wicket starts to receive a bad reputation. And this is where this bad reputation stops the natural spreading Wicket’ usage between developers, between teams in a company, between companies. Word of mouth adoption channel is closed here. And needless to say, when new developers arrive on this kind of existing project, they are not in a "wicket's loving mood". Difficult to understand, difficult to maintain. And you know, the first meeting is important ! We can improve a lot Wicket Examples's value by having more comments or a better pedagogical naming convention. A "test yourself" page where developers can test their Wicket’s skills, with the correct answer and with the minimum level score to start using Wicket with ease, could be interresting. But it's not good enough. The difficulties I have found in many places are : Model, Page, Granularity Model, Page, Granularity : from my clients, these 3 points are the "dislike's culprit" : Models seem to be difficult to masterise, but it’s a core concept. Getting Models proficiency is the key. Writing page (java code) that are well structured, have nice code, are easy to read should be highlighted (even if it’s more a Java
Re: File upload using REST API
Hi, I haven't any code that does file upload, but I think you need to implement a custom IWebSerialDeserial that extracts file (or a list of them) from request an then you can pass this value to your REST resource with annotation @RequestBody. Files can be extracted from request in the usual way: http://stackoverflow.com/questions/2422468/how-to-upload-files-to-server-using-jsp-servlet On 24/10/2016 08:13, James Selvakumar wrote: Dear friends, I want to upload a file using REST API. I'm already using WicketStuff REST library. I searched and couldn't see any example based on Wicket. Can anyone guide me to understand how to do this in Wicket? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 8.0.0-M1 MarkupNotFoundException
Ok thank you! Andrea. On 20/10/2016 12:07, Greg Johnson wrote: Create link missing from home page (MacOs 10.12 Safari 10.0) … Found a “create” link in the help docs … Created WICKET-6256 Regards, Greg Johnson On 20 Oct. 2016, at 19:47, Andrea Del Bene <an.delb...@gmail.com> wrote: That's strange...you should be able to create issues as you belong to jira-users group: https://issues.apache.org/jira/plugins/servlet/project-config/WICKET/permissions Which is exactly the problem or the error you get? On 19/10/2016 02:40, greg.johnson wrote: sure, i don't seem to have permission in jira to create an issue, am i missing something? username: gregjohnson thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/8-0-0-M1-wicket-link-MarkupNotFoundException-tp4675812p4675828.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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 8.0.0-M1 MarkupNotFoundException
That's strange...you should be able to create issues as you belong to jira-users group: https://issues.apache.org/jira/plugins/servlet/project-config/WICKET/permissions Which is exactly the problem or the error you get? On 19/10/2016 02:40, greg.johnson wrote: sure, i don't seem to have permission in jira to create an issue, am i missing something? username: gregjohnson thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/8-0-0-M1-wicket-link-MarkupNotFoundException-tp4675812p4675828.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: 8.0.0-M1 MarkupNotFoundException
Hi Greg, can you open an issue and attach the quickstart. Thank you. On 17/10/2016 01:19, Greg Johnson wrote: Hi, the example is a very basic “menu” example where on menu select main content is changed. From the attached quickstart … * run Start.java * localhost:8080/ - Home Page displays * Press browser refresh - Home Page displays * Press browser refresh - MarkupNotFoundException: Markup not found for Component: [TransparentWebMarkupContainer [Component id = wicket_link1]] if the tags are removed there is no problem. Note that there are no links, it is just the mere presence of the tags that seems to cause the problem. Perhaps the architecture is flawed, however it is not clear to me why it only fails on the 3rd render. Any help would be appreciated, thanks. Regards, Greg Johnson
Re: Wicket vs JS frameworks.
IMHO things are quite simple. JS base app are told to be highly scalable because they rely on a REST, stateless architecture. So scaling is just a matter of adding servers without worrying of replicating a user session. This is true until you need to log a user into your app. At this point someone, somewhere (usually in a oauth server) has to "remember" your logged in users somehow, which means that you are no more stateless :-). When Wicket was born people didn't use to care about been stateless at any cost, and unfortunately for many years Wicket was labeled as stateful framework. This is absolutely wrong as "by default" a Wicket app is stateless. The user guide explain in details such concept. With the last release we also made an additional effort to keep AJAX features stateless-friendly. The bottom line: no matter which framework you use. if you want to be scalable be stateless. If you can't, keep user session the smallest you can. :-) On 15/10/2016 02:57, fzb wrote: From the posts so far this is what i understand.. 1. JS based apps are best suited for high scale applications.. It is worth the effort you take to build and maintain such apps.. 2. Wicket can scale only to certain extent based on the server capacity ? If so how to quantify ? (What about load balancing ? What about stateless pages ? Why it does not scale ?) 3. JS based apps resource availability is plenty.. So for new projects better to go with these ? - What if the maintaining these apps becomes tedious due the cons of these JS discussed earlier. May be some more insights will help us all understand, how to choose what depending on the scenarios in hand. - fzb -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-vs-JS-frameworks-tp4675771p4675796.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: Wicket vs JS frameworks.
The "new" JS Frameworks in combination with JSON have made quite cheap building CRUD web app. But there are a number of factors that I personally don't like at all with this type of solutions: - they only work with single-page applications. period. SPA is not a silver-bullet, it's not the best solution for everything. - the same can be stated for JSON. I might need to use another data format and maybe I might prefer a relational db instead of Mongo... - hard to test your app in isolation. With wicket you can test your generated HTML without even using a server. - standard "bending": you have to use something that is not pure HTML (custom tags, JSX, ...) and then COMPILE it to something standard (most of the time JS) :-( - ... My 3 cents. On 14/10/2016 06:33, fzb wrote: Hi, I am a fan of Wicket & had been working on for last 6 to 7 yrs using the same. Recently had evaluated few frameworks Angular, ReactJS etc in view of developing new applications, I did not feel them appealing may be due to my very bad java script knowledge.. if at all i learn and start working on it, I felt I am not going to be productive on it. Currently I feel Wicket due to its Component based is very much productive and helps to give the consistency across application in terms of look n feel etc. Just thought of hearing comments from others as well .. Are those using Wicket, using other frameworks as well. Are there any combinations which works well with Wicket or otherwise. - fzb -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-vs-JS-frameworks-tp4675771.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: examples7x.wicket.apache.org --> 502 Proxy Error
Restarted. Now should be ok. Thank you! On 04/09/2016 22:15, Francois Meillet wrote: http://examples7x.wicket.apache.org/index.html is down. There is a 502 Proxy Error http://examples6x.wicket.apache.org/index.html is OK. François - 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: Chrome extension and Eclipse plugin for wicket-source helper are updated!
Thank you VERY much Jenny! On 22/08/2016 03:30, Jenny Brown wrote: About 5 years ago, I created wicket-source, a set of extensions that let you inspect a wicket component in your browser, and click a button to go to that line of your source code in Eclipse. As time went on, the browser extensions drifted out of compatibility, to the sadness of those who used them. Eventually even the workarounds stopped working. So this weekend, I update the Chrome wicket-source extension for Chrome 48 (updated in chrome web store) and updated the Eclipse plugin (jar is on github) for Eclipse Neon. (Yeah!!!) Screenshots, details, and download links are on the wiki: https://github.com/jennybrown8/wicket-source/wiki The server-side wicket application module still works as before, and is available for Wicket 7. The Firefox plugin was deprecated, and requires a full rewrite from scratch, so it's not usable for now. I'll try to come back to this when Firefox Web Extensions and Firebug 3 stabilize and provide the APIs I need for it to work. I forked the project when I separated from the employer where it was created, so there is a new package name for the extensions that have been updated. At this time, the maven coordinates for the web application server-side plugin remain with the old name. The wiki documents all of this. I looked at Eclipse Marketplace and the self-hosting was confusing; if someone familiar with that wants to pair with me to try to get it properly submitted, I can try. I don't have my own hosting service for the binaries. Jenny Brown - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problem migrating to Wicket 7
Hi, Dirk could you test your app with version 7.4.0-SNAPSHOT? This should solve your problem. Thank you. Andrea. On 18/06/2016 11:03, Martin Grigorov wrote: https://issues.apache.org/jira/browse/WICKET-6185 On Fri, Jun 17, 2016 at 8:46 PM, Martin Grigorovwrote: It is caused by a change for WICKET-5988 Now the body container is not added to the Border but it relies solely on component resolving. The problem is that the resolving is not used when visiting the children Please file a ticket at JIRA! Thanks! On Jun 17, 2016 10:08 AM, "Martin Grigorov" wrote: Hi, I'll take a look soon! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jun 16, 2016 at 8:04 AM, Dirk Forchel wrote: Hi Martin, I've added a much more simpler test application to show what's not working (see myproject2.zip below). On the first page you can see on the right side a TextComponent with a simple Behavior added to a Page. This Behavior adds some JavaScriptResourceReference (the jQuery function definition) and an OnDomReadyHeaderItem (the jQuery function call) to the header. If it works, the value of the input field is replaced from "test" to "Hello Dude!" and the input element is highlighted for a short moment. On the second page you can find the same functionality but added to a Border component. This works as well as described. On the third page I've added a TextComponent with the same Behavior but to the BorderBodyContainer (the content area) of our layout class (a Border component) which is added to another Border (our layout container). On this page, the Behavior is NOT working with Wicket 7.3. But the same IS working with Wicket 6.23. You can easily switch between both versions by changing the wicket.version in the pom.xml. I've noticed during my investigation, that the "renderHead" method of the Behavior class never gets called and I have not glue why! I could imagine, that one reason could be the fact, that we use two nested Border components. But the behavior should work with this combination as well, I think. Could you please have a look at this problem. Here is the quickstart: myproject2.zip
Re: examples7x.wicket.apache.org not available
Restarted! Should shortly be available. Andrea. On 08/06/2016 11:11, Marc Ende wrote: Hi, I've seen that the http://examples7x.wicket.apache.org/ is currently not available. There is an proxy error. It would be great if the examples would be available soon, they're a great resource. ;) Cheers Marc - 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: Regarding nested multipart modal dialog
Sorry if I jump into the conversation so roughly, but isn't enough to override updateAjaxAttributes of FormPanel's AjaxButton(OK_ID) ?: @Override protected void updateAjaxAttributes(AjaxRequestAttributes attributes) { super.updateAjaxAttributes(attributes); attributes.setMultipart(false); } I did a test with the quickstart and seems to work. On 20/05/2016 10:24, Rakesh A wrote: Hi, Created JIRA issue - https://issues.apache.org/jira/browse/WICKET-6171 I tried to refresh the root form by adding it to 'AjaxRequestTarget', but it didn't work. Any workaround you know of, that I can use for now ? Regards, Rakesh.A -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Regarding-nested-multipart-modal-dialog-tp4674764p4674769.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: [wicketstuff-restannotations] AbstractRestResource.toObject makes it impossible for mapped methods to know a parameter conversion went wrong.
You're welcome! On 10/05/2016 15:06, Fabio Fioretti wrote: I confirm version 6.23.0 fixed the problem. Thank you for the great support! Kind regards, Fabio On Thu, Apr 28, 2016 at 12:02 PM, Fabio Fioretti < windom.macroso...@gmail.com> wrote: Thanks Andrea, that would be excellent! Keep up the great work, Fabio On Thu, Apr 28, 2016 at 11:52 AM, Andrea Del Bene <an.delb...@gmail.com> wrote: Thank you for the issue! I think we can make it for next release 6.23.0 which should come quite soon (at the moment we are voting to release Wicket 6.23.0). Andrea. On 28/04/2016 11:34, Fabio Fioretti wrote: Done: https://github.com/wicketstuff/core/issues/490 Many thanks, Fabio On Thu, Apr 28, 2016 at 11:03 AM, Martin Grigorov < martin.grigo...@gmail.com wrote: Please file an issue at Wicketstuff GibHub. On Apr 28, 2016 10:31 AM, "Fabio Fioretti" <windom.macroso...@gmail.com wrote: Hi Martin, Thanks, I agree - findOffices() shouldn't be executed at all. In fact, handleMethodExecution() returns before invoking application code in all other cases (step 1 for unauthorized access, step 3 for validation errors). Any chance to have it fixed relatively soon? (maybe Andrea can answer this) Kind regards, Fabio On Thu, Apr 28, 2016 at 6:44 AM, Martin Grigorov <mgrigo...@apache.org wrote: Hi, On Wed, Apr 27, 2016 at 12:07 PM, Fabio Fioretti < windom.macroso...@gmail.com> wrote: Hi all, Please consider the following simple implementation of AbstractRestResource (6.22.0): @ResourcePath("/rest/api") public class MyRestResource extends AbstractRestResource { public MyRestResource () { super(new JsonWebSerialDeserial(new GsonObjectSerialDeserial())); } @MethodMapping(value = "/offices") public List findOffices( @RequestParam(value = "region", required = false) Integer regionId) { return findOfficesByRegion(regionId); } } My question relates to the findOffices method and its filtering regionId parameter when the value is not a valid integer. For example, consider the request 'GET /rest/api/offices?region=AA'. At the second step of AbstractRestResource.handleMethodExecution, extractMethodParameters is invoked, which in turn triggers the conversion of all parameters through the static method toObject. When the conversion goes wrong and ConversionException is thrown, toObject catches it, sets the response status to 400 and returns null! Now, when my findOffices is finally executed, I get a null regionId but I don't know whether it was not valid or the parameter was not present at all. Checking the response status downstream is also particularly hard because I have no getStatus (Tomcat 6 here, ouch!). To my mind, findOffices should return null instead of the unfiltered list of offices if the conversion went wrong, even because the response status is 400 (as set by toObject). However, how can I know it? Any suggestions? IMO this is a bug in the library. #findOffices() should not be executed at all. A response with status code 400 should be returned immediately after the unsuccessful convention without giving a chance to the application code to be executed. Many thanks, Fabio - 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: Wicket jQuery UI - 4th anniversary!
Congratulations Sebastien!!! And the new site is REALLY nice! Andrea On 02/05/2016 22:52, Sebastien wrote: Dear Wicket jQuery UI users, I'm happy to announce the 4th anniversary of the project since its first release! :) *Stats* A few words about project's stats: - visits on the demo site almost reach 550k pageviews since its launch - artifact downloads are still increasing - Kendo UI is confirming its progression over jQuery UI There is a (very) big peak on march, which might be due to a recent InfoQ interview about Wicket 7.2.0 (on which Wicket jQuery UI was quoted) [1]. *Surprise!* This year, the project gets a very nice birthday gift from my best-geek-girl-friend! Thanks to her, the demo site has a brand new responsive skin :) It is not yet officially active, but you can still have a preview [2], your feedback is more than welcome! Thanks again for your confidence and, to whom is concerned, your very precious help! :) -Sebastien. [1] http://www.infoq.com/news/2016/03/apache-wicket-7.2 [2] http://163.172.29.241/wicket-jquery-ui/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-restannotations] AbstractRestResource.toObject makes it impossible for mapped methods to know a parameter conversion went wrong.
Thank you for the issue! I think we can make it for next release 6.23.0 which should come quite soon (at the moment we are voting to release Wicket 6.23.0). Andrea. On 28/04/2016 11:34, Fabio Fioretti wrote: Done: https://github.com/wicketstuff/core/issues/490 Many thanks, Fabio On Thu, Apr 28, 2016 at 11:03 AM, Martin Grigorovwrote: Hi Martin, Thanks, I agree - findOffices() shouldn't be executed at all. In fact, handleMethodExecution() returns before invoking application code in all other cases (step 1 for unauthorized access, step 3 for validation errors). Any chance to have it fixed relatively soon? (maybe Andrea can answer this) Kind regards, Fabio On Thu, Apr 28, 2016 at 6:44 AM, Martin Grigorov wrote: Hi, On Wed, Apr 27, 2016 at 12:07 PM, Fabio Fioretti < windom.macroso...@gmail.com> wrote: Hi all, Please consider the following simple implementation of AbstractRestResource (6.22.0): @ResourcePath("/rest/api") public class MyRestResource extends AbstractRestResource { public MyRestResource () { super(new JsonWebSerialDeserial(new GsonObjectSerialDeserial())); } @MethodMapping(value = "/offices") public List findOffices( @RequestParam(value = "region", required = false) Integer regionId) { return findOfficesByRegion(regionId); } } My question relates to the findOffices method and its filtering regionId parameter when the value is not a valid integer. For example, consider the request 'GET /rest/api/offices?region=AA'. At the second step of AbstractRestResource.handleMethodExecution, extractMethodParameters is invoked, which in turn triggers the conversion of all parameters through the static method toObject. When the conversion goes wrong and ConversionException is thrown, toObject catches it, sets the response status to 400 and returns null! Now, when my findOffices is finally executed, I get a null regionId but I don't know whether it was not valid or the parameter was not present at all. Checking the response status downstream is also particularly hard because I have no getStatus (Tomcat 6 here, ouch!). To my mind, findOffices should return null instead of the unfiltered list of offices if the conversion went wrong, even because the response status is 400 (as set by toObject). However, how can I know it? Any suggestions? IMO this is a bug in the library. #findOffices() should not be executed at all. A response with status code 400 should be returned immediately after the unsuccessful convention without giving a chance to the application code to be executed. Many thanks, Fabio - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [wicketstuff-restannotations] How to automatically generate Swagger definitions.
Hi, at the moment we don't have such kind of integration with Swagger. You may obtain some results if you use Spring in your application: https://dzone.com/articles/swagger-make-developers-love. However I've never tried this kind of solution. On 25/04/2016 16:08, Fabio Fioretti wrote: Hi all, I have been successfully using wicketstuff-restannotations to create some REST web services in my Wicket 6.22.0 application - thanks for that, very straightforward. Now that my REST resources and methods are complete and correctly annotated, I would need to generate the related Swagger definitions. Is there an easy way to do so? Many thanks, Fabio - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: HTML and Binding generator for Wicket
Nice work! I remember I tried to do something similar in an old project but the final result was much more rudimental. Thank you! On 12/04/2016 15:28, subes wrote: Hi there, I have a framework to announce that was built on top of Wicket and Wicket-Bootstrap. It applies the Naked Objects pattern to generate HTML files and the corresponding Wicket Binding for you based on your models. All the while allowing you to fully stay in control and be able to do what you are used to with Wicket and the components provided by Wicket-Bootstrap. More info at the documentation website: http://invesdwin.de/nowicket/ And on GitHub: https://github.com/subes/invesdwin-nowicket So just wanted to express my thanks to the Wicket developers and contributors who made this possible. :) And yes, I am aware of Apache Isis and especially talk about the difference between NoWicket and Apache Isis in the Introduction of the documentation. Mainly the difference is that NoWicket does not aim at going as deep as the persistence layer for the models and does not want to be a full CRUD framework. Also explaining what disadvantages that would have for wanting to stay in control. With NoWicket you actually still have your HTML files to edit and the Wicket Page and Panel implementations you can customize. NoWicket just automates the boring coding for most needs and reduces the amount of SLOC to write by a magnitude. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
New sit for user guide examples.
Hi, I've finally found the time to work on a site with live examples from the user guide. You can see the result here : http://examples-wickettutorial.rhcloud.com/ It's an early version so any feedback is welcome! Have fun. Andrea. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: New documentation on Wicket internals
Thanks also to Martin who double-checked my docs! Andrea. Great Andrea! Thanks a lot! kind regards Tobias Am 25.03.2016 um 16:34 schrieb andrea del bene <an.delb...@gmail.com>: Hi, I've added a couple of notes to the userguide about markup parsing and autocomponents: https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents Have fun! Andrea. - 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
New documentation on Wicket internals
Hi, I've added a couple of notes to the userguide about markup parsing and autocomponents: https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#autocomponents Have fun! Andrea. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: HTML markup file generated by code or HTML markup file with parameter
https://ci.apache.org/projects/wicket/guide/7.x/guide/single.html#advanced_5 On 25/03/2016 12:24, Ernesto Reinaldo Barreiro wrote: IMarkupResourceStreamProvider? On Fri, Mar 25, 2016 at 12:19 PM, andre seamewrote: Hello, Question? I would like to create a component.java that is associated to a HTML markup file component.html, but a part of the markup file must be dynamic. Why? A standard form is associated to a HTML markup file like: ... ... .. ... But, I would like to group the input fields with other information, therefore I create panels. So my form is now associated to a HTML markup file like: ... panel contents come here - The panel includes ... panel contents come here - The panel includes .. panel contents come here - The panel includes ... How to do that? Create GenericPanel.java and Panel1.java that extends GenericPanel.java. Panel1.java is associated to the HTML markup file Panel1.html: ... ... And do again for iI = 2 to 10. This will probably work, but it is complex. The idea is to create a repeater: http://wicket.apache.org;> panel contents come here - The panel includes So the question is how to do the association between GenericPanel.java[i] and GenericPanel.htlm[i] that must contain ? As far as I understand the wicket mechanism, the HTML markup file is a constant file that describes the HTML code of the component. Is it possible in wicket 6? Wicket 7? Thanks, PHL - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Non managed CSS
yes :) https://ci.apache.org/projects/wicket/guide/6.x/guide/single.html#resources_9 On 21/03/2016 16:08, gmparker2000 wrote: Just wondering if there is a way to have unmanaged CSS appear last in the HTML head. I want Wicket to include managed CSS but have the unmanaged CSS appear last so it can contain overrides. Currently it appears at the top of the head section. I am using Wicket 6. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Non-managed-CSS-tp4674080.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: Apache Wicket mentioned @ heise Developer
Thank you Tobias! On 07/03/2016 10:53, Tobias Soloschenko wrote: Hi all, just saw that Apache Wicket is mentioned @ heise Developer (german): http://www.heise.de/developer/meldung/Developer-Snapshots-Programmierer-News-in-ein-zwei-Saetzen-3128501.html Translated (english, more or less): https://translate.google.com/translate?hl=en=de=en=http%3A%2F%2Fwww.heise.de%2Fdeveloper%2Fmeldung%2FDeveloper-Snapshots-Programmierer-News-in-ein-zwei-Saetzen-3128501.html kind regards Tobias - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: https://twitter.com/apache_wicket after 10 months
Thank you Francois! On 05/02/2016 09:05, Francois Meillet wrote: Dear All, https://twitter.com/apache_wicket after 10 months : 50 tweets posted about technical articles 50 tweets posted about src example lib 500 tweets posted about websites based on Apache Wicket Stay tuned, follow @apache_wicket on Twitter ! https://twitter.com/apache_wicket François - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DateTimeField AJAX DatePicker not work
Hi, another possible solution is to queue components instead of adding them. This seems to work fine with inline enclosures. Andrea. On 04/02/2016 10:51, Bas Gooren wrote: Hi Christopher, Martin, I just did a quick debug, and it’s caused by the inline enclosure. When I replace that with a WebMarkupContainer, and manage the visibility of that element, everything works as expected. See my gist here: https://gist.github.com/bgooren/11602fa0d786548bfd70 We’ve had some unexpected issues with inline enclosures in the past, which is why I usually use explicit containers. In any case: the DatePicker behavior does not get it’s renderHead() method called once the second DateTimeField becomes visible, and it is inside the inline enclosure. Why that is the case requires more debugging. My gist provides a solution in the meantime. Met vriendelijke groet, Kind regards, Bas Gooren Op 3 februari 2016 bij 23:41:21, Martin Grigorov (mgrigo...@apache.org) schreef: Hi, I don't have time to debug this problem now but I'll try to do it early next week. Please create a ticket in JIRA so it won't get forgotten! Thanks! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Feb 2, 2016 at 2:02 PM, Christopher Authwrote: Hi, I have some problems with the org.apache.wicket.extensions.yui.calendar.DateTimeField. In the constructor I set the visibility to false. Ajax redraw, when a checkbox is clicked, the DateTimeField is marked as visible. As far as everything works. Only then I can't open the DatePicker of the second DateTimeField. An example is below https://github.com/ChrAu/wickettest to find. I have test it with Wicket 6.19/6.22/7.2 Regards Christopher - 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: Wicket Presentation
Hi Martijn, I think it would be ok if the presentation was more or less like the one you have done for the 10th year of the project. You might add some slides to promote the new site and the community resources (wicketstuff, twitter, etc...). My two cents. On 27/01/2016 10:40, Martijn Dashorst wrote: I'm still considering it. Unfortunately it falls right in a very busy period for me. What kind of presentation would you like to go to? What kind of subjects should be covered? Martijn On Tue, Jan 26, 2016 at 7:20 PM, Jered Myerswrote: Is anybody planning any Wicket presentations at ApacheCon North America in May? -- Jered - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 8
So far the most notable things you can find in branch lambdas are new lambda-enhanced models (see https://github.com/apache/wicket/commit/ae70d7d02821695e165e3a36828792de8d21f14c) and MarkupContainer#childrenStream to access children component as Java 8 Stream (see https://github.com/apache/wicket/commit/73ac8c7e6da3ff9dd0244ad66c63944ba3d64c78). Andrea. On 08/01/2016 09:56, Martin Grigorov wrote: Hi, The migration guide is still very short, i.e. there are no many changes in master branch yet: https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+8.0 There are some changes in branch lambdas ( https://github.com/apache/wicket/tree/lambdas) which have to be evaluated and eventually merged to master. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jan 8, 2016 at 1:57 AM, Sven Ludwigwrote: Hi! it has been a while. I just checked https://cwiki.apache.org/confluence/display/WICKET/Ideas+for+Wicket+8.0 and https://wicket.apache.org/start/wicket-8.x.html Can you provide a few links or pointers to commits, classes, methods, tests or functional interfaces (just as you see fit) regarding specifically the support for Lambda handlers? I would really like to have a closer look if code already exists and I would prefer to start with a hint from one of the devs. Kind Regards, Sven On 25.10.15 at 02:57, Mihir Chhaya wrote: Thanks for the reply. -Mihir. On Sat, Oct 24, 2015, 8:18 AM Martijn Dashorst < martijn.dasho...@gmail.com> wrote: No. I don't think it will be in 6 months. We might do some milestones. We'll be sure to get Java 8 features right. Martijn On Saturday, 24 October 2015, Mihir Chhaya wrote: Hello, On apache wicket website download section, there is link for wicket 8 snapshot. Just curious; is there planned or projected date decided for the final release? Thanks, -Mihir. -- Become a Wicket expert, learn from the best: http://wicketinaction.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: Wicket CSRF/XSRF protection
Hi, I think you might need to roll out your own RequestCycleListener to check for the XSRF-TOKEN. Or alternatively if you are using wicketstuff REST support you could use hook method onBeforeMethodInvoked to check the token before REST API is invoked. See https://github.com/wicketstuff/core/tree/master/wicketstuff-restannotations-parent and javadoc http://wicketstuff.org/core/javadoc7/apidocs/org/wicketstuff/rest/resource/AbstractRestResource.html Andrea. Hi all, Starting from [this][1] question on stackoverflow, I'm going to ask one thing more. I've developed a web application in which Apache Wicket plays as "REST backend", it only exposes HTTP Resources, there is an application and there are no pages, and no html related. All "frontend" is developed in AngularJS. Now, I need protection against CSRF attacks. AngularJS documentation says: To take advantage of this [angular XSRF protection], your server needs to set a token in a JavaScript readable session cookie called XSRF-TOKEN on first HTTP GET request. On subsequent non-GET requests the server can verify that the cookie matches X-XSRF-TOKEN HTTP header, and therefore be sure that only JavaScript running on your domain could have read the token. How can I get this token managed by Apache Wicket? Are there wicket implementations of such mechanism? I found /*CsrfPreventionRequestCycleListener*/ but this doesn't protect all requests, it seems to be configured (by default) only to protect ajax requests on components or links; or /*CryptoMapper*/ with /*KeyInSessionSunJceCryptFactory*/, but this does not seem to do what I'm looking for. I "just" want to send a token, not to crypt urls, but if guarantees the same protection I'll do. I've not found so much on documentation, can you help me? [1]: http://stackoverflow.com/questions/29881338/add-csrf-protection-header-to-wicket-ajax-call#new-answer Best regards, Andrea - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Security Issue or incorrect usage?
Hi, the wiki entry you have found is pretty old (StyleSheetReference is no more part of the API). Where did you read the note you reported in the mail? BTW: I don't think it's a security issue. It just says that variable interpolation is done the first time the resource is requested, so you should avoid to put sensitive user informations into your dynamic CSS/JS. Andrea. Guys, Please advise on the following "feature". There is the following cool ability in wicket: https://cwiki.apache.org/confluence/display/WICKET/Dynamically+Generate+a+CSS+Stylesheet Pretty much the same approach can be used for JavaScript. But it's noted: if try to retrieve URL for dynamically generated CSS or JS after initial load of it by "legal" use - you will receive file with substituted parameters for first user. Is it security issue or just incorrect usage of this feature? Thanks, Ilya - Orienteer(http://orienteer.org) - Modern Data Warehouse for your business. - 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: Problem with wicket encolsures and (possibly) OpenEntityManagerInViewFilter
Hi, have you tried Wicket 7.0.0 as well? The problem occurred only with 7.1.0? Try to use version 7.2.0-SNAPSHOT which contains some bug-fixes for enclosures and component queuing. Hello! I've introduced OpenEntityManager filter to my application and switched to wicket 7.1.0 and all enclosures that worked perfectly before went crazy. Here is a web xml snippet: open-entitymanager-in-view-filter org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter open-entitymanager-in-view-filter /* TestWebApplication org.apache.wicket.protocol.http.WicketFilter applicationClassName com.test.rest.webapp.TestWebApplication TestWebApplication /* Here is the exception I am getting: org.apache.wicket.WicketRuntimeException: A component with id: wicket_enclosure2324 has already been queued at org.apache.wicket.ComponentQueue.add(ComponentQueue.java:60) at org.apache.wicket.ComponentQueue.add(ComponentQueue.java:43) at org.apache.wicket.MarkupContainer.queue(MarkupContainer.java:1710) at org.apache.wicket.MarkupContainer.dequeueAutoComponents(MarkupContainer.java:1379) at org.apache.wicket.MarkupContainer.onInitialize(MarkupContainer.java:1364) at org.apache.wicket.Page.onInitialize(Page.java:299) at org.apache.wicket.Component.fireInitialize(Component.java:877) at org.apache.wicket.MarkupContainer.internalInitialize(MarkupContainer.java:994) at org.apache.wicket.Page.isPageStateless(Page.java:465) at org.apache.wicket.request.handler.render.WebPageRenderer.isPageStateless(WebPageRenderer.java:287) at org.apache.wicket.request.handler.render.WebPageRenderer.shouldRenderPageAndWriteResponse(WebPageRenderer.java:329) at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:193) at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175) at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:865) at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293) at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:261) at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:203) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:284) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307) at org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:178) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:453) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:560) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1072) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:382) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1006) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:365) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:926) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:988) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at
Re: Quetsion to nesting Forms and reflecting states of FormComponents after ajax refreshs
Hi, playing with the quickstart I've noticed something strange that might help to solve this issue. Before rendering phase both the inner and outer form are marked as submitted (Form#isSubmitted returns true). This is quite strange as I would expect that only the inner form would be marked as submitted. It turned out that the cause of this strange behavior is AjaxFormSubmitBehavior#onEvent which just contains: getForm().getRootForm().onFormSubmitted(new AjaxFormSubmitter(this, target)); I don't understand why the onFormSubmitted is called on the root form and not on the actually submitted one. If we remove getRootForm() the issue is resolved and no test gets broken. The call to getRootForm() was introduced ages ago for WICKET-1282 but the issue doesn't provide much details about it. Andrea. Hi, > 2) if the application needs to repaint any form which is not > processed then the application has to call #inputChanged() for > this form / form component this will break current applications. We can argue which approach is more consistent, but I don't think we should change this just because of a single user request: His solution is to not using nested forms. Regards Sven On 20.11.2015 17:13, Martin Grigorov wrote: On Fri, Nov 20, 2015 at 5:02 PM, Sven Meierwrote: When a nested form is submitted Wicket calls the processing methods only for the nested form. I don't see a reason why #inputChanged() should be an exception. The outer form is not processed, because we don't want validation errors to appear. #inputChanged() is called, so that on a possible render of the whole page the input of the user is preserved. This is what I said in my mail earlier. I suggest: 1) call form processing methods only for the submitted form (and the ones which requests processing explicitly, i.e. #wantSubmitOnNestedFormSubmit() and #wantSubmitOnParentFormSubmit()) 2) if the application needs to repaint any form which is not processed then the application has to call #inputChanged() for this form / form component The current way is: 1) call #inputChanged() for *all* 2) call other processing methods only for the submitted one and the extra ones which explicitly want to participate 3) the application should call #clearInput() for any non-processed For me the approach I suggest is more consistent and expected. it is very common to reuse components in Wicket I'm shocked ;) So a Panel with a Form could appear as a nested anywhere. That is the main reason to support nested forms. Yes, and it comes with a price. In most cases it's not necessary to include a form in panels - generally I would advice against it: - because "it's not supported in HTML" - again, it comes with a price (see above) Have fun Sven On 20.11.2015 16:47, Martin Grigorov wrote: On Fri, Nov 20, 2015 at 4:37 PM, Sven Meier wrote: IMO the current behavior is wrong. I don't see anything wrong with the current nested form handling. Care to elaborate? The problem I see is that Wicket treats #inputChanged() differently than all other Form processing methods (like #validate(), #on[In]Valid(), #updateModel()). When a nested form is submitted Wicket calls the processing methods only for the nested form. I don't see a reason why #inputChanged() should be an exception. It's rather unusual to have to formComponents for the same model on a single page. IMHO Patrick shouldn't use nested forms in the first place, I consider them an advanced feature. Advanced or not, it is very common to reuse components in Wicket. So a Panel with a Form could appear as a nested anywhere. That is the main reason to support nested forms. Regards Sven On 20.11.2015 16:06, Martin Grigorov wrote: OK. I see what happens. At org.apache.wicket.markup.html.form.Form#onFormSubmitted(org.apache.wicket.markup.html.form.IFormSubmitter) Wicket calls #inputChanged() for the root form, so this calls #inputChanged() on *all* FormComponents (including nested ones). My first reaction is: this is a bug! But then ... the purpose of the rawInput is to preserve the data entered by the user. So if your #onSubmit() logic in the nested form / submitter repaints the form components in the root/parent form then their data would be lost and the user will have to re-type it again. It seems in both cases the application developer will have to do something: 1) either clear the input manually (as now) 2) or update it manually when needed (by calling #inputChanged() only on the FormComponents in the rootForm). IMO the current behavior is wrong. Please create a bug with a quickstart. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Nov 20, 2015 at 3:51 PM, Patrick Davids < patrick.dav...@nubologic.com> wrote: Hi Martin, this is true for my DropDownChoice2. But DropDownChoice1 does not get validated. So, this could be the reason why it is not
Re: Wicket 7.1.0 breaks OnChangeAjaxBehavior on Select2
Could you create a quickstart reproducing the problem and create a Jira issue? Thank you. On 28/10/2015 13:31, Peter Henderson wrote: Hi fellow users. A quick heads up. I've just upgraded from wicket 7.0.0 to 7.1.0. It looks like something has broken OnChangeAjaxBehavior on Select2 form fields. Hopefully I'll be able to build a quickstart later. The exception for the record. org.apache.wicket.core.request.handler.ComponentNotFoundException: Component 'form:partFF:fg:fg_body:edit:location' has been removed from page. at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:177) at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:865) at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293) at org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70) at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:203) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:284) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 8
Not yet AFAIK. We have just started to work on it scathing some ideas about adopting java 8 and improving the APIs. On 24 Oct 2015 13:33, "Mihir Chhaya"wrote: > Hello, > > On apache wicket website download section, there is link for wicket 8 > snapshot. Just curious; is there planned or projected date decided for the > final release? > > Thanks, > -Mihir. >
Re: Have a Heineken on me Wicket team!
How to say no to a beer ? :-) PS: a Franziskaner would be better :D On Wed, Sep 23, 2015 at 11:43 AM, Tobias Soloschenko < tobiassolosche...@googlemail.com> wrote: > :-D > > +1 to rename Wicket 7 to Wicket 007 > > Made my day :-D > > kind regards > > Tobias > > > Am 23.09.2015 um 10:25 schrieb Martijn Dashorst < > martijn.dasho...@gmail.com>: > > > > Did you use Wicket 007? > > > > Martijn > > > >> On Tue, Sep 22, 2015 at 11:15 PM, Paul Borswrote: > >> Soon we will lunch a small little site for the new James Bond 007 movie > and > >> as some of you might now, he started drinking Heineken now-a-day :) > >> > >> http://hknbond-us.heineken.com/ > >> > >> Just wanted to thank the Wicket team for making such simple projects > even > >> easier !!! > >> > >> - > >> ~ Thank you, > >>p...@bors.ws > >> -- > >> View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Have-a-Heineken-on-me-Wicket-team-tp4672013.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 > > > > > > > > -- > > Become a Wicket expert, learn from the best: http://wicketinaction.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 > >
11 years and still strong
https://dzone.com/articles/poll-what-java-jvm-frameworks-do-you-use :-)
Re: New Community page
On 24/08/15 17:29, Mihir Chhaya wrote: Thanks, Andrea. Very helpful links for developers like me and, everybody else looking into Wicket site for any other reason. My humble observation though; there is 'CONTRIBUTE' link before 'COMMUNITY'. Would it be helpful in 'linking' those two or having reference of COMMUNITY on the other one? Or, Contribute section mentioning other projects (WicketStuff and Wicket-Bootstrap - with reference to COMMUNITY page) Hi and thank you for your feedback. I think your observation is right. I will try to insert a reference to 'community' at then end of 'contribute' page. I hope I have not confused with mention of my observation above. Thanks again to you and the wicket team, -Mihir. On Mon, Aug 24, 2015, 5:25 AM Andrea Del Bene an.delb...@gmail.com wrote: Hi folks, I've uploaded a new page on our site called 'Community' where anyone can find the different community-driven resources for Wicket. https://wicket.apache.org/community/ I hope you will like it! Andrea - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
New Community page
Hi folks, I've uploaded a new page on our site called 'Community' where anyone can find the different community-driven resources for Wicket. https://wicket.apache.org/community/ I hope you will like it! Andrea
Web Frameworks pool
Hi guys, if you have 5 seconds to spare please vote this poll :). Thank you. Andrea. http://www.surveygizmo.com/s3/2262144/Poll-Which-JVM-Web-Frameworks-Do-You-Use
Unit testing with CDI
Hi folks, I'm trying to put together a minimal quickstart project illustrating how to use CDI in Wicket. I followed the code from the CDI example I was able to create a working application. The only problem I still facing is about unit testing. What should I do to write a test case for my application? I'm still getting a BeanManager not found error. I guess I have to configure something in the servlet context but I can't figure out what. Any idea? PS: the code is here https://github.com/bitstorm/WicketExperiments/tree/master/cdi-example
Re: Unit testing with CDI
ok, I'll give it a try. Thank you ! On 27 Jul 2015 18:35, Martin Grigorov mgrigo...@apache.org wrote: Hi, Master branch has some unit tests that use cdi-unit 2.x library. Can you use them as starting point? On Jul 27, 2015 6:28 PM, Andrea Del Bene an.delb...@gmail.com wrote: Hi folks, I'm trying to put together a minimal quickstart project illustrating how to use CDI in Wicket. I followed the code from the CDI example I was able to create a working application. The only problem I still facing is about unit testing. What should I do to write a test case for my application? I'm still getting a BeanManager not found error. I guess I have to configure something in the servlet context but I can't figure out what. Any idea? PS: the code is here https://github.com/bitstorm/WicketExperiments/tree/master/cdi-example
Re: Wicket 6 - test ajax component.
Hi, I don't think it's possible to send a specific key as this requires JavaScript code to be executed. But you can test AJAX events: //simulate an AJAX click event tester.executeAjaxEvent(label, click); See 'Testing AJAX events' in the userguide for more details. Andrea. On 20/07/2015 16:27, gump lee wrote: Dear All, Is it possible to write a unit test with WicketTester which I need to send Enter key to an AJAX component? Best regards, Gump - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-annotations and page mounting
Hi, AFAIK this is not possible, you must mount your pages using a path parameter (something like: 'summary/${account}'). andrea. On 10/07/2015 18:51, Jason Novotny wrote: Hi, I'm using wicket-annotations and I've added: newAnnotatedMountScanner().scanPackage(com.foo.web.pages).mount(this); in my Application class. My page classes all have: @MountPath(value =summary) However, I want to adjust the pages to not use query parameters like account=5 and use / like account/5 instead. Is there a way to set this across the app, just like scanPackage, or do I have to set this on each page in my application? I'm using latest Wicket 6. Thanks, Jason - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Broken URL on Wicket Homepage
Hi, we had an issue with the CI infrastructure and it's not completely solved yet for 6.x version. That's why docs for 6.x are not available. Andrea. On 02/07/2015 10:53, Urbani, Edmund wrote: Currently on http://wicket.apache.org/ under New and noteworthy there's this (non-linked and broken) URL: http://ci.apache.org/projects/wicket/apidocs/6.x/org/apache/wicket/markup/html/image/InlineImage.html This URL (pointing to the 7.x API) would actually work and make sense: http://ci.apache.org/projects/wicket/apidocs/7.x/org/apache/wicket/markup/html/image/InlineImage.html Kind regards, Edmund - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
I could do it if I knew what to do. Who is maintaining the examples site (in addition to you Martin)? Everything is possible. All I need is longer day. 24 hours are not enough... Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Jun 29, 2015 at 10:53 AM, Maxim Solodovnik solomax...@gmail.com wrote: Is it possible update http://www.wicket-library.com/ to have wicket7 examples as well? I believe this might be very useful :) On Mon, Jun 29, 2015 at 1:49 PM, andrea del bene an.delb...@gmail.com wrote: Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of improvements: 1) AbstractResource is now supports content-range and accept-range which is great! I'll remove my custom code for this :) 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) which is great :)) 3) MediaComponent requires *PackageResourceReference* as resourceReference :(( why it can't be ResourceReference? Are there any examples in wicket7 regarding new Video Component? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- WBR Maxim aka solomax - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket7: MediaComponent and Source classes
Hi, in wicket-examples take a look at the project in org.apache.wicket.examples.media Andrea. On 29/06/2015 06:47, Maxim Solodovnik wrote: Hello All, Recently I have upgraded to Wicket+wicketstuff 7.0.0-M6 and found lots of improvements: 1) AbstractResource is now supports content-range and accept-range which is great! I'll remove my custom code for this :) 2) HTML5 Video is supported by wicket itself (was removed from wicketstuff) which is great :)) 3) MediaComponent requires *PackageResourceReference* as resourceReference :(( why it can't be ResourceReference? Are there any examples in wicket7 regarding new Video Component? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Accessing a .properties file
Hi, if you are trying to read/write files in a specific package take a look here: http://stackoverflow.com/questions/5291852/writing-to-file-inside-package-java Andrea. Hi, I want to access a properties file using a BufferedInputStream for reading and a FileOutputStream for writing. My problem is that I don’t know what to use as constructor of the BIS/FOS. Currently I’m using just „config.properties“. But the program keeps throwing exceptions at me and it won’t stop. Can I use any variable like $tomcatHome or something like this in the constructor so the file is generated at a consistent location? Thanks for your time and help with this Lukas - 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
semiserious: Android M logo
Looks so familiar to me :-) https://www.google.it/webhp?hl=en#hl=enq=android+M+logo - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Use thrid party JQuery Plugin in Wicket Panel
Hi, maybe this paragraph of the user guide can help you: http://ci.apache.org/projects/wicket/guide/6.x/guide/single.html#resources_6 You can read your js file both as an URL or as a context-relative resources (see http://ci.apache.org/projects/wicket/guide/6.x/guide/single.html#resources_5) On 17/06/2015 17:53, Tom Norton wrote: Our web site is only partially developed with wicket, so the the javascript file in question can't be retrieved using a package-based approach. Is there a way to add an absolute reference for a javascript plugin? Thanks, Tom On Tue, Jun 16, 2015 at 4:50 PM, Martin Grigorov mgrigo...@apache.org wrote: Hi, Yes, use: response.render(JavaScriptHeaderItem.forReference(new *JQueryPluginResourceReference*(YourScope.class, your-plugin.js))) Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Jun 16, 2015 at 11:40 PM, Tom Norton tomwnorton.mailing.li...@gmail.com wrote: We are in the process of upgrading from wicket 5 to wicket 6 and we are having trouble with some of our panels that load custom JQuery plugins. Because wicket 6 writes the script tags for child components before parent components, our components that use third party jquery plugins get wiped out when the wicket application adds the main jquery javascript. Is there a way to configure wicket to load jquery first, and then to load the individual jquery plugin javascript files afterwards? Thanks, Tom - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: up to date Wicket presentation?
Hi, sorry if I take part to this conversation only now, but I realized that I do have a presentation (in English) I used for a crush-course on Wicket 6. It doesn't cover every topic of the framework but it might help you. Here's the link: https://www.dropbox.com/s/e41qr6mwsnsabkh/Presentazione%20Wicket.odp?dl=0 On 12/06/2015 12:06, Ernesto Reinaldo Barreiro wrote: Dear Wicketeers, Does anyone has, and is willing to share, a recent (in English) presentation of Apache Wicket? I mean newer than http://www.slideshare.net/jbaruch/wicket-presentation-alphacsp-java-web-frameworks-playoff-2008 which is, by the way, a nice presentation :-) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: up to date Wicket presentation?
yes, at the end of the course everyone was in love with wicket :D On 15 Jun 2015 19:57, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Mon, Jun 15, 2015 at 4:52 PM, andrea del bene an.delb...@gmail.com wrote: a crush-course on Wicket 6. It doesn't cover every topic of the framework but it might help you. Crush: a burning desire to be with someone who you find very attractive and extremely special. I absolutely love a crush course for Wicket... Martijn - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Possible to add a new component to a page using IComponentResolver ?
You are right. I'm afraid you can not do what you want in Wicket 6 because up to this version autocomponents (i.e those who are added during markup parsing) are removed after rendering phase. That's why your link doesn't find its component. With Wicket 7 autocomponents are no more removed and your code works fine. Here I've created a quickstart with your code for Wicket 7: https://www.dropbox.com/s/2pua1utz5r35nde/TagWithLink.zip?dl=0 Hi Andrea, Hi, A nice example of a custom IComponentResolver can be found in WicketStuff with module JEE-Web-Integration: https://github.com/wicketstuff/core/wiki/JEE-Web-Integration. The code is here: https://github.com/wicketstuff/core/tree/master/jdk-1.7-parent/jee-web-parent/jee-web. Look at class JEEWebResolver to learn more about component resolvers. A chapter on this topic is in my TODO list :). Thanks for your reply but looking at the JEEWebResolver it seems that you're just writing out some markup but not trying to register a link / ILinkListener like I'm trying to do. Or did I miss something ? Cheers, Tobias - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Possible to add a new component to a page using IComponentResolver ?
Hi, A nice example of a custom IComponentResolver can be found in WicketStuff with module JEE-Web-Integration: https://github.com/wicketstuff/core/wiki/JEE-Web-Integration. The code is here: https://github.com/wicketstuff/core/tree/master/jdk-1.7-parent/jee-web-parent/jee-web. Look at class JEEWebResolver to learn more about component resolvers. A chapter on this topic is in my TODO list :). On 08/05/2015 10:41, Tobias Gierke wrote: Hi, I'm trying to use IComponentResolver to implement a custom tag that will render a panel with a link that when clicked will display some help text. I want to use a custom tag for this because I need to be able to programmatically validate up-front (during the build process) that there are no missing help texts (=unknown help text IDs) in the code base. Parsing XHTML to do so is obviously way easier than parsing the application's java sources so that's why I opted for the IComponentResolver approach. My component resolver: ---8--8--8--8--8--8--8--- @Override public Component resolve(MarkupContainer container, MarkupStream markupStream, ComponentTag tag) { if ( markupStream.getWicketNamespace().equalsIgnoreCase( tag.getNamespace() ) TAG_NAME.equalsIgnoreCase( tag.getName() ) ) { final String tagValue = tag.getAttribute(helpTextId); return new HelpTextTag( helpText.+container.getPage().getAutoIndex() , new HelpTextId( tagValue.trim() ) ); } return null; } ---8--8--8--8--8--8--8--- HelpTextTag is a very simple panel: ---8--8--8--8--8--8--- ?xml version=1.0 encoding=UTF-8? html xmlns=http://www.w3.org/1999/xhtml; xmlns:wicket=http://wicket.apache.org/; body wicket:panel div a wicket:id=helpTextLinkimg wicket:id=helpTextImg width=16 height=16 /Help/a /div /wicket:panel /body /html ---8--8--8--8--8--8--- public class HelpTextTag extends Panel { private final HelpTextId helpTextId; public HelpTextTag(String id,HelpTextId helpTextId) { super(id); this.helpTextId = helpTextId; } @Override protected void onInitialize() { super.onInitialize(); final LinkString l = new LinkString(helpTextLink) { @Override public void onClick() { setResponsePage( new HelpPage(helpTextId) ); } }; l.add( new Image(helpTextImg , new PackageResourceReference(img/help.png) ) ); add(l); } } ---8--8--8--8--8--8--8--- Most likely due to my lack of understanding how IComponentResolver really fits into the grand scheme of things :) , trying to click the link always fails with a Could not find component ... on page Exception ... which kind of makes sense since the HelpTextTag is not add()ed to the component hierarchy (at least not by me). Here's the markup generated by Wicket: ---8--8--8--8--8--8--8--- wicket:extend wicket:help wicketsource=com.voipfuture.voipmng.onlinehelp:HelpTextTagResolver.java:36 helptextid=test.pagewicket:panel!-- MARKUP FOR com.voipfuture.voipmng.onlinehelp.HelpTextTag BEGIN -- div a wicketsource=com.voipfuture.voipmng.onlinehelp:HelpTextTag.java:23 href=../page?2-1.ILinkListener-_wicket_child11-_wicket_extend12-_wicket_child67-_wicket_extend68-helpText.69-helpTextLink wicket:id=helpTextLink img width=16 height=16 wicketsource=com.voipfuture.voipmng.onlinehelp:HelpTextTag.java:31 src=../resource/org.apache.wicket.Application/img/help-ver-1375187674000.png wicket:id=helpTextImg /a Help /div !-- MARKUP FOR com.voipfuture.voipmng.onlinehelp.HelpTextTag END --/wicket:panel/wicket:help a wicketsource=com.vodecc.voipmng.boundary.wicket.onlinehelp:HelpTextsOverviewPage.java:20 href=../page?2-1.ILinkListener-someOtherLink wicket:id=someOtherLinkSome link/a /wicket:extend ---8--8--8--8--8--8--8--- Is it even possible to add a new Panel/component without it already being present in the component hierarchy ? I looked at the IComponentResolver implementations that ship with Wicket and they either just generate/rewrite existing markup or replace a component that has already been added to the page. Thanks, Tobias - 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
User guide now under Git repository
Hi folks, in the last days we ported the user guide into the official Wicket Git repository. We have added a new sub project named wicket-user-guide containing the source documents of the guide. Now the entire documentation can be generated running the command 'mvn clean package -P guide' on parent project or inside wicket-user-guide. In this way the guide is part of the Continuous Integration process and is automatically regenerated each time we commit a change. Last but not least, now contributors can use Git and the Github mirror to create pull requests for the guide. For more details see http://ci.apache.org/projects/wicket/guide/6.x/guide/contributing.html. Have fun! Andrea. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 7: Problem hiding form from AjaxSubmitLink
Done! thank you guys. On 14/04/2015 08:44, Martin Grigorov wrote: Hi, I think Sven's solution is more generic. Also it will be consistent with WICKET-5597 On Apr 13, 2015 5:20 PM, Sven Meier s...@meiers.net wrote: Well, then we should change the type attribute as well, i.e. from submit to button. Why not just use #setPreventDefault(true)? Because if JavaScript is disabled, the browser will still submit the form, without triggering the callback on the AjaxSubmitLink. Regards Sven Am 13.04.2015 um 18:01 schrieb andrea del bene: The case pointed out by Don is slightly different as the AjaxSubmitLink is attached to a input type=submit/ tag. Adding 'attributes.setPreventDefault(true);' in updateAttributes actually solves his problem. On 13/04/2015 14:32, Sven Meier wrote: Hi Andrea, since WICKET-5597 AjaxSubmitLink already changes the button to prevent default submitting of the form: tag.put(type, button); Have fun Sven Am 13.04.2015 um 14:19 schrieb Andrea Del Bene: Due to WICKET-5197 I think we should add to 'attributes.setPreventDefault(true);' to AjaxSubmitLink Hi, Please create a quickstart app and attach it to a ticket at JIRA. Thanks! On Apr 12, 2015 9:43 PM, Don Ferguson don.fergu...@gmail.com wrote: Dear Wicket Boffins, I have a Wicket 6 app that I’ve recently migrated to Wicket 7. In the app there is a form whose AjaxSubmitLink hides the form as part of the submit. In Wicket7, this causes a ListenerInvocationNotAllowedException to be thrown, since the component that submitted the form is no longer visible. What is the approved “wicket way” to do what I’m attempting? Thanks in advance. -Don Here’s a stripped down version of the code: JAVA: public class TestPage extends WebPage { public TestPage() { Form form = new Form(form); form.add(new AjaxSubmitLink(submit) { @Override protected void onSubmit(AjaxRequestTarget target, Form? form) { super.onSubmit(target, form); form.setVisible(false); target.add(form); } }); add(form.setOutputMarkupPlaceholderTag(true)); } } HTML: html xmlns=http://www.w3.org/1999/xhtml; xmlns:wicket= http://wicket.apache.org; body h3Test Form Submit Hides Form/h3 form wicket:id=form h4Form Element/h4 input type=submit wicket:id=submit value=Submit/ /form /body EXCEPTION THROWN ON SUBMIT: org.apache.wicket.core.request.handler.ListenerInvocationNotAllowedException: Component rejected interface invocationComponent: [Form [Component id = form]] Listener: [RequestListenerInterface name=IFormSubmitListener, method=public abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()] at org.apache.wicket.RequestListenerInterface.invoke( RequestListenerInterface.java:212) at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandle r.invokeListener(ListenerInterfaceRequestHandler.java:241) at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandle r.respond(ListenerInterfaceRequestHandler.java:234) … - 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 - 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: Wicket 7: Problem hiding form from AjaxSubmitLink
Due to WICKET-5197 I think we should add to 'attributes.setPreventDefault(true);' to AjaxSubmitLink Hi, Please create a quickstart app and attach it to a ticket at JIRA. Thanks! On Apr 12, 2015 9:43 PM, Don Ferguson don.fergu...@gmail.com wrote: Dear Wicket Boffins, I have a Wicket 6 app that I’ve recently migrated to Wicket 7. In the app there is a form whose AjaxSubmitLink hides the form as part of the submit. In Wicket7, this causes a ListenerInvocationNotAllowedException to be thrown, since the component that submitted the form is no longer visible. What is the approved “wicket way” to do what I’m attempting? Thanks in advance. -Don Here’s a stripped down version of the code: JAVA: public class TestPage extends WebPage { public TestPage() { Form form = new Form(form); form.add(new AjaxSubmitLink(submit) { @Override protected void onSubmit(AjaxRequestTarget target, Form? form) { super.onSubmit(target, form); form.setVisible(false); target.add(form); } }); add(form.setOutputMarkupPlaceholderTag(true)); } } HTML: html xmlns=http://www.w3.org/1999/xhtml; xmlns:wicket= http://wicket.apache.org; body h3Test Form Submit Hides Form/h3 form wicket:id=form h4Form Element/h4 input type=submit wicket:id=submit value=Submit/ /form /body EXCEPTION THROWN ON SUBMIT: org.apache.wicket.core.request.handler.ListenerInvocationNotAllowedException: Component rejected interface invocationComponent: [Form [Component id = form]] Listener: [RequestListenerInterface name=IFormSubmitListener, method=public abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()] at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:212) at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:241) at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:234) … - 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: Wicket 7: Problem hiding form from AjaxSubmitLink
The case pointed out by Don is slightly different as the AjaxSubmitLink is attached to a input type=submit/ tag. Adding 'attributes.setPreventDefault(true);' in updateAttributes actually solves his problem. On 13/04/2015 14:32, Sven Meier wrote: Hi Andrea, since WICKET-5597 AjaxSubmitLink already changes the button to prevent default submitting of the form: tag.put(type, button); Have fun Sven Am 13.04.2015 um 14:19 schrieb Andrea Del Bene: Due to WICKET-5197 I think we should add to 'attributes.setPreventDefault(true);' to AjaxSubmitLink Hi, Please create a quickstart app and attach it to a ticket at JIRA. Thanks! On Apr 12, 2015 9:43 PM, Don Ferguson don.fergu...@gmail.com wrote: Dear Wicket Boffins, I have a Wicket 6 app that I’ve recently migrated to Wicket 7. In the app there is a form whose AjaxSubmitLink hides the form as part of the submit. In Wicket7, this causes a ListenerInvocationNotAllowedException to be thrown, since the component that submitted the form is no longer visible. What is the approved “wicket way” to do what I’m attempting? Thanks in advance. -Don Here’s a stripped down version of the code: JAVA: public class TestPage extends WebPage { public TestPage() { Form form = new Form(form); form.add(new AjaxSubmitLink(submit) { @Override protected void onSubmit(AjaxRequestTarget target, Form? form) { super.onSubmit(target, form); form.setVisible(false); target.add(form); } }); add(form.setOutputMarkupPlaceholderTag(true)); } } HTML: html xmlns=http://www.w3.org/1999/xhtml; xmlns:wicket= http://wicket.apache.org; body h3Test Form Submit Hides Form/h3 form wicket:id=form h4Form Element/h4 input type=submit wicket:id=submit value=Submit/ /form /body EXCEPTION THROWN ON SUBMIT: org.apache.wicket.core.request.handler.ListenerInvocationNotAllowedException: Component rejected interface invocationComponent: [Form [Component id = form]] Listener: [RequestListenerInterface name=IFormSubmitListener, method=public abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()] at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:212) at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:241) at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:234) … - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ace Editor Wicket integration?
Unfortunately no :-/ Hi folks, has anybody already done a successful Wicket integration of the Ace code editor (https://github.com/ajaxorg/ace https://github.com/ajaxorg/ace) and is willing to share it (or at least some code snippets)? -Tom - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: PDF viewed in panel via ResourceReference works in 6.12 but not in 6.13
Just a small observation that might help. Move code from PdfViewer contructor to onInitialize. This makes URL generation safer although it doesn't explain why your code worked until 6.12.0. I guess it depends on the mount path of your page. Most probably it is /wicket/bookmarkable/... On Mar 14, 2015 7:37 PM, Bruce Lombardi brlom...@gmail.com wrote: Interesting, When I run your code I see that the url is as you say: ./wicket/resource/org.apache.wicket.Application/pdfProducer Whereas in my working code (wicket version 6.12) it is: ./resource/org.apache.wicket.Application/pdfProducer And in my non-working code (wicket versions 6.13 - 6.19) it is: ../resource/org.apache.wicket.Application/pdfProducer If I remove the first dot from the url with the debuggerthen run from there the pdf appears as it should. I wonder why they are different in the two projects and why I'm getting .. with later versions. I'm also wondering if there is another library that is somehow incompatible with later versions of Wicket. I think the only library we use that interacts with Wicket is wicket bootstrap - currently as below (but I've tried other version): dependency groupIdde.agilecoders.wicket/groupId artifactIdwicket-bootstrap-core/artifactId version0.9.8/version /dependency dependency groupIdde.agilecoders.wicket/groupId artifactIdwicket-bootstrap-extensions/artifactId version0.9.8/version /dependency I will add these dependencies to your quickstart and see if it makes a difference. Bruce
Re: PDF viewed in panel via ResourceReference works in 6.12 but not in 6.13
Good! It would be nice to understand what caused this change from 6.12.0 to 6.13.0 but this requires a quickstart to reproduce the specific problem. If you have the time and the chance to create such quickstart you can open an issue on JIRA. Thanks Andrea, Your small observation was important. After moving the code into the onInitialize method everything started working. The url produced is ./resource/org.apache.wicket.Application/pdfProducer and not . ./resource/org.apache.wicket.Application/pdfProducer. I also test the wicket-bootstrap theory, but that does not seem to be involved. I will use this fix. Since this works should I still open a JIRA issue? Thanks again, Bruce -Original Message- From: Andrea Del Bene [mailto:an.delb...@gmail.com] Sent: Sunday, March 15, 2015 10:00 AM To: users@wicket.apache.org Subject: Re: PDF viewed in panel via ResourceReference works in 6.12 but not in 6.13 Just a small observation that might help. Move code from PdfViewer contructor to onInitialize. This makes URL generation safer although it doesn't explain why your code worked until 6.12.0. I guess it depends on the mount path of your page. Most probably it is /wicket/bookmarkable/... On Mar 14, 2015 7:37 PM, Bruce Lombardi brlom...@gmail.com wrote: Interesting, When I run your code I see that the url is as you say: ./wicket/resource/org.apache.wicket.Application/pdfProducer Whereas in my working code (wicket version 6.12) it is: ./resource/org.apache.wicket.Application/pdfProducer And in my non-working code (wicket versions 6.13 - 6.19) it is: ../resource/org.apache.wicket.Application/pdfProducer If I remove the first dot from the url with the debuggerthen run from there the pdf appears as it should. I wonder why they are different in the two projects and why I'm getting .. with later versions. I'm also wondering if there is another library that is somehow incompatible with later versions of Wicket. I think the only library we use that interacts with Wicket is wicket bootstrap - currently as below (but I've tried other version): dependency groupIdde.agilecoders.wicket/groupId artifactIdwicket-bootstrap-core/artifactId version0.9.8/version /dependency dependency groupIdde.agilecoders.wicket/groupId artifactIdwicket-bootstrap-extensions/artifactId version0.9.8/version /dependency I will add these dependencies to your quickstart and see if it makes a difference. Bruce - 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: PDF viewed in panel via ResourceReference works in 6.12 but not in 6.13
Hi, I've created a quickstart based on your code but I can't reproduce the issue. I've shared it on Dropbox: https://www.dropbox.com/s/qmolvzvp9a0xplf/ResourceIssue.tar.gz?dl=0 The only thing I've noted is that your resource url doesn't have starting segment 'wicket', i.e my resource url is: ./wicket/resource/org.apache.wicket.Application/pdfProducer Maybe you have some custom setting for wicket segments ('wicket', 'bookmark', etc...)? The problem (which I think is a bug) is in the way the url is produced. The line String url = (String)RequestCycle.get().urlFor(resourceReference, null); Produces the url to use for the resource ref. In the non-working version it returns: ../resource/org.apache.wicket.Application/pdfProducer If I set a breakpoint just after this line and I manually remove the first dot in the string using the debugger to get: ./resource/org.apache.wicket.Application/pdfProducer and then let the code continue to run, my pdf appears correctly. The debug trace also shows the correct uri. 2015-03-13 17:59:30,292 DEBUG - ServletWebRequest - Calculating context relative path from: context path '', filterPrefix '', uri '/wicket/resource/org.apache.wicket.Application/pdfProducer' 2015-03-13 17:59:30,298 DEBUG - ServletWebRequest - Calculating context relative path from: context path '', filterPrefix '', uri '/wicket/resource/org.apache.wicket.Application/pdfProducer' 2015-03-13 17:59:30,301 DEBUG - ServletWebRequest - Calculating context relative path from: context path '', filterPrefix '', uri '/wicket/resource/org.apache.wicket.Application/pdfProducer' 2015-03-13 17:59:30,305 DEBUG - CompoundRequestMapper - One compatible mapper found for URL 'wicket/resource/org.apache.wicket.Application/pdfProducer' - 'Mapper: org.apache.wicket.core.request.mapper.ResourceReferenceMapper; Score: 1' Maybe someone knows how to fix this? I could strip the first dot as a workaround in the mean time. Bruce - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket roadmap
The most up-to-date version of the site is the one from Martijn who is leading the development. I think there are few things left to do to complete this task. I've opened a PR to solve a couple of small layout issues in two pages. Apart from this there are some TODO in the documentation page to ' integrate media objects' for book pictures and videos, but honestly I don't know exactly what this is about. IMHO we should also add a new header link for 'community' pages like friends projects and WicketStuff. new web design for https://wicket.apache.org I hope this will be ready for Wicket 7.0.0 ( https://github.com/dashorst/wicket-site, http://bitstorm.github.io/wicket-site/) @Martijn, @Andrea ? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicketstuff JavaDoc
Hi everybody, I've created a gh-pages branch to host javadoc for wicketstuff. It contains docs for 6.x and master branch. They are linked in the readme file of each respective branch. http://wicketstuff.org/core/javadoc6/apidocs/index.html http://wicketstuff.org/core/javadoc7/apidocs/index.html Have fun! @Martin. Can be CI configured to generate and automatically update the doc? Doing it manually it's not a big issue but if can make it automatic is of course better. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff REST-Annotations: error handling impossible?
That's a simple but yet very useful improvement! I will commit it ASAP. Thank you. Andrea. Hi everybody, We are using the Wicketstuff REST-Annotations and we are very happy with it. Thank you very much :-) We have a small thingy however for which I would like to propose a minor change in the code. It is about the fact that it is very hard, if not impossible, to customize error handling. I have created a Ticket in GitHub for it: https://github.com/wicketstuff/core/issues/384 Thanks and regards, Hans - 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: Wicketstuff REST-Annotations: error handling impossible?
Not at the moment. But it's a nice idea for future improvements :) Hello, have missed this useful component somehow Is there any way to get wsdl? and wadl? On Tue, Feb 24, 2015 at 4:20 PM, Hans Lesmeister hans.lesmeis...@lessy-software.de wrote: Hi Andrea, thank you for your quick response. Great to hear that the change will be committed :-) Regards, Hans -Ursprüngliche Nachricht- Von: andrea del bene [mailto:an.delb...@gmail.com] Gesendet: Dienstag, 24. Februar 2015 11:02 An: users@wicket.apache.org Betreff: Re: Wicketstuff REST-Annotations: error handling impossible? That's a simple but yet very useful improvement! I will commit it ASAP. Thank you. Andrea. Hi everybody, We are using the Wicketstuff REST-Annotations and we are very happy with it. Thank you very much :-) We have a small thingy however for which I would like to propose a minor change in the code. It is about the fact that it is very hard, if not impossible, to customize error handling. I have created a Ticket in GitHub for it: https://github.com/wicketstuff/core/issues/384 Thanks and regards, Hans - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: URL Encryption in detail
On 19/02/2015 11:28, lucast wrote: Dear forum, Reading the Apache Wicket Guide on URL Encryption in detail https://wicket.apache.org/guide/guide/security.html#security_4 , the section suggests that simply calling is not enough for url encryption at production level. Further down on that section, there is one recommendation of making the url encryption stronger: Is simply adding *getSecuritySettings().setCryptFactory(new KeyInSessionSunJceCryptFactory())*; line enough to make the URLs on my application better as suggested on URL Encryption in detail https://wicket.apache.org/guide/guide/security.html#security_4 ? My impression is that maybe it isn't since I understand KeyInSessionSunJceCryptFactory is the default CryptFactory for the application. Well no, the default one is CachingSunJceCryptFactory which does NOT generate a separate key for each user. On the contrary KeyInSessionSunJceCryptFactory creates a different key for each user (session). It uses a password-based algorithm to encrypt/decrypt urls which is secure enough for this purpose. In addition to this, CryptoMapper(IRequestMapper wrappedMapper, Application application) API Doc states that: For better security it is recommended to use CryptoMapper(IRequestMapper, IProvider) with a specific ICrypt implementation that generates a separate key for each user. KeyInSessionSunJceCryptFactory provides such an implementation that stores the key in the HTTP session. Does the above sentence mean that one ought to implement a CryptProvider class using KeyInSessionSunJceCryptFactory or something better/stronger ? Encryption and security are not my forte and at the same time I admit I am looking for an out-of-the-box solution where I can just simply carry on implementing the rest of my wicket app. Thanks in advance, Lucas -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/URL-Encryption-in-detail-tp4669640.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: URL Encryption in detail
On 19/02/2015 13:23, andrea del bene wrote: On 19/02/2015 11:28, lucast wrote: Dear forum, Reading the Apache Wicket Guide on URL Encryption in detail https://wicket.apache.org/guide/guide/security.html#security_4 , the section suggests that simply calling is not enough for url encryption at production level. Further down on that section, there is one recommendation of making the url encryption stronger: Is simply adding *getSecuritySettings().setCryptFactory(new KeyInSessionSunJceCryptFactory())*; line enough to make the URLs on my application better as suggested on URL Encryption in detail https://wicket.apache.org/guide/guide/security.html#security_4 ? My impression is that maybe it isn't since I understand KeyInSessionSunJceCryptFactory is the default CryptFactory for the application. Well no, the default one is CachingSunJceCryptFactory which does NOT generate a separate key for each user. On the contrary KeyInSessionSunJceCryptFactory creates a different key for each user (session). It uses a password-based algorithm to encrypt/decrypt urls which is secure enough for this purpose. Sorry, with Wicket 6.19.0 the default CryptFactory is actually KeyInSessionSunJceCryptFactory so you are ok with just : WicketApplication.init() { setRootRequestMapper(new CryptoMapper(getRootRequestMapper(), this)); } you might need to implement you own stronger CryptFactory only if you are not satisfied with password-based cypher. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: New committer - Sebastien Briquet
Welcome on board Sebastien! On 14 Feb 2015 11:20, Maxim Solodovnik solomax...@gmail.com wrote: Congratulations Sebastien! WBR, Maxim (from mobile, sorry for the typos) On Feb 14, 2015 4:11 PM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Congratulations! On Fri, Feb 13, 2015 at 11:38 PM, Francois Meillet francois.meil...@gmail.com wrote: Welcome Sébastien Thanks for your commitment ! François Le 13 févr. 2015 à 22:55, Tobias Soloschenko tobiassolosche...@googlemail.com a écrit : Congratulations!!! kind regards Tobias Am 13.02.2015 um 22:05 schrieb Zala Pierre GOUPIL goupilpie...@gmail.com: \o/ Bienvenue Sébastien ! Bravo et continue comme ça ! On Fri, Feb 13, 2015 at 10:02 PM, Martin Grigorov mgrigo...@apache.org wrote: The Project Management Committee (PMC) for Apache Wicket has asked Sebastien Briquet to become a committer and we are pleased to announce that he has accepted. Sebastien has been involved with Wicket for several years now by developing one of the most successful integrations with JavaScript libraries, namely Wicket jQuery UI https://github.com/sebfz1/wicket-jquery-ui, reporting bugs, contributing fixes and participating in discussions. Being a committer will enable him to help us even easier in the future. Please welcome Sebastien Briquet to our team! Bienvenue Sebastien! -- Si le sang ne coule pas assez chaud dans tes veines, je le répandrai sur le sable pour qu'il bouille au soleil. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Regards - Ernesto Reinaldo Barreiro
Article on JSP/JSF integration
Hi, for those you might be interested in this topic, I wrote an article on JavaLobby about WicketStuff module JEE Web Integration created by Tobias Soloschenko. http://java.dzone.com/articles/integrate-jspjsf-pages-wicket Andrea. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: @SpringBean annotation, no-arg constructor
Hi, it looks like more a Spring problem rather than a Wicket one. What's your full stacktrace? Hi, when injecting a bean via @SpringBean annotation into a Wicket page, this bean must provide a default constructor, otherwise I am receiving the error: java.lang.IllegalArgumentException: Superclass has no null constructors but no arguments were given Is there a solution to inject beans without no-arg constructors? thanks a lot, Chris - 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: Error building wicket-6.19.0 from src
Hi, how did you get the code ? did you download it or did you use the 6.19.0 branch? I've tested the source from distribution (http://www.apache.org/dyn/closer.cgi/wicket/6.19.0) and everything it's fine. These method are final since a long time... I get the following error when I try to compile the 6.19.0 source code: [ERROR] 7014: org.apache.wicket.feedback.FeedbackCollector: Method 'public java.util.List collect()' is now final [ERROR] 7014: org.apache.wicket.feedback.FeedbackCollector: Method 'public java.util.List collect(org.apache.wicket.feed back.IFeedbackMessageFilter)' is now final [ERROR] 7014: org.apache.wicket.feedback.FeedbackCollector: Method 'public org.apache.wicket.feedback.FeedbackCollector setIncludeSession(boolean)' is now final [ERROR] 7014: org.apache.wicket.feedback.FeedbackCollector: Method 'public org.apache.wicket.feedback.FeedbackCollector setRecursive(boolean)' is now final Any idea what could be causing this? Regards, Chris - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff gae-initializer-parent
hi, appengine has a quite confusing versioning policy. The last version supporting java 6 (hence not requiring servlet 3) is 1.8.1 so if you use this version or an earlier one you should be ok. Unfortunately l also don't use appengine as deployment environment so l can't help you more in detail. On 9 Feb 2015 09:09, Martin Grigorov mgrigo...@apache.org wrote: Any hosting/cloud provider with Java: - Amazon WS - OpenShift - Cloudbees - Rackspace - ... Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Feb 9, 2015 at 9:59 AM, Wicket und Cocoon hansheinrichbr...@yahoo.de wrote: what is a good place to upload a wicket application. Am 09.02.2015 um 08:18 schrieb Tobias Soloschenko: Hi again, I found a topic in which the implementation of Servlet 3.0 for Google AppEngine is requested by several users https://code.google.com/p/googleappengine/issues/detail?id=3091 kind regards Tobias Am 09.02.2015 um 07:46 schrieb Wicket und Cocoon hansheinrichbr...@yahoo.de: Hello Martin, i tried your gae-initializer-example but get the following error wnhem i try gae:run and ask localhost:8080: java.lang.NoSuchMethodError: javax.servlet.http.HttpServletRequest. isAsyncStarted()Z i use appengine-java-sdk-1.9.7 and your example under jdk 1.7 when i read the few google information about wicket and appengine i am not sure if it is a good idea to transfer wicket to appengine. Regards Heiner - 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
[ANNOUNCE] Apache Wicket 7.0.0-M5 Released
The Apache Wicket PMC is proud to announce Apache Wicket 7.0.0-M5! We have released another milestone release for Apache Wicket 7. We aim to finalize Wicket 7 over the coming months and request your help in testing the new major version. Caveats --- It is still a development version so expect API breaks to happen over the course of the coming milestone releases. Semantic versioning --- As we adopted semver Wicket 7 will be the first release since 6.0 where we are able to refactor the API. We will continue to use semver when we have made Wicket 7 final and maintain api compatibility between minor versions of Wicket 7. Requirements Wicket 7 requires the following: - Java 7 - Servlet 3 compatible container You can't mix wicket libraries from prior Wicket versions with Wicket 7. Migration guide --- As usual we have a migration guide available online for people migrating their applications to Wicket 7. We will continue to update the guide as development progresses. If you find something that is not in the guide, please update the guide, or let us know so we can update the guide. You can find the guide here:http://s.apache.org/wicket7migrate Using this release -- With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version7.0.0-M5/version /dependency Or download and build the distribution yourself, or use our convenience binary package * Source:http://www.apache.org/dyn/closer.cgi/wicket/7.0.0-M5 * Binary:http://www.apache.org/dyn/closer.cgi/wicket/7.0.0-M5/binaries The signatures for the source release artefacts: Signature for apache-wicket-7.0.0-M5.zip: -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools -https://gpgtools.org iEYEABECAAYFAlRTjfQACgkQJBX8W/xy/UW+TQCfZn81bkbmcrVEGjWY4rUA2sfy rJMAn2Ah/6X2M9Cf02hEMyb8JV+ZPaBa =xlUP -END PGP SIGNATURE- Signature for apache-wicket-7.0.0-M5.tar.gz: -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools -https://gpgtools.org iEYEABECAAYFAlRTjfQACgkQJBX8W/xy/UVGggCdFyCZATMis/829BmasZKgx28m uDEAn2eZhOrh8//AIYnkRYFLtWJnyx0F =kWVF -END PGP SIGNATURE- CHANGELOG for 7.0.0-M5: Release Notes - Wicket - Version 7.0.0-M5 ** Bug * [WICKET-5584] - DiskDataStore error * [WICKET-5747] - Wicket Ajax Click handling gets requeued in OnDomReady so fire out of order * [WICKET-5748] - StackOverflowError while trying to get the Markup of WicketHeadContainer * [WICKET-5751] - NullPointerException in IntHashMap * [WICKET-5752] - ReplacementResourceBundleReference should return the dependencies for the replacing resource ref * [WICKET-5759] - AjaxRequestAttributes extra parameters aren't properly handled in getCallbackFunction() * [WICKET-5770] - PageParametersEncoder should not decode parameters with no name * [WICKET-5772] - LoadableDetachableModel caches null value if load() fails, bug in getObject() {attached = true;} * [WICKET-5777] - Reload of page leads to WicketRuntimeException * [WICKET-5782] - Missing escaping in MultiFileUploadField.js - sort of XSS * [WICKET-5783] - Multiple events in AjaxEventBehavior with prefix 'on' * [WICKET-5784] - arraycopy with bad length in AbstractRequestLogger:172 * [WICKET-5793] - Request for static resource creating a session in 6.13.0+ * [WICKET-5800] - wicket:enclosure within FormComponentPanel causes exception related to dequeueing * [WICKET-5809] - URL IPv6 parsing * [WICKET-5811] - Infinite loop issue in PropertyValidator#createUnresolvablePropertyMessage(FormComponent) * [WICKET-5812] - AtmosphereBehavior wrongly sets Ajax base url to '.' * [WICKET-5817] - Wicket-JMX should depend on asm-util ** Improvement * [WICKET-4703] - StringResourceModel should provide an overridable getString(Component) method * [WICKET-5746] - Fire an event once all JS event listeners are registered * [WICKET-5753] - It is impossible to determine the form submitting component's inputName when AjaxFormSubmitBehavior is used * [WICKET-5754] - (String)ResourceModel's defaultValue could be an IModelString * [WICKET-5756] - Allow to use custom ciphers when using SunJceCrypt class * [WICKET-5758] - Portuguese translation * [WICKET-5760] - Add constructor (String, Serializable, String) to AttributeAppender * [WICKET-5774] - UrlRenderer should render full and absolute urls in their canonical form * [WICKET-5775] - Replace the session upon successful signin for better support for Session Fixation * [WICKET-5776] - Add information about the component when it fail
[ANNOUNCE] Apache Wicket 6.19.0 Released
The Apache Wicket PMC is proud to announce Apache Wicket 6.19.0! This is the nineteenth maintenance release of the Wicket 6.x series. This release brings 28 bug fixes and improvements. Starting with Wicket 6 we use semantic versioning for the future development of Wicket, and as such no API breaks are present in this release compared to 6.0.0. Git tag: release/wicket-6.19.0 New and noteworthy -- This release fixes 12 bugs and adds 16 improvements. - [WICKET-5756] - Allow to use custom ciphers when using SunJceCrypt class - [WICKET-5780] - Add a resource reference for ContextRelativeResource - [WICKET-5802] - HTML 5 Import New feature: - [WICKET-5771] - Ability to escape resource bundle messages added with wicket:message See the changelog added below for more detailed information concerning this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324069projectId=12310561 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12328934styleName=TextprojectId=12310561 Using this release -- With Apache Maven update your dependency to (and don't forget to update any other dependencies on Wicket projects to the same version): dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version6.19.0/version /dependency Or download and build the distribution yourself, or use our convenience binary package * Source:http://www.apache.org/dyn/closer.cgi/wicket/6.19.0 * Binary:http://www.apache.org/dyn/closer.cgi/wicket/6.19.0/binaries Upgrading from earlier versions --- If you upgrade from 6.y.z this release is a drop in replacement. If you come from a version prior to 6.0.0, please read our Wicket 6 migration guide found at * https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0 Have fun! — The Wicket team The signatures for the source release artefacts: Signature for apache-wicket-6.19.0.zip: -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools -https://gpgtools.org iEYEABECAAYFAlRTb2UACgkQJBX8W/xy/UW1egCg1LOkWMrnD+FJoHKjp7Gulyvm s+UAoMNN/mgMKo+p33h3vt4fnLTemLGT =RpfO -END PGP SIGNATURE- Signature for apache-wicket-6.19.0.tar.gz: -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools -https://gpgtools.org iEYEABECAAYFAlRTb2UACgkQJBX8W/xy/UVZcACguyKdrM0byfMp5IWqzwFMx5Lo i6UAn25gHcC0w8QWiNJXV7u99iTHssaP =+QQW -END PGP SIGNATURE- CHANGELOG for 6.19.0: ** Bug * [WICKET-5747] - Wicket Ajax Click handling gets requeued in OnDomReady so fire out of order * [WICKET-5752] - ReplacementResourceBundleReference should return the dependencies for the replacing resource ref * [WICKET-5755] - Restoring focus after Ajax replace no longer works in IE8 * [WICKET-5759] - AjaxRequestAttributes extra parameters aren't properly handled in getCallbackFunction() * [WICKET-5770] - PageParametersEncoder should not decode parameters with no name * [WICKET-5782] - Missing escaping in MultiFileUploadField.js - sort of XSS * [WICKET-5783] - Multiple events in AjaxEventBehavior with prefix 'on' * [WICKET-5784] - arraycopy with bad length in AbstractRequestLogger:172 * [WICKET-5793] - Request for static resource creating a session in 6.13.0+ * [WICKET-5809] - URL IPv6 parsing * [WICKET-5811] - Infinite loop issue in PropertyValidator#createUnresolvablePropertyMessage(FormComponent) * [WICKET-5812] - AtmosphereBehavior wrongly sets Ajax base url to '.' ** Improvement * [WICKET-4703] - StringResourceModel should provide an overridable getString(Component) method * [WICKET-5746] - Fire an event once all JS event listeners are registered * [WICKET-5753] - It is impossible to determine the form submitting component's inputName when AjaxFormSubmitBehavior is used * [WICKET-5754] - (String)ResourceModel's defaultValue could be an IModelString * [WICKET-5756] - Allow to use custom ciphers when using SunJceCrypt class * [WICKET-5758] - Portuguese translation * [WICKET-5760] - Add constructor (String, Serializable, String) to AttributeAppender * [WICKET-5775] - Replace the session upon successful signin for better support for Session Fixation * [WICKET-5776] - Add information about the component when it fail in detach phase * [WICKET-5778] - Pass the IModifiable to the IChangeListener in ModificationWatcher * [WICKET-5780] - Add a resource reference for ContextRelativeResource * [WICKET-5794] - Make DefaultExceptionMapper extensible * [WICKET-5797] - Convenience method to call setResponsePage with forward option * [WICKET-5799] - Add rel=prev/next in PagingNavigator.html * [WICKET-5802] - HTML Import * [WICKET-5806] - Wicket.Log
Re: swap panels from child element
Changing visibility is less complex and if the result looks good I would go for it. Hi, I would like to swap panels B and C when the user clicks on a certain div element in Subpanel Aa The Page consists of following panels: - Panel A Subpanel Aa - Panel B - Panel C How can I access the panels B and C and replace them or change their visibility from the WebMarkupContainer onEvent(AjaxRequestTarget target) method? Is it better to replace them or change their visibility? Subpanel Aa: … WebMarkupContainer div=new WebMarkupContainer(„item); div.setOutputMarkupId(true); div.add(new AjaxEventBehavior(onclick) { protected void onEvent(AjaxRequestTarget target) { } }); ... Thanks, Chris - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 6.19.0 release date?
Same for me. Some issues like WICKET-5808 needed more time as they turned out to be more complex and delicate. On 23/01/2015 10:32, Sebastien wrote: Hi, I also go for a new milestone/release-candidate before 7.0.0 final... Btw, for a release candidate, I think that the usual naming is -RCx, like 7.0.0-RC1 Best regards, Sebastien On Fri, Jan 23, 2015 at 10:18 AM, Tobias Soloschenko tobiassolosche...@googlemail.com wrote: Hi, mh I was thinking about if the two pull requests Wicket-5801 / Wicket-5819 will find their way into the Version 7 of Wicket - we should add another milestone to let Wicket Users test the new functionality first. In addition there is one task left for the spring integration to be finished and fit the spring 4.0 generic autowiring standard. Currently List is supported / Map, Set not - I provided the code to finish it in the Ticket Wicket-5808. What do you think about it? kind regards Tobias Am 23.01.2015 um 10:03 schrieb Martin Grigorov mgrigo...@apache.org: Fine by me! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Jan 23, 2015 at 10:59 AM, Martijn Dashorst martijn.dasho...@gmail.com wrote: I was thinking about a 7.0.0-CR1 (candidate for release)? The enabled/disabled link discussion triggered me a bit. And we would really like to have a go at checking if we find any issues with our applications. 7.0.0 final sh/could be the next release (we can discuss if that should be 2 or 4 weeks from now) Martijn On Thu, Jan 22, 2015 at 2:35 PM, Martin Grigorov mgrigo...@apache.org wrote: 6.19 only or 7.0.0 too ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Jan 22, 2015 at 3:21 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: I'll see if I can build a release this weekend (or tomorrow) Martijn On Thu, Jan 22, 2015 at 12:50 PM, Tom Götz t...@decoded.de wrote: Hi there, are there already considerations for a release date of 6.19.0? Cheers, -Tom - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How to solve this login problem?
I'm not sure, but maybe you need to use the WebSocket. After all, if you have to push an event from server to client I don't see many alternatives. Hi, I got my first problem where my colleagues can't help me anymore. Because I'm fairly new to Wicket, I don't know how to describe it properly, so here's the complete story: We have a login form inside a Wicket Panel, which shows up as a dialog. When the form is sent, the onSubmit method is called correctly and the user gets authenticated. That works fine. Now in my task I have to find an alternative method to login. I want to try a QR-Code and a related app for my Android Phone. The phone scans the code, solves the integrated challenge and sends it back to the panel. What I have done so far: 1) the login panel shows the QR-Code, which contains the Wicket-sessionID and a challenge 2) a smartphone app scans the code and solves the challenge 3) on Wicket side, I implemented a stateless WebResource, which will be contacted by the app to push the response 4) the resource has references to all open Wicket-Sessions, so I can get the correct session via ID from 1) 5) the resource hands the response to the login panel 5) the panel proofs the response Maybe you already guessed my problem: When I login normally, the onSubmit-method delivers the AjaxRequestTarget, which I need to close the dialog (/target.appendJavaScript($.deMailLayer.close();)/) With the QR-Code-login, I'm now somewhere in my panel, but I don't have this target. I can't get it with /RequestCycle.get().find(AjaxRequestTarget.class)/ either because there is no Request from the browser :-( How can I login my user (and force the browser to refresh if this is necessary)? If it helps: I'm using Wicket 6 and our session class extends /AbstractAuthenticatedWebSession/ - Seb PS: I answered to the mailing list registration, but got an error back, so I don't know if it worked or not. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/How-to-solve-this-login-problem-tp4668931.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: Wicket 7.0.4M - bug related to queueing and wicket:enclosure
Hi, now the snapshot should work. Andrea. On 05/01/2015 11:32, mscoon wrote: Hi Martin, I just tried it with 7.0.0-SNAPSHOT and I get the same exception. I have opened https://issues.apache.org/jira/browse/WICKET-5800 with details and a quickstart. Thanks Marios On Wed, Dec 24, 2014 at 12:33 PM, Martin Grigorov mgrigo...@apache.org wrote: - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Happy New Year!!!!
Thank you! I also wish you you a wonderful new year! Hello All, Happy New Year! Let all troubles stay in 2014 and upcoming year be full of love and happiness :) WBR, Maxim (from mobile, sorry for the typos) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page Expired
Hi, with Wicket 6.17.0 do still have this problem? Can you create a quickstart to reproduce this problem? Thank you. Dear all I wrote an openid provider web application with 6.14.0 (upgrade from 1.5.3 gradually) which enabled ssl and url encryption. Everything worked fine until I upgrade wicket to 6.18.0, I got page expired exception page and the url became plaintext after I redirect it to another page. Any suggestions? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: current page highlighting
Hi, the code looks correct. You should debug return line 'return getPage().getClass().equals(...' and see why the condition is always false. Hi all i am trying to create dynamic navigation links in which current page link should be highlighted but i am unable to get desired outcome. i am using listview to display my menu items but unable to highlight the current page link. please suggest necessary changes ListHeaderListItems is list of pojo item. my pojo has two fields label(String) and destPage(Class) My Mark-up: Thanks in advance - K -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/current-page-highlighting-tp4668902.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: Strange behavior of FormComponentBehavior
Hi Andreas, what is the type of the model object for flag component? I see that inside convertInput is a ImageImpl while inside onSubmit is ImageRef I'm experiencing the strangest behavior with a FormComponentPanel. My custom FormComponentPanel has the following method: @Override protected void convertInput() { CountryImpl c = new CountryImpl(countryId, name.getConvertedInput(), currency.getConvertedInput(), flag.getConvertedInput()); System.err.println(Setting converted input: + c + (identity: + System.identityHashCode(c) + )); setConvertedInput(c); } Upon form submission I get the following printout on System.err: Setting converted input: CountryImpl[id: 53b2c7a0986c5f4527783d16, name: Sweden, currency: SEK, flag: ImageImpl[id=543d4328e4b0524ccbf143f8, data.length=13452]] (identity: 1113118053) Which is exactly what I expect. Great. Now to the part I can't explain: In the Form that encloses this FormComponentPanel, I have the following code: ( @Override public void onSubmit() { Country country = countryPanel.getModelObject(); System.err.println(country from countryPanel.getModelObject(): + country + (identity: + System.identityHashCode(country) + )); ... } And upon submit I get the following output: country from countryPanel.getModelObject(): CountryImpl[id: 53b2c7a0986c5f4527783d16, name: Sweden, currency: SEK, flag: ImageRef[id: 543d4328e4b0524ccbf143f8]] (identity: 1025123013) As you can see, the countryPanel.getModelObject() does not match the object that I used in setConvertedInput! (By looking at the System.identityHashCode one can see that they are not the same object.) Why is this? This is how I've always done! Other (strange) observations: - If I change one of the text-fields (name or currency) it works as expected! I get the same object out from getModelObject as I give to setConvertedInput - If I instead of countryPanel.getModelObject() do countryPanel.getConvertedInput() I get the expected object. (In [1] however, it says I should use getModelObject() I've stepped through the Wicket form processing code but it's really complex and I can't determine where it goes wrong. I have other custom components (seemingly identical to the CountryPanel) that works as expected. Any suggestions on what may be the issue is welcome. (I would hook you up with a minimal test case if I could, but I can't reproduce this when writing from scratch. Some detail seems to evade me.) best regards, Andreas Lundblad [1] https://cwiki.apache.org/confluence/display/WICKET/Creating+Custom+FormComponentPanel%27s+to+build+valid+objects+using+Wicket%27s+Form+Validation+Logic - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Read JSON from ajax post
Hi. If you have to read json from request body have a look here: https://github.com/wicketstuff/core/blob/master/jdk-1.7-parent/wicketstuff-restannotations-parent/restannotations/src/main/java/org/wicketstuff/rest/utils/http/HttpUtils.java see method readStringFromRequest Hello all, I am having trouble in reading json from ajax call. I am trying to implement some component that has behavior that receive ajax requests. Component uses kendoUI and sends ajax request to my listener as post method with small json in body (for example {id:1}) but I am not able to read it in wicket. I am new to wicket, but I have tried to get it from requestCycle.getRequest().getPostParameters() and no luck. Can anyone help me? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Read-JSON-from-ajax-post-tp4668789.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: Should I use a (stateless) WebPage or a Resource to return a json response for an autocomplete component?
Hi, I suggest you to use a resource instead of an adapted stateless page. Wicketstuff has a module with special Wicket resources to implement REST api: https://github.com/wicketstuff/core/tree/master/jdk-1.7-parent/wicketstuff-restannotations-parent. Here you can find resources that already produce JSON in output. To configure them you might use a Wicket initializer: http://wicket.apache.org/guide/guide/single.html#advanced_3 Hi all, I am making an autocomplete component based on jquery-autocomplete. I have currently implemented the data source using a stateless web page which writes the json response. What I don't like about this is that it is a separate file/class from my autocomplete component. But I like that it's stateless. Could I achieve the same effect (statelessness) using a dynamic resource registered/created from within the autocomplete component? In other words I want the autocomplete component, upon creation, to register a resource that can be used to serve the autocomplete options. But I want the resource to be stateless and lightweight and the requests to return the autocomplete options should not have to go through the page that contains the autocomplete component. Furthermore, if I have the same autocomplete component twice in a page, the resource should be registered only once and server requests for both components. Is this possible? Can you provide some guidelines? Thanks Marios - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicke website makeover time?
I think the very first priority now is to decide which Github repository should be the official one for this task. I think this should be Martijn's repository merged with all the changes made by Chris. I don't know if Martijn agrees with me. In this days he should be very busy with the three presentations he will hold at the incoming Apache Con in Budapest. So maybe he won't be able to reply very soon. PS: thank you for having revamped this topic :)! Sorry, for the confusion - I realize now that I was referring to Chris J Lee's fork of Martijn's work. I cloned Chris J Lee's fork and ran Jekyll on it and looks very modern and sexy indeed. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicke website makeover time?
I think we haven't mentioned yet the nice work done by Chris J. Lee: https://github.com/chrisjlee/wicket-site This should be the last version of Martijn's initial work. Hi Martijn, Did you build that page via jekyll or from raw HTML? I'm thinking we could easily restructure the current jekyll content to output in that layout/style. I'm playing around with a new type of layout called 'landing' (for landing page - eg., like the home page) where things are laid out like your sample. Regards, Chris -Original Message- From: Guillaume Smet [mailto:guillaume.s...@gmail.com] Sent: Friday, 14 November 2014 11:50 PM To: users@wicket.apache.org Subject: Re: Wicke website makeover time? Hi, Personnally, I really liked what Martijn did here: http://people.apache.org/~dashorst/wicket-flat/ It's clean and has personnality. The only thing IMHO is that a one page design for this amount of information is perhaps a bit too much. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicke website makeover time?
One last useful reference is https://issues.apache.org/jira/browse/WICKET-3341. This is the official issue to discuss new site design. Personally I like very much https://issues.apache.org/jira/secure/attachment/12583195/wicket-flat-new-top.002.png which is a variation of the flat theme. I think we haven't mentioned yet the nice work done by Chris J. Lee: https://github.com/chrisjlee/wicket-site This should be the last version of Martijn's initial work. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: CircularDependencyException when upgrading from Wicket 6.9.0 to 6.10.0
It should be a bug: https://issues.apache.org/jira/browse/WICKET-5752 Hi there, I’m trying to upgrade some semi-legacy app to the current Wicket version. I discovered that I get a CircularDependencyException when upgrading from 6.9.0 to 6.10.0 without any code changes. I created a quickstart based on Wicket 6.10.0 that throws the exception when opening the home page (when changing to 6.9.0 everything is fine): https://dl.dropboxusercontent.com/u/236111/quickstart.zip The demo app uses some jquery(-ui) resource references and resource replacements. Could someone point me into the right direction maybe? Cheers, -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
Re: AjaxFormChoiceComponentUpdatingBehavior for custom CheckGroup and CheckGroupSelector
I haven't used this js library, but isn't enough to trigger a click event on checkboxes? Like: $('#'+checkbox.id).iCheck('check'); $('#'+checkbox.id).trigger(click); Dear Forum, Based on wicket examples, I built a custom CheckGroup with added CheckGroupSelector. I also want to add an AjaxFormChoiceComponentUpdatingBehavior() instance to the CheckGroup to update the items selected. And this is where the problem lies. I have extended CheckGroup class to make use of ICheck jquery plugin http://fronteed.com/iCheck/ . Because CheckGroupSelector is JavaScript sugar according to a previous post http://apache-wicket.1842946.n4.nabble.com/Wicket-FormTester-not-working-with-CheckGroupSelector-tp4668206p4668217.html (thanks for the reply, Andrea), I had to replace CheckGroupSelector and AbstractSelector class. For the custom AbstractSelector class, I replaced the CheckSelector.js to make use of the ICheck functions, $('#'+checkbox.id).iCheck('check'), $('#'+checkbox.id).iCheck('uncheck'), etc. The problem that I have now is that AjaxFormChoiceComponentUpdatingBehavior no longer picks the click event from the checkboxes. In order to resolve this problem, I am propagating the click event from inside CheckSelector.js using javascript code from this stackoverflow answer http://stackoverflow.com/a/2381862/158499 . But this still doesn't solve the problem. My question is, how can I get AjaxFormChoiceComponentUpdatingBehavior to pick up any event when I select/unselect any checkboxes from the custom Icheck solution? Failing that, how can I best create my own implementation of AjaxFormChoiceComponentUpdatingBehavior to know when a checkbox has been clicked? Sorry for the long post. Thanks, Lucas -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AjaxFormChoiceComponentUpdatingBehavior-for-custom-CheckGroup-and-CheckGroupSelector-tp4668281.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: Wicket FormTester not working with CheckGroupSelector.
Hi, CheckGroupSelector (and all the other subclasses of AbstractCheckSelector) is not a form component, as the exception says. It is more like a JavaScript sugar that implements the select/unselect all feature. Hence I'm afraid you can't test via Java code... Dear Forum, I'm implementing the CheckGroup example from wicket-examples http://www.wicket-library.com/wicket-examples-6.0.x/compref/wicket/bookmarkable/org.apache.wicket.examples.compref.CheckGroupPage;jsessionid=B179E71FA0687FABCC91FC1D8759085F?0 I have added a AjaxFormChoiceComponentUpdatingBehavior() instance to the CheckGroup to update the items selected. I got the idea from RadioChoice example page http://www.wicket-library.com/wicket-examples-6.0.x/compref/wicket/bookmarkable/org.apache.wicket.examples.compref.RadioChoicePage?3 The CheckGroup example makes use of a CheckGroupSelector and I am having problem testing this one with formTester. In the automated test, I am trying to run, I call to unselect all. However, I am getting an error message that says: *org.apache.wicket.WicketRuntimeException: Component with id: groupSelector is not a FormComponent* How can I set/unset this CheckGroupSelector? Thanks in advance, Lucas -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-FormTester-not-working-with-CheckGroupSelector-tp4668206.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: simple confirmation on button/link
you can also use behavior AbstractDefaultAjaxBehavior which has updateAjaxAttributes(AjaxRequestAttributes attributes), so you can share confirmation code among different components. Hi, On Thu, Oct 30, 2014 at 11:57 PM, Garret Wilson gar...@globalmentor.com wrote: Andrea, thanks for jolting my brain; I was a little sleepy this morning. I was using a subclass of AjaxLink that added confirmation JavaScript as I outlined below. My original HTML was: button wicket:id=foo type=submit The root of the problem is that Wicket kept turning that into: button wicket:id=foo type=button id=foo7 Thus even though I got a confirmation dialog, the FileUpload was never being populated because the form was never being submitted. It turns out that apparently I have to use a subclass of AjaxSubmitLink rather than AjaxLink if I want the form to actually be submitted, even though I specified type=submit in the HTML. So my immediate problem is solved. On a higher level, though, it means that I now have to go create a ConfirmationAjaxSubmitLink along with my ConfirmationAjaxLink. I would have thought/hoped that things like submission and confirmation were something that could be injected to various components using behaviors rather that subclassing all over the place. There is a way to provide a global #updateAjaxAttributes() that is called for each and every Ajax behavior: org.apache.wicket.ajax.AjaxRequestTarget.IListener#updateAjaxAttributes With https://git-wip-us.apache.org/repos/asf?p=wicket.git;a=commit;h=d1caec5e I've improved it so there is no need to cast it to AbstractDefaultAjaxBehavior in the application code. You can use AbstractDefaultAjaxBehavior#getComponent() to check whether you should contribute to the ajax attributes or nor. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: simple confirmation on button/link
You have to add it explicitly with the usual way. This is more desirable if you don't want to apply it to every Ajax behavior as you suggested. @Andrea: how would you share this behavior between ConfirmingAjaxLink and ConfirmingAjaxSubmitLink ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Oct 31, 2014 at 2:56 PM, Andrea Del Bene an.delb...@gmail.com wrote: you can also use behavior AbstractDefaultAjaxBehavior which has updateAjaxAttributes(AjaxRequestAttributes attributes), so you can share confirmation code among different components. Hi, - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: simple confirmation on button/link
You are suggesting something like we see in GlobalUpdateAjaxAttributesTest, right? What I was thinking of was a less powerful solution suited to decorate standard AJAX links only in few cases you might need confirmation. You have to refresh your knowledge about the related code. Or I should ... Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Oct 31, 2014 at 3:54 PM, Andrea Del Bene an.delb...@gmail.com wrote: You have to add it explicitly with the usual way. This is more desirable if you don't want to apply it to every Ajax behavior as you suggested. @Andrea: how would you share this behavior between ConfirmingAjaxLink and ConfirmingAjaxSubmitLink ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Oct 31, 2014 at 2:56 PM, Andrea Del Bene an.delb...@gmail.com wrote: you can also use behavior AbstractDefaultAjaxBehavior which has updateAjaxAttributes(AjaxRequestAttributes attributes), so you can share confirmation code among different components. Hi, - 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: simple confirmation on button/link
Probably there was a misunderstanding :). I saw Garret Wilson searching for a behavior to inject submission and confirmation into various components. I just pointed out that actually we have a special behavior for AJAX (AbstractDefaultAjaxBehavior) that can be used to factorize custom Ajax request attributes and apply them when needed instead of repeating code in various subclasses. Of course with this solution you have to manually add you custom behavior and is not powerful as an Ajax listener as you suggested. Unless you use a more powerful language than Java that provides something like Scala's Trait I don't see how you could implement your solution without re-implementing the standard Ajax links. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Oct 31, 2014 at 5:33 PM, Andrea Del Bene an.delb...@gmail.com wrote: - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: simple confirmation on button/link
On 30/10/14 17:57, Garret Wilson wrote: All, I've created a simple confirmation link based on Sven Meier's ConfirmationLink code https://cwiki.apache.org/confluence/x/X4U on Confluence. For the most part it works, but... ...but if I'm on an upload form, then an an Ajax link won't work because I need to actually submit the multipart information. Hi, not sure I've got your problem. Are you submitting a form using a Ajax link? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Unit testing RadioChoice with AjaxFormComponentUpdatingBehavior
On 30/10/14 21:08, Nick Pratt wrote: Wicket 6.17.0 I have a RadioChoice (in a Form) that has an attached AjaxFormComponentUpdatingBehavior. The onUpdate() method of the Behavior fires an event for other components on the page to update (change visibility depending on user selection in radio choice). Im trying to unit test it using: formTester.selectRadioChoice( propertyType, 2 ); I guess that's a typo :) or are you using a custom formTester? and then I'm trying to trigger the behavior to fire so that I can check that the various components are visible/invisible: Component component = baseTester.getComponentFromLastRenderedPage( form:propertyType ); for ( Behavior b : component.getBehaviors() ) { if ( b instanceof AjaxFormComponentUpdatingBehavior ) { baseTester.executeBehavior( (AbstractAjaxBehavior) b ); } } However, I'm running in to this when the behavior is executed: org.apache.wicket.core.request.handler.ListenerInvocationNotAllowedException: Behavior rejected interface invocation. Is it possible to unit test this specific behavior, and am I going about this the right way? I've verified that the application works as expected in a browser. BTW, multiple-choice component should use AjaxFormChoiceComponentUpdatingBehavior instead of AjaxFormComponentUpdatingBehavior. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Page Parameters logging
hi, maybe you can use a custom error page: Application.getApplicationSettings().setInternalErrorPage We have a secret parameter that we don't want to be logged in a stack trace or anything. Right now we're using a custom IRequestHandler to intercept the exception but I'm wondering if there's a more elegant way to do this. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Page-Parameters-logging-tp4668053.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: Page Parameters logging
Sorry. I've realized that maybe you need a more efficient strategy to hide your parameter. I think that using a custom request handler is the right way. you can override getExceptionMapperProvider in you application to return tour custom handler for exception. You can have a look at DefaultExceptionMapper to find some implementation hints. hi, maybe you can use a custom error page: Application.getApplicationSettings().setInternalErrorPage We have a secret parameter that we don't want to be logged in a stack trace or anything. Right now we're using a custom IRequestHandler to intercept the exception but I'm wondering if there's a more elegant way to do this. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Page-Parameters-logging-tp4668053.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: alternative solution for addOrReplace()?
Hi, could you post the code you use inside onConfigure to addOrReplace inner container? Maybe you could avoid detaching/attaching overriding method detachModels in your inner containers. Hi Paul, thanx for replying. Oh, I use Ajax very heavily in this case. Thats why I said: the panel works quite good for ajax rendering and refreshing use-cases Hmm... ok... I think I missed some details. I try to explain. My page contains two sections seperated from each other. A kind of data-entry and a kind of displaying the results. The section which displays the results is a quite complicated panel, having an RefreshingView for about 30 (I will name them) sub-panels. These sub-panels addOrReplace() an inner container while rendering itself. And the replacement depends on my model object type. So, my sub-panel class has a hugh knowledge about how to render the results. On entering some data on the data-entry section I refresh the whole panel in the display section with all its sub-panels using Ajax. And this works great. Some of the sub-panels also rerender/refresh own there own, by listening to events etc pepe. All this behaviours are working very well. The only disadvantage is, using addOrReplace(), I have a heavy detaching/attaching situation and a performance problem. So, the best solution for now would be, keeping my panel implementation as it is, but just having my models detached only once, not for iteration. And here I dont have any idea how to solve that... :-/ thanx and kind regards Patrick - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Atom newsfeed link
Have you tried mounting your resource? (next paragraph 15.10) Hello, I've followed this guide to create a Atom feed link with Wicket and Rome: http://wicket.apache.org/guide/guide/resources.html at paragraph 15.9 Custom resources. However when I use the link to the newsfeed in google feedburner http://feedburner.google.com, it does not recognize it and even web browsers, when opening the feed link, are actually redirected to the page containing the link, thus receiving HTML code, instead of the XML feed. How do I create a bookmarkable link to the custom resource itself instead of the page containing it? Here is the feed link: http://goo.gl/we1CG7 And my java code is just a copypaste of the tutorial linked above. Any help appreciated, thanks in advance. - 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: Make wicket aware of loaded javascript
Hi, maybe you are refreshing th dom via AJAX and you loose previously defined js functions. What components do you refresh when you add panel via AJAX? Hi, I have a javascript function already loaded when the first page loads. When adding a new Panel thru ajax I add target.appendJavascript afterwards but I get Exception evaluating javascript: ReferenceError: deselectAll is not defined. I know that the script is there. I must be missing something. Any pointers? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Make-wicket-aware-of-loaded-javascript-tp4667733.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