Re: E-Commerce and Open Source projects
thanks for the prompt response. I've taken the Thread to Stack Exchange : http://stackoverflow.com/questions/22705039/e-commerce-project-licensing - Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/E-Commerce-and-Open-Source-projects-tp4665137p4665167.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
AbstractFormValidator in Wizard
I have a problem with form validation within a wizard. The wizard is used for account setup which concludes in setting a password as the final step. Originally this wasn't inside a wizard, but a panel with an embedded form. As I was dealing with this panel, I added it to the wizard, disabling the form buttons. Now I had to add form validation again and used an AbstractFormValidator (see below). It usually works, but occasionally the form seems to be submitted multiple times although I clicked "Finish" only once. I rarely can reproduce it, but it happens to our users every now and then. Maybe someone can shed light on what I might be doing wrong. The method below is called in the constructor of the WizardStep, and just so you know, the form component "password2" has validators checking if the required number of letters, numbers, special characters etc. are fulfilled. private void addFormValidator(){ add(new AbstractFormValidator() { public FormComponent[] getDependentFormComponents() { try{ log.debug("{}:{}: Retrieving form coponents", uniqueId, midm); FormComponent passwd = (FormComponent) passwordPanel.getPasswordForm().get("password"); FormComponent passwd2 = (FormComponent) passwordPanel.getPasswordForm().get("password2"); log.debug("{}:{}: Found 2 form coponents", uniqueId, midm); return new FormComponent[] { passwd, passwd2 }; } catch (Exception e){ return null; } } public void validate(Form form) { try { log.debug("{}:{}: Before password change", uniqueId, midm); passwordPanel.changePassword(passwordPanel.getNewPassword(), null); log.debug("{}:{}: After password change", uniqueId, midm); if (!authenticated){ log.debug("{}:{}: Before authentication", uniqueId, midm); authenticateUser(); log.debug("{}:{}: After authentication", uniqueId, midm); } } catch (UnavailableDataSourceException e) { form.error("There was a database error changing your password, please try again later."); } catch (UpdatePasswordException e) { form.error("There was an error changing your password: " + e.getMessage()); } catch (PreviousPasswordException e) { form.error("The submitted password was previously used! Please choose a " + "different password"); } catch (ExpiredPasswordException e) { log.error("{}:{}: Unable to update password for user, reason: " + e.getMessage(), uniqueId, midm); form.error ("An internal error occurred while updating your password, the password was NOT changed!"); } catch (ServicePasswordIsMidasPasswordException e) { form.error("The submitted service password was your MIDAS password. " + "This is not allowed."); } catch (ErrorUserCreationException e) { log.error("{}:{}: Unable to update password for user, reason: " + e.getMessage(), uniqueId, midm); form.error ("An internal error occurred while updating your password, the password was NOT changed!"); } catch (PasswordChangedTodayException e) { form.error("Your password can only be changed once a day!"); } catch (PasswordExpirationUpdateException e) { log.error("{}:{}: Unable to update password for user, reason: " + e.getMessage(), uniqueId, midm); form.error ("An internal error occurred while updating your password, the password was NOT changed!"); } catch (Exception e) { log.error("{}:{}: Unable to update password for user, reason: " + e.getMessage(), uniqueId, midm); form.error ("An internal error occurred while updating your password, the password was NOT changed!"); } } }); } -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AbstractFormValidator-in-Wizard-tp4665164.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Netbeans and "Compile On Save"
Hi This is really the wrong list try netbeans users or their forum. However the success of this also depends on the container you are using. Thanks David On 27 March 2014 16:05, Brad Grier wrote: > I used to be able to make code changes in Netbeans, save and test the > results > immediately. For some time now, this "compile on save" functionality no > longer works unless I first log out of my web app. It seems the session is > invalid after the intermediate compile. I'm getting a NoClassDefFoundError > for the current page (ultimately originating out of > DefaultPageFactory.newPage line 65 in wicket 6.14). > > I've ignored the problem for awhile now but I'd like to get it resolved. If > I forget to sign out after save, I have to restart the entire application > to > continue. Has anyone seen this and found a workaround? I'm using Netbeans 8 > but the problem also existed in 7.4. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Netbeans-and-Compile-On-Save-tp4665159.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 > >
Variables Assigned to ModalWindow are not the same as in the Callback
Hi In a Component i create a ModalWindow. To this ModalWindow i add a Component/Page. In the Constructor i put an reference to an entity. when i use this reference in the callback of the Modal Window i got two diferent references. Can this be, bcause the reference in the modal window was serialized ? How can i find out why the serialization did not work ? AjaxLink ajaxButton = new AjaxLink(){ onClick(AjaxRequestTarget target){ MyEntity myEntity = ...; showModal(target,entity); } } public void showModal(AjaxRequestTarget target,MyEntity myEntity){ WindowClosedCallback windowClosedCallback = new WindowClosedCallback() { private static final long serialVersionUID = 1L; public void onClose(AjaxRequestTarget target) { // this reference myEntity.save(); MyEnclosingPanel.this.refresh(target); setResponsePage(MyEnclosingPanel.this.getPage()); } }; Panel panel = new MyPanel(myEntity) ModalWindow modalWindow = new ModalWindow(); modalWindow.setWindowClosedCallback(windowClosedCallback); modalWindow.show(panel, target); } -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Variables-Assigned-to-ModalWindow-are-not-the-same-as-in-the-Callback-tp4665161.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: One field enabled in a disabled container
Why not use what Tomas proposed with an IVisitor that visits all form components and enable/disable them? Look at forms with flair http://code.google.com/p/londonwicket/downloads/detail?name=LondonWicket-FormsWithFlair.pdf for inspiration. On Thu, Mar 27, 2014 at 5:21 PM, Entropy wrote: > Yeah, I considered that. Unfortunately the hierarchy is such that these > two > are in the middle and buried a bit in the HTML hierarchy. In a simpler > situation, that would've worked spendidly. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/One-field-enabled-in-a-disabled-container-tp4665156p4665160.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 > > -- Regards - Ernesto Reinaldo Barreiro
RE: One field enabled in a disabled container
Yeah, I considered that. Unfortunately the hierarchy is such that these two are in the middle and buried a bit in the HTML hierarchy. In a simpler situation, that would've worked spendidly. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/One-field-enabled-in-a-disabled-container-tp4665156p4665160.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
Netbeans and "Compile On Save"
I used to be able to make code changes in Netbeans, save and test the results immediately. For some time now, this "compile on save" functionality no longer works unless I first log out of my web app. It seems the session is invalid after the intermediate compile. I'm getting a NoClassDefFoundError for the current page (ultimately originating out of DefaultPageFactory.newPage line 65 in wicket 6.14). I've ignored the problem for awhile now but I'd like to get it resolved. If I forget to sign out after save, I have to restart the entire application to continue. Has anyone seen this and found a workaround? I'm using Netbeans 8 but the problem also existed in 7.4. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Netbeans-and-Compile-On-Save-tp4665159.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: One field enabled in a disabled container
Before committing to a - as you said wierd requirement - by breaking the form structure, I'd rather do the setEnabled() - dance but separate it into a special behavior attached to the form. So you have your requirement fulfilled while keeping the GUI code clean and readable. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/One-field-enabled-in-a-disabled-container-tp4665156p4665158.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: One field enabled in a disabled container
Maybe split this one form in two, one with these 2 fields and one with the rest. Depending on the state, you enable either all, just the one with the 2 fields or none. Best, Marvin Richter -Original Message- From: Entropy [mailto:blmulholl...@gmail.com] Sent: Thursday, March 27, 2014 4:38 PM To: users@wicket.apache.org Subject: One field enabled in a disabled container A wierd requirement was just handed to me. We have a form that gets enabled/disabled depending on business rules as normal. However, now I am being told to disable ALL BUT TWO fields in a particular state. Is my only option here to leave the form enabled and then disable EVERY other control explicitly like: form.get("A").setEnabled(true); form.get("B").setEnabled(true); form.get("C").setEnabled(true); form.get("D").setEnabled(true); [...etc] Or is there a way to disable the container, and spare specific fields? I suspect I'll have to do the former, but there's quite a few fields and I am hoping there's some wicket trick. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/One-field-enabled-in-a-disabled-container-tp4665156.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
One field enabled in a disabled container
A wierd requirement was just handed to me. We have a form that gets enabled/disabled depending on business rules as normal. However, now I am being told to disable ALL BUT TWO fields in a particular state. Is my only option here to leave the form enabled and then disable EVERY other control explicitly like: form.get("A").setEnabled(true); form.get("B").setEnabled(true); form.get("C").setEnabled(true); form.get("D").setEnabled(true); [...etc] Or is there a way to disable the container, and spare specific fields? I suspect I'll have to do the former, but there's quite a few fields and I am hoping there's some wicket trick. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/One-field-enabled-in-a-disabled-container-tp4665156.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Avoid calling Page.onInitialize if page constructor throws an exception
Hi, #onInitialize() is not called here with 6.14.0 and 6.15.0-SNAPSHOT. Regards Sven On 03/27/2014 03:30 PM, Robin Shine wrote: Hi All, We are glad to see that the issue WICKET-5387 (Page#onInitialize called after an exception in the constructor of Page) has been resolved in 6.13.0. However when I tried this version (and 6.14.0) with below code, the issue still exist: public class TestPage extends WebPage { public TestPage() { throw new RuntimeException("exception"); } @Override protected void onInitialize() { super.onInitialize(); System.out.println("onInitialize"); } } As you can see from above code, I intentionally throws an exception in TestPage constructor and hoping that onInitialize() method is not called when I visit that page. But the result is that "onInitialize" is still getting called in this case. Am I understanding WICKET-5387 incorrectly? And is there any approach to prevent onInitialize() from being called in case of a constructor exception? We want this as onInitialize() might rely on some params setup in the constructor, and calling onInitialize() will lead to other exceptions hiding exceptions thrown in constructor. Regards Robin - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Replace HTML Markup Dynamically
Thank you Martin! I can confirm this work around is working well in my application! Jered Myers On 03/27/2014 03:19 AM, Martin Grigorov wrote: https://issues.apache.org/jira/browse/WICKET-5545 As a workaround you can replace com.test.help.HelpPage#onInitialize() with com.test.help.HelpPage#onConfigure() Martin Grigorov Wicket Training and Consulting On Thu, Mar 27, 2014 at 11:03 AM, Martin Grigorov wrote: This is a regression from https://issues.apache.org/jira/browse/WICKET-5415 I'll debug it and create a ticket. Martin Grigorov Wicket Training and Consulting On Wed, Mar 26, 2014 at 7:58 PM, Jered Myers wrote: Martin, The problem appears to have begun in Wicket 6.13. I have confirmed the problem is not in 6.10, 6.11, and 6.12. I am attaching a quickstart, so all you need to do is change the Wicket version in the pom between 6.13 and 6.12 to see the difference. I will start going through Git and see if I can find the change in 6.13. Thanks for your help. Jered Myers On 03/25/2014 03:16 PM, Martin Grigorov wrote: Hi, Upgrade to 6.11, then to 6.12, 6.13 and see when it starts. Then we can check together the respective changelog/release notes. Martin Grigorov Wicket Training and Consulting On Tue, Mar 25, 2014 at 11:31 PM, Jered Myers wrote: We were running Wicket 6.10 with our application and after upgrading to Wicket 6.14 our help file system no longer works. The system would open a modal window and dynamically set the HTML file to use based on StringResourceModels. This allows us to set the name of the help file in a components properties file and use the same help modal window to display the help file. The problem now is that the entire page redirects to the help file instead of just the page in the modal window. Does anybody have any idea what might of changed or how I can fix this? Here is the key code in the ModalWindow's page: protected void onInitialize() { super.onInitialize(); String helpFileName = fileNameModel.getObject() + ".html"; // add the anchor tag if it exists if (anchorModel != null && !Strings.isEmpty(anchorModel. getObject())) { helpFileName += "#" + anchorModel.getObject(); } getRequestCycle().scheduleRequestHandlerAfterCurrent(new RedirectRequestHandler("docs/" + helpFileName)); } Thanks for your help! -- Jered Myers - 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
Avoid calling Page.onInitialize if page constructor throws an exception
Hi All, We are glad to see that the issue WICKET-5387 (Page#onInitialize called after an exception in the constructor of Page) has been resolved in 6.13.0. However when I tried this version (and 6.14.0) with below code, the issue still exist: public class TestPage extends WebPage { public TestPage() { throw new RuntimeException("exception"); } @Override protected void onInitialize() { super.onInitialize(); System.out.println("onInitialize"); } } As you can see from above code, I intentionally throws an exception in TestPage constructor and hoping that onInitialize() method is not called when I visit that page. But the result is that "onInitialize" is still getting called in this case. Am I understanding WICKET-5387 incorrectly? And is there any approach to prevent onInitialize() from being called in case of a constructor exception? We want this as onInitialize() might rely on some params setup in the constructor, and calling onInitialize() will lead to other exceptions hiding exceptions thrown in constructor. Regards Robin
Re: http://wicketinaction.com/ not reachable
Not a registration issue at least (Registration Expiration Date: 2015-01-10 00:00:00) On Thu, Mar 27, 2014 at 3:00 PM, Sebastien wrote: > Same from France. Did you renew the domain name ? :S > > > On Thu, Mar 27, 2014 at 2:56 PM, Richter, Marvin < > marvin.rich...@jestadigital.com> wrote: > >> I get the same message from the Hoster (Germany) >> >> >> -Original Message- >> From: grsm...@atlanticbb.net [mailto:grsm...@atlanticbb.net] >> Sent: Thursday, March 27, 2014 2:49 PM >> To: users@wicket.apache.org >> Subject: Re: http://wicketinaction.com/ not reachable >> >> I can get to in. Am in the United States. >> George >> >> -Original Message- >> From: Bert >> Sent: Thursday, March 27, 2014 8:44 AM >> To: users >> Subject: http://wicketinaction.com/ not reachable >> >> Hallo wicketeers, >> >> I can not currently reach the blog http://wicketinaction.com/ >> >> I get an error from the hoster bhosted.nl: >> >> De bHosted.nl server is benaderd met een domein dat niet bekend is op >> deze server. Om veiligheidsredenen wordt deze pagina ook getoond indien >> deze server benaderd wordt met alleen een IP adres. >> >> >> Is this just me? >> >> Bert >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >
Re: http://wicketinaction.com/ not reachable
Same from France. Did you renew the domain name ? :S On Thu, Mar 27, 2014 at 2:56 PM, Richter, Marvin < marvin.rich...@jestadigital.com> wrote: > I get the same message from the Hoster (Germany) > > > -Original Message- > From: grsm...@atlanticbb.net [mailto:grsm...@atlanticbb.net] > Sent: Thursday, March 27, 2014 2:49 PM > To: users@wicket.apache.org > Subject: Re: http://wicketinaction.com/ not reachable > > I can get to in. Am in the United States. > George > > -Original Message- > From: Bert > Sent: Thursday, March 27, 2014 8:44 AM > To: users > Subject: http://wicketinaction.com/ not reachable > > Hallo wicketeers, > > I can not currently reach the blog http://wicketinaction.com/ > > I get an error from the hoster bhosted.nl: > > De bHosted.nl server is benaderd met een domein dat niet bekend is op deze > server. Om veiligheidsredenen wordt deze pagina ook getoond indien deze > server benaderd wordt met alleen een IP adres. > > > Is this just me? > > Bert > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
RE: http://wicketinaction.com/ not reachable
I get the same message from the Hoster (Germany) -Original Message- From: grsm...@atlanticbb.net [mailto:grsm...@atlanticbb.net] Sent: Thursday, March 27, 2014 2:49 PM To: users@wicket.apache.org Subject: Re: http://wicketinaction.com/ not reachable I can get to in. Am in the United States. George -Original Message- From: Bert Sent: Thursday, March 27, 2014 8:44 AM To: users Subject: http://wicketinaction.com/ not reachable Hallo wicketeers, I can not currently reach the blog http://wicketinaction.com/ I get an error from the hoster bhosted.nl: De bHosted.nl server is benaderd met een domein dat niet bekend is op deze server. Om veiligheidsredenen wordt deze pagina ook getoond indien deze server benaderd wordt met alleen een IP adres. Is this just me? Bert - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: http://wicketinaction.com/ not reachable
I can get to in. Am in the United States. George -Original Message- From: Bert Sent: Thursday, March 27, 2014 8:44 AM To: users Subject: http://wicketinaction.com/ not reachable Hallo wicketeers, I can not currently reach the blog http://wicketinaction.com/ I get an error from the hoster bhosted.nl: De bHosted.nl server is benaderd met een domein dat niet bekend is op deze server. Om veiligheidsredenen wordt deze pagina ook getoond indien deze server benaderd wordt met alleen een IP adres. Is this just me? Bert - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
http://wicketinaction.com/ not reachable
Hallo wicketeers, I can not currently reach the blog http://wicketinaction.com/ I get an error from the hoster bhosted.nl: De bHosted.nl server is benaderd met een domein dat niet bekend is op deze server. Om veiligheidsredenen wordt deze pagina ook getoond indien deze server benaderd wordt met alleen een IP adres. Is this just me? Bert
Re: E-Commerce and Open Source projects
Hi Arjun, That's a good set of questions you have posted. However, I am thinking that due to the nature of the question, you might get more replies if you post it in a start-up related forum. I think Stackexchange (stackoverflow.com is part of it) have one. Alternatively, there are a couple of software start-up books written solely for software developers that might be able to shed more light on this. It might not be relevant to your question (in terms of licensing) but there are two books you might get better idea for pricing: Micro-ISV: From Vision to Reality and Start Small, Stay Small: A Developer's Guide to Launching a Startup. You can look them up on Amazon. I hope that helps. Kind regards, Lucas -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/E-Commerce-and-Open-Source-projects-tp4665137p4665146.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Need to refresh the page to see the errors on feedbackpanel.
Hi Martin, Thanks got it working. And thanks for the materials too. Regards, -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Need-to-refresh-the-page-to-see-the-errors-on-feedbackpanel-tp4665139p4665145.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Need to refresh the page to see the errors on feedbackpanel.
Yes, it helps! We see AjaxRequestTarget around so it is in Ajax context. If you need to show the feedback messages in Ajax request you need to do: target.add(feedbackPanel); Also you need to call: feedbackPanel.setOutputMarkupId(true) when you add the feedbackPanel to its parent. Read http://wicket.apache.org/guide/guide/ajax.html (and the guide as a whole). It will be useful ;) Martin Grigorov Wicket Training and Consulting On Thu, Mar 27, 2014 at 11:13 AM, chathuraka.waas wrote: > Hi Martin, > > i'm bit new to wicket and actually dont know what you mean by using ajax to > show messages. > > given below is my code for submit button if it helps. > > FMAjaxSubmitLink publishButton = new FMAjaxSubmitLink("Button") { > > private static final long serialVersionUID = 1L; > > @Override > public void submit(AjaxRequestTarget target, Form f) { > isDraft = false; > processSubmit(target, (PublishForm) form.getModelObject()); > } > > @Override > protected void onError(AjaxRequestTarget target, Form form) > { > setError("", null, target); > } > }; > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Need-to-refresh-the-page-to-see-the-errors-on-feedbackpanel-tp4665139p4665142.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Replace HTML Markup Dynamically
https://issues.apache.org/jira/browse/WICKET-5545 As a workaround you can replace com.test.help.HelpPage#onInitialize() with com.test.help.HelpPage#onConfigure() Martin Grigorov Wicket Training and Consulting On Thu, Mar 27, 2014 at 11:03 AM, Martin Grigorov wrote: > This is a regression from > https://issues.apache.org/jira/browse/WICKET-5415 > I'll debug it and create a ticket. > > Martin Grigorov > Wicket Training and Consulting > > > On Wed, Mar 26, 2014 at 7:58 PM, Jered Myers > wrote: > >> Martin, >> >> The problem appears to have begun in Wicket 6.13. I have confirmed the >> problem is not in 6.10, 6.11, and 6.12. I am attaching a quickstart, so >> all you need to do is change the Wicket version in the pom between 6.13 and >> 6.12 to see the difference. I will start going through Git and see if I >> can find the change in 6.13. Thanks for your help. >> >> Jered Myers >> >> >> On 03/25/2014 03:16 PM, Martin Grigorov wrote: >> >>> Hi, >>> >>> Upgrade to 6.11, then to 6.12, 6.13 and see when it starts. >>> Then we can check together the respective changelog/release notes. >>> >>> Martin Grigorov >>> Wicket Training and Consulting >>> >>> >>> On Tue, Mar 25, 2014 at 11:31 PM, Jered Myers >>> wrote: >>> >>> We were running Wicket 6.10 with our application and after upgrading to Wicket 6.14 our help file system no longer works. The system would open a modal window and dynamically set the HTML file to use based on StringResourceModels. This allows us to set the name of the help file in a components properties file and use the same help modal window to display the help file. The problem now is that the entire page redirects to the help file instead of just the page in the modal window. Does anybody have any idea what might of changed or how I can fix this? Here is the key code in the ModalWindow's page: protected void onInitialize() { super.onInitialize(); String helpFileName = fileNameModel.getObject() + ".html"; // add the anchor tag if it exists if (anchorModel != null && !Strings.isEmpty(anchorModel. getObject())) { helpFileName += "#" + anchorModel.getObject(); } getRequestCycle().scheduleRequestHandlerAfterCurrent(new RedirectRequestHandler("docs/" + helpFileName)); } Thanks for your help! -- Jered Myers >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> > >
Re: Need to refresh the page to see the errors on feedbackpanel.
Hi Martin, i'm bit new to wicket and actually dont know what you mean by using ajax to show messages. given below is my code for submit button if it helps. FMAjaxSubmitLink publishButton = new FMAjaxSubmitLink("Button") { private static final long serialVersionUID = 1L; @Override public void submit(AjaxRequestTarget target, Form f) { isDraft = false; processSubmit(target, (PublishForm) form.getModelObject()); } @Override protected void onError(AjaxRequestTarget target, Form form) { setError("", null, target); } }; -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Need-to-refresh-the-page-to-see-the-errors-on-feedbackpanel-tp4665139p4665142.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Need to refresh the page to see the errors on feedbackpanel.
Hi, This code looks OK. No need to set it visible explicitly. Do you use Ajax when you have feedback messages to show ? Martin Grigorov Wicket Training and Consulting On Thu, Mar 27, 2014 at 11:00 AM, chathuraka.waas wrote: > Hi, > > i'm trying to migrate my app to wicket 6.14 and find it difficult to show > the error messages in my feedback panel. > > i'm working on a project that has been for a long time so i'm not sure if > there might be code thats disabling the error messages. > > what i'm trying to do is add a feedback panel to my pages and show the > errors. but i can only see them after refreshing the page. > > heres my code and markup. > > this.add(new FeedbackPanel("feedback").setVisible(true)); > > > > what am i doing wrong here. > > Thanks in advance. > > Regards, > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Need-to-refresh-the-page-to-see-the-errors-on-feedbackpanel-tp4665139.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Replace HTML Markup Dynamically
This is a regression from https://issues.apache.org/jira/browse/WICKET-5415 I'll debug it and create a ticket. Martin Grigorov Wicket Training and Consulting On Wed, Mar 26, 2014 at 7:58 PM, Jered Myers wrote: > Martin, > > The problem appears to have begun in Wicket 6.13. I have confirmed the > problem is not in 6.10, 6.11, and 6.12. I am attaching a quickstart, so > all you need to do is change the Wicket version in the pom between 6.13 and > 6.12 to see the difference. I will start going through Git and see if I > can find the change in 6.13. Thanks for your help. > > Jered Myers > > > On 03/25/2014 03:16 PM, Martin Grigorov wrote: > >> Hi, >> >> Upgrade to 6.11, then to 6.12, 6.13 and see when it starts. >> Then we can check together the respective changelog/release notes. >> >> Martin Grigorov >> Wicket Training and Consulting >> >> >> On Tue, Mar 25, 2014 at 11:31 PM, Jered Myers >> wrote: >> >> We were running Wicket 6.10 with our application and after upgrading to >>> Wicket 6.14 our help file system no longer works. The system would open >>> a >>> modal window and dynamically set the HTML file to use based on >>> StringResourceModels. This allows us to set the name of the help file >>> in a >>> components properties file and use the same help modal window to display >>> the help file. The problem now is that the entire page redirects to the >>> help file instead of just the page in the modal window. Does anybody >>> have >>> any idea what might of changed or how I can fix this? >>> >>> Here is the key code in the ModalWindow's page: >>> >>> protected void onInitialize() >>> { >>> super.onInitialize(); >>> >>> String helpFileName = fileNameModel.getObject() + ".html"; >>> >>> // add the anchor tag if it exists >>> if (anchorModel != null && !Strings.isEmpty(anchorModel. >>> getObject())) >>> { >>> helpFileName += "#" + anchorModel.getObject(); >>> } >>> >>> getRequestCycle().scheduleRequestHandlerAfterCurrent(new >>> RedirectRequestHandler("docs/" + helpFileName)); >>> } >>> >>> Thanks for your help! >>> >>> -- >>> Jered Myers >>> >>> > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org >
Need to refresh the page to see the errors on feedbackpanel.
Hi, i'm trying to migrate my app to wicket 6.14 and find it difficult to show the error messages in my feedback panel. i'm working on a project that has been for a long time so i'm not sure if there might be code thats disabling the error messages. what i'm trying to do is add a feedback panel to my pages and show the errors. but i can only see them after refreshing the page. heres my code and markup. this.add(new FeedbackPanel("feedback").setVisible(true)); what am i doing wrong here. Thanks in advance. Regards, -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Need-to-refresh-the-page-to-see-the-errors-on-feedbackpanel-tp4665139.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: calling downloadLink.onClick() directly
Check the Wiki page I gave you. It uses target.appendJavaScript("location.href='"+ url + "';"); Martin Grigorov Wicket Training and Consulting On Wed, Mar 26, 2014 at 9:54 PM, eaglei22 wrote: > I am not familar on how to perform a redirect from AJAX. I tried: > > new RedirectPage(excelFile.getPath()); > > and, > > target.appendJavaScript("location.hash='excelFile.getPath()'"); > > Can you give me a simple example? > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/calling-downloadLink-onClick-directly-tp4665125p4665136.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 > >