Re: [Wicket-user] Reverting the constructor change of 2.0
c) as well, except I don't think it's that good idea to release a beta before that. It certainly ain't beta if we expect the code to change that significantly. So imho either call it alpha or release it afterwards we commit the changes. -Matej Eelco Hillenius wrote: Hi, It looks like the discussion around reverting the constructor change that we did for 2.0 has cooled down. This email is not a vote yet, but a summary of opinions so far[1]. Those of you Wicket committers who didn't have your say yet (Juergen, Frank, Gwyn, Janne, Jan, Ate), I consider that an OK for reverting. If not, please reply to the thread. Juergen, you have been working on 2.0 quite a bit. Can you please state your opinion, and can you tell us whether there are more functional differences between 1.3 and 2.0 other than the constructor change, Java 5 features, the attach/ detach change and improved models and validators?[2] I think so far we can safely say reverting is supported broadly. At least, of the people who reacted, most stated they actually preferred add over the new constructor, and those who were either neutral or had a slight preference for the new constructor would still support reverting as that would keep the momentum for the project going. So, it looks like this may happen. But we'll vote about that in a few days. Before we do that, we have to reach consensus on the package we'll vote on. We have some different - and strong - opinions[3] so we need to find a way to bridge that. Here are what I think the different opinions: a) focus on stabilizing 1.3 first, meanwhile keep supporting 2.0 (though only for bugfixes). 1.4 will be the release with backports of the currently missing 2.0 features, and 1.5 will be 1.4 + the Java 5 features (including generics). b) as a) but rather than developing 1.3 up to a final release, freeze asap (only fix bugs) and start on 1.4 c) put all backports except for the Java 5 features in 1.3 after the beta1 release (which we agreed upon doing this weekend). 1.4 will be for the Java 5 features, and the branch should be started as soon as 1.3 is feature complete. Maybe the most constructive way to gather opinions here is to first let people plainly state what they prefer before we enter discussion mode. So, please state what package you think is the best idea (or introduce d if you want), and why. Cheers, Eelco [1] http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9350505 http://www.nabble.com/Re%3A-IMPORTANT%3A-your-opinion-on-the-constructor-tf3359229.html#a9344068 [2] http://www.nabble.com/State-1.3--features-tf3376983.html [3] http://www.nabble.com/VOTE%3A-backporting-wicket-2.0-model-change-to-1.3-tf3364601.html http://www.nabble.com/roadmap-tf3366743.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Reverting the constructor change of 2.0
I didn't have much time in the recent to actually work on apps based on Wicket, neither 1.x not 2.x. Thus I have no experience wih either and no preference regarding the constructor change. I go with what the experts decide. In 2.x there two more changes which have not yet been backported into 1.3 - Localizer - markup loading based on fragments I don't thnk there is any magic involved in backporting both, it just needs some doing and extensive testing. Juergen On 3/10/07, Matej Knopp [EMAIL PROTECTED] wrote: c) as well, except I don't think it's that good idea to release a beta before that. It certainly ain't beta if we expect the code to change that significantly. So imho either call it alpha or release it afterwards we commit the changes. -Matej Eelco Hillenius wrote: Hi, It looks like the discussion around reverting the constructor change that we did for 2.0 has cooled down. This email is not a vote yet, but a summary of opinions so far[1]. Those of you Wicket committers who didn't have your say yet (Juergen, Frank, Gwyn, Janne, Jan, Ate), I consider that an OK for reverting. If not, please reply to the thread. Juergen, you have been working on 2.0 quite a bit. Can you please state your opinion, and can you tell us whether there are more functional differences between 1.3 and 2.0 other than the constructor change, Java 5 features, the attach/ detach change and improved models and validators?[2] I think so far we can safely say reverting is supported broadly. At least, of the people who reacted, most stated they actually preferred add over the new constructor, and those who were either neutral or had a slight preference for the new constructor would still support reverting as that would keep the momentum for the project going. So, it looks like this may happen. But we'll vote about that in a few days. Before we do that, we have to reach consensus on the package we'll vote on. We have some different - and strong - opinions[3] so we need to find a way to bridge that. Here are what I think the different opinions: a) focus on stabilizing 1.3 first, meanwhile keep supporting 2.0 (though only for bugfixes). 1.4 will be the release with backports of the currently missing 2.0 features, and 1.5 will be 1.4 + the Java 5 features (including generics). b) as a) but rather than developing 1.3 up to a final release, freeze asap (only fix bugs) and start on 1.4 c) put all backports except for the Java 5 features in 1.3 after the beta1 release (which we agreed upon doing this weekend). 1.4 will be for the Java 5 features, and the branch should be started as soon as 1.3 is feature complete. Maybe the most constructive way to gather opinions here is to first let people plainly state what they prefer before we enter discussion mode. So, please state what package you think is the best idea (or introduce d if you want), and why. Cheers, Eelco [1] http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9350505 http://www.nabble.com/Re%3A-IMPORTANT%3A-your-opinion-on-the-constructor-tf3359229.html#a9344068 [2] http://www.nabble.com/State-1.3--features-tf3376983.html [3] http://www.nabble.com/VOTE%3A-backporting-wicket-2.0-model-change-to-1.3-tf3364601.html http://www.nabble.com/roadmap-tf3366743.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Reverting the constructor change of 2.0
Hi I am not a committer so I can't really estimate the feasibility of the various scenarios, but I'd prefer C as it sounds like the fastest road to a stable release including generics. Cheers, Wilko Eelco Hillenius wrote: Hi, It looks like the discussion around reverting the constructor change that we did for 2.0 has cooled down. This email is not a vote yet, but a summary of opinions so far[1]. Those of you Wicket committers who didn't have your say yet (Juergen, Frank, Gwyn, Janne, Jan, Ate), I consider that an OK for reverting. If not, please reply to the thread. Juergen, you have been working on 2.0 quite a bit. Can you please state your opinion, and can you tell us whether there are more functional differences between 1.3 and 2.0 other than the constructor change, Java 5 features, the attach/ detach change and improved models and validators?[2] I think so far we can safely say reverting is supported broadly. At least, of the people who reacted, most stated they actually preferred add over the new constructor, and those who were either neutral or had a slight preference for the new constructor would still support reverting as that would keep the momentum for the project going. So, it looks like this may happen. But we'll vote about that in a few days. Before we do that, we have to reach consensus on the package we'll vote on. We have some different - and strong - opinions[3] so we need to find a way to bridge that. Here are what I think the different opinions: a) focus on stabilizing 1.3 first, meanwhile keep supporting 2.0 (though only for bugfixes). 1.4 will be the release with backports of the currently missing 2.0 features, and 1.5 will be 1.4 + the Java 5 features (including generics). b) as a) but rather than developing 1.3 up to a final release, freeze asap (only fix bugs) and start on 1.4 c) put all backports except for the Java 5 features in 1.3 after the beta1 release (which we agreed upon doing this weekend). 1.4 will be for the Java 5 features, and the branch should be started as soon as 1.3 is feature complete. Maybe the most constructive way to gather opinions here is to first let people plainly state what they prefer before we enter discussion mode. So, please state what package you think is the best idea (or introduce d if you want), and why. Cheers, Eelco [1] http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9350505 http://www.nabble.com/Re%3A-IMPORTANT%3A-your-opinion-on-the-constructor-tf3359229.html#a9344068 [2] http://www.nabble.com/State-1.3--features-tf3376983.html [3] http://www.nabble.com/VOTE%3A-backporting-wicket-2.0-model-change-to-1.3-tf3364601.html http://www.nabble.com/roadmap-tf3366743.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/Reverting-the-constructor-change-of-2.0-tf3380114.html#a9408760 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Reverting the constructor change of 2.0
Hello, as a purse user of Wicket 1.2, I would like to see option c) happen. I'm really looking forward on upgrading my current app to use some of the new features, and to do things more elegantly. Also, I'd like to see Generics support as soon as possible; IModel makes so much more sense with it, and I am sure it will help especially new people coming to Wicket. But most important to me is actually a stable release, for which I'll get bugfixes. That's why I'm still with 1.2. So, as soon as there'll be a 1.3 beta (with a stable around the corner) I'll going to start porting and providing feedback. I did so when switching another app from 1.1 to 1.2 and had a good experience with that (bugs I found in the beta were fixed withing hours - really cool!) So, I hope my opinion helps you in your decision making :) greetings, Rüdiger Eelco Hillenius schrieb: Hi, It looks like the discussion around reverting the constructor change that we did for 2.0 has cooled down. This email is not a vote yet, but a summary of opinions so far[1]. Those of you Wicket committers who didn't have your say yet (Juergen, Frank, Gwyn, Janne, Jan, Ate), I consider that an OK for reverting. If not, please reply to the thread. Juergen, you have been working on 2.0 quite a bit. Can you please state your opinion, and can you tell us whether there are more functional differences between 1.3 and 2.0 other than the constructor change, Java 5 features, the attach/ detach change and improved models and validators?[2] I think so far we can safely say reverting is supported broadly. At least, of the people who reacted, most stated they actually preferred add over the new constructor, and those who were either neutral or had a slight preference for the new constructor would still support reverting as that would keep the momentum for the project going. So, it looks like this may happen. But we'll vote about that in a few days. Before we do that, we have to reach consensus on the package we'll vote on. We have some different - and strong - opinions[3] so we need to find a way to bridge that. Here are what I think the different opinions: a) focus on stabilizing 1.3 first, meanwhile keep supporting 2.0 (though only for bugfixes). 1.4 will be the release with backports of the currently missing 2.0 features, and 1.5 will be 1.4 + the Java 5 features (including generics). b) as a) but rather than developing 1.3 up to a final release, freeze asap (only fix bugs) and start on 1.4 c) put all backports except for the Java 5 features in 1.3 after the beta1 release (which we agreed upon doing this weekend). 1.4 will be for the Java 5 features, and the branch should be started as soon as 1.3 is feature complete. Maybe the most constructive way to gather opinions here is to first let people plainly state what they prefer before we enter discussion mode. So, please state what package you think is the best idea (or introduce d if you want), and why. Cheers, Eelco [1] http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9350505 http://www.nabble.com/Re%3A-IMPORTANT%3A-your-opinion-on-the-constructor-tf3359229.html#a9344068 [2] http://www.nabble.com/State-1.3--features-tf3376983.html [3] http://www.nabble.com/VOTE%3A-backporting-wicket-2.0-model-change-to-1.3-tf3364601.html http://www.nabble.com/roadmap-tf3366743.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Question about DataGridView
Hi, - OK, I will red it clearly *[Wicket-user] Design questions: Use of controllers and wicket models * * *- there should be a method on Item like getIndex() ICellPopulator#populateItem(Item cellItem, String componentId, IModel rowModel) but it is cellItem it return index of column, not index of row when I call cellItem.getIndex(), it always return 1 (It is second column in my table) Am I misunderstand? - see how DataTable does, namely DataTable.newRowItem() i believe. Thank, I can do it now. Thank you again, Blackzabaha Igor Vaynberg wrote: On 3/9/07, *blackboy zabaha* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: - with the checkbox I can't get the list of selected row, I try to do DataGridView.getModelObject but it return null, so my question is how can I get list of model object in current page of DataGridView, it take IDataProvider rather than IModel, not like ListView, isn't it used for displaying only not for modifying in form because it does not hold any model and so can't update it's model? i have very recently described how to do this in this thread: *[Wicket-user] Design questions: Use of controllers and wicket models * - how can I get row index of each row, in ICellPopulator#populateItem(Item cellItem, String componentId, IModel rowModel), both cellItem rowModel seem to contain no detail of row index. there should be a method on Item like getIndex() - how to dynamic change style of each row to class=odd/class=even up to row index in DataGridView. see how DataTable does, namely DataTable.newRowItem() i believe. -igor Thank you, Blackzabaha The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] AJAX validation
Jean-Baptiste Quenot schreef: * Arnout Engelen: So far it seems either Apache2, mod_caucho or Resin (2.1.16) is eating the POST body parameters. Has anyone ever seen something like this? Any idea where to look? Is POST followed by a redirect? Yes, the response to the POST is a redirect (http 301 moved permanently). If yes, is the URL missing a trailing slash? Do you mean the URL to which the POST request is sent or the one to which the user is redirected? The POST request goes to 'https://host/contextname?wicket:interface (etc) The redirect redirects to 'https://host/contextname/?wicket:interface (etc) What Wicket version are you using? 1.2.4 - we had some problems with 1.2.5 that didn't appear in 1.2.4. Kind regards, Arnout - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Instructions for using WICKET-126
Currently my development environment is downright ugly when it comes the edit - test changes cycle. I'm using: Maven Jetty plugin Intellij Idea As it currently stands, here's my cycle: 1. Make a change (doesn't matter if it's to a template or page class) 2. Wait for the entire application to redeploy - at least this happens automatically 3. Go back to my browser and click refresh; get a Page out of date error or something like that; I forget as I'm not sitting in front of it right now. 4. Click Go to home page 5. I'm forced to log in again 6. Finally, navigate through my application to get to back to place where I can see the change I made. Wash.Rinse.Repeat. A thousand times a day. Clearly, I'm doing something wrong. I have the configuration:development parameter set in my web.xml so if I disable automatic redeployment in Jetty, I can push my template changes out and see them almost immediately, however I make far more changes to my backing classes than I do to the templates themselves so I'd rather keep the Jetty auto-redeploy on. So first, is there something I should be doing differently to make this cycle a little shorter. When I was using Tomcat and a different presentation framework, sessions persisted across auto-redeployments so I could at least avoid having to log back in and navigate back to where I was each time. It's not much of an improvement but it's something. Can the same thing be done with Jetty/Wicket? Tomcat/Wicket? Second, I ran across the JIRA issue, WICKET-126: https://issues.apache.org/jira/browse/WICKET-126 This seems to describe some changes in the 1.3 base that would enable much easier hot-redeployment of classes. The discussion in the issue went back and forth, but it's a little hard to tell what form this functionality took int he end and how to use it. Are there any instructions outside that issue on its use? Do I need to check out the 1.3 code from Subversion or is it available from the wicketstuff.org maven respoitory (wha I'm currently using for 1.3 SNAPSHOTS)? I'm sure many of you have your development environments setup to avoid a prolonged change review cycle. I'd love to hear any tips you have. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Instructions for using WICKET-126
Not using IDEA I can only comment on the Java stuff. Wicket doesn't impose any special thing on the server and runtime environment. Therefore hotswap should be functioning. My experience with Eclipse is that running the application in debug mode allows hotswap to occur, and typically doesn't require a redeploy. I think this is available for IDEA as well (run your jetty using a debugger). On eclipse my mantra for the day is: - start server in debug mode from within eclipse - modify template or Java code (only inside methods, no structural changes) - see change immediately When a structural change was made, the hotswap will complain and you have to restart the server. From what I remember of using IDEA is that you also can run the app server in debug mode, and have it pick up changes in class files without redeploy. Read more here (possibly outdated but should give you ideas): http://jetty.mortbay.org/jetty5/faq/faq_s_950-IDEs_t_IntelliJ.html Martijn On 3/10/07, Matt Welch [EMAIL PROTECTED] wrote: Currently my development environment is downright ugly when it comes the edit - test changes cycle. I'm using: Maven Jetty plugin Intellij Idea As it currently stands, here's my cycle: Make a change (doesn't matter if it's to a template or page class) Wait for the entire application to redeploy - at least this happens automatically Go back to my browser and click refresh; get a Page out of date error or something like that; I forget as I'm not sitting in front of it right now. Click Go to home page I'm forced to log in again Finally, navigate through my application to get to back to place where I can see the change I made. Wash.Rinse.Repeat. A thousand times a day. Clearly, I'm doing something wrong. I have the configuration:development parameter set in my web.xml so if I disable automatic redeployment in Jetty, I can push my template changes out and see them almost immediately, however I make far more changes to my backing classes than I do to the templates themselves so I'd rather keep the Jetty auto-redeploy on. So first, is there something I should be doing differently to make this cycle a little shorter. When I was using Tomcat and a different presentation framework, sessions persisted across auto-redeployments so I could at least avoid having to log back in and navigate back to where I was each time. It's not much of an improvement but it's something. Can the same thing be done with Jetty/Wicket? Tomcat/Wicket? Second, I ran across the JIRA issue, WICKET-126: https://issues.apache.org/jira/browse/WICKET-126 This seems to describe some changes in the 1.3 base that would enable much easier hot-redeployment of classes. The discussion in the issue went back and forth, but it's a little hard to tell what form this functionality took int he end and how to use it. Are there any instructions outside that issue on its use? Do I need to check out the 1.3 code from Subversion or is it available from the wicketstuff.org maven respoitory (wha I'm currently using for 1.3 SNAPSHOTS)? I'm sure many of you have your development environments setup to avoid a prolonged change review cycle. I'd love to hear any tips you have. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Instructions for using WICKET-126
Second, I ran across the JIRA issue, WICKET-126: https://issues.apache.org/jira/browse/WICKET-126 This seems to describe some changes in the 1.3 base that would enable much easier hot-redeployment of classes. The discussion in the issue went back and forth, but it's a little hard to tell what form this functionality took int he end and how to use it. Are there any instructions outside that issue on its use? Do I need to check out the 1.3 code from Subversion or is it available from the wicketstuff.org maven respoitory (wha I'm currently using for 1.3 SNAPSHOTS)? It's all in there (1.3) so start using it today. YMMV though, but you already read that from the comments. So, play with it, so how it works out for you, and if you have issues, please share them here. Eelco - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] AJAX validation
this bug has been fixed in 1.2.5. what problems did you have in 1.2.5? most of them have been fixed and you can build the branch yourself until we release 1.2.6 -igor On 3/10/07, Arnout Engelen [EMAIL PROTECTED] wrote: Jean-Baptiste Quenot schreef: * Arnout Engelen: So far it seems either Apache2, mod_caucho or Resin (2.1.16) is eating the POST body parameters. Has anyone ever seen something like this? Any idea where to look? Is POST followed by a redirect? Yes, the response to the POST is a redirect (http 301 moved permanently). If yes, is the URL missing a trailing slash? Do you mean the URL to which the POST request is sent or the one to which the user is redirected? The POST request goes to 'https://host/contextname?wicket:interface (etc) The redirect redirects to 'https://host/contextname/?wicket:interface(etc) What Wicket version are you using? 1.2.4 - we had some problems with 1.2.5 that didn't appear in 1.2.4. Kind regards, Arnout - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] What's the best way of doing menus in Wicket?
The nice part about wicket is that it does not limit your presentation skills. Regarding menu, the best menu for me by now is a jQuery plugin wrote by Jonathan Sharp: http://jdsharp.us/code/jQuery/plugins/jdMenu . It uses a simple ul-li markup, supports unlimited levels and is completely unobtrusive. It can be used to create both: static dynamic menus with wicket. Generally speaking, wicket jQuery fits perfectly together for completing any task.. Thomas R. Corbin-2 wrote: We need a menu bar across the top of our pages, with pull down menus. We used to use this stuff: http://struts-menu.sf.net but I'm not sure how to integrate it, since it seems to rely on jsp tags. Thanks. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- View this message in context: http://www.nabble.com/What%27s-the-best-way-of-doing-menus-in-Wicket--tf3366440.html#a9413904 Sent from the Wicket - User mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Instructions for using WICKET-126
* Matt Welch: Hello Matt, Second, I ran across the JIRA issue, WICKET-126: This seems to describe some changes in the 1.3 base that would enable much easier hot-redeployment of classes. That's right, with this new feature you don't need to restart your webapp in most cases. The discussion in the issue went back and forth, but it's a little hard to tell what form this functionality took int he end and how to use it. Are there any instructions outside that issue on its use? Yes, please have a look at the Javadoc of wicket.protocol.http.ReloadingWicketFilter Do I need to check out the 1.3 code from Subversion or is it available from the wicketstuff.org maven respoitory (wha I'm currently using for 1.3 SNAPSHOTS)? You can do both. Your feedback on the reloading feature will be appreciated. Thanks in advance, -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Property file substitution
Is it possible to substitute properties into other properties? I tried the
Ant-like syntax:
Page1.properties:
my.label=My homepage
my.other.label=${my.label} is neat.
Is there a syntax which would render my.other.label as 'My homepage is
neat.'?
--
View this message in context:
http://www.nabble.com/Property-file-substitution-tf3382305.html#a9414382
Sent from the Wicket - User mailing list archive at Nabble.com.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Instructions for using WICKET-126
Thanks for all of the information and links. I'll be diving into this on Monday and I'll reply here with my results. On 3/10/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote: * Matt Welch: Hello Matt, Second, I ran across the JIRA issue, WICKET-126: This seems to describe some changes in the 1.3 base that would enable much easier hot-redeployment of classes. That's right, with this new feature you don't need to restart your webapp in most cases. The discussion in the issue went back and forth, but it's a little hard to tell what form this functionality took int he end and how to use it. Are there any instructions outside that issue on its use? Yes, please have a look at the Javadoc of wicket.protocol.http.ReloadingWicketFilter Do I need to check out the 1.3 code from Subversion or is it available from the wicketstuff.org maven respoitory (wha I'm currently using for 1.3 SNAPSHOTS)? You can do both. Your feedback on the reloading feature will be appreciated. Thanks in advance, -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Reverting the constructor change of 2.0
On 10/03/07, Eelco Hillenius [EMAIL PROTECTED] wrote: a) focus on stabilizing 1.3 first, meanwhile keep supporting 2.0 (though only for bugfixes). 1.4 will be the release with backports of the currently missing 2.0 features, and 1.5 will be 1.4 + the Java 5 features (including generics). b) as a) but rather than developing 1.3 up to a final release, freeze asap (only fix bugs) and start on 1.4 c) put all backports except for the Java 5 features in 1.3 after the beta1 release (which we agreed upon doing this weekend). 1.4 will be for the Java 5 features, and the branch should be started as soon as 1.3 is feature complete. Hi, I've kept quiet, as I've not had a chance to actually get into 2.0, so have no personal view on rollback, but I'm certainly not going to go against the experiences of the committers who do have to deal with the multiple branches. My preferences would be (c), for the same reasons you state in your other email. Regarding the beta release, I think we must do the release ASAP, if for no other reason than to work through the stages of an Apache release, although I'm not sure what the best designation is - personally I'd consider calling it a checkpoint release, but that's another matter! /Gwyn - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Property file substitution
Take a look at StringResourceModel. It should do what you want.
On 3/10/07, Jonathan Cone [EMAIL PROTECTED] wrote:
Is it possible to substitute properties into other properties? I tried the
Ant-like syntax:
Page1.properties:
my.label=My homepage
my.other.label=${my.label} is neat.
Is there a syntax which would render my.other.label as 'My homepage is
neat.'?
--
View this message in context:
http://www.nabble.com/Property-file-substitution-tf3382305.html#a9414382
Sent from the Wicket - User mailing list archive at Nabble.com.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Nick Heudecker
Professional Wicket Training Consulting
http://www.systemmobile.com
Eventful - Intelligent Event Management
http://www.eventfulhq.com
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Property file substitution
I don't think we support that. Feel free to open a feature request,
though personally, while I see the fun factor, I don't think it is
something we can't live about. So, please provide a patch if you care
about such a feature :)
Eelco
On 3/10/07, Jonathan Cone [EMAIL PROTECTED] wrote:
Is it possible to substitute properties into other properties? I tried the
Ant-like syntax:
Page1.properties:
my.label=My homepage
my.other.label=${my.label} is neat.
Is there a syntax which would render my.other.label as 'My homepage is
neat.'?
--
View this message in context:
http://www.nabble.com/Property-file-substitution-tf3382305.html#a9414382
Sent from the Wicket - User mailing list archive at Nabble.com.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Property file substitution
Oops. I didn't read his email very closely.
On 3/11/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
I don't think we support that. Feel free to open a feature request,
though personally, while I see the fun factor, I don't think it is
something we can't live about. So, please provide a patch if you care
about such a feature :)
Eelco
On 3/10/07, Jonathan Cone [EMAIL PROTECTED] wrote:
Is it possible to substitute properties into other properties? I tried
the
Ant-like syntax:
Page1.properties:
my.label=My homepage
my.other.label=${my.label} is neat.
Is there a syntax which would render my.other.label as 'My homepage is
neat.'?
--
View this message in context:
http://www.nabble.com/Property-file-substitution-tf3382305.html#a9414382
Sent from the Wicket - User mailing list archive at Nabble.com.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Nick Heudecker
Professional Wicket Training Consulting
http://www.systemmobile.com
Eventful - Intelligent Event Management
http://www.eventfulhq.com
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
