Cannot add InputHintFormBehavior to a form element
Hi, i'm trying to migrate my application from Wicket 1.4 to 6.13 and getting a compilation error when trying to add a InputHintFormBehavior to a form element. private final Form form = new Form(); form.add(new InputHintFormBehavior(component.getMarkupId())); how this is achieved in wicket 6. Thanks in advance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Cannot-add-InputHintFormBehavior-to-a-form-element-tp4663928.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: Cannot add InputHintFormBehavior to a form element
Hi, Showing us the error would help. InputHintFormBehavior is not from Wicket distro. It is your own class, or from a third party library. Martin Grigorov Wicket Training and Consulting On Fri, Jan 24, 2014 at 10:12 AM, chathuraka.waas chathuraka.w...@gmail.com wrote: Hi, i'm trying to migrate my application from Wicket 1.4 to 6.13 and getting a compilation error when trying to add a InputHintFormBehavior to a form element. private final Form form = new Form(); form.add(new InputHintFormBehavior(component.getMarkupId())); how this is achieved in wicket 6. Thanks in advance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Cannot-add-InputHintFormBehavior-to-a-form-element-tp4663928.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
Cannot add InputHintFormBehavior to a form element
Hi, got the issue fixed. it was due to a error in my own class. thanks for the reply. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Cannot-add-InputHintFormBehavior-to-a-form-element-tp4663928p4663931.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
timing for Wicket 7?
Hi, What's the estimated release date for Wicket 7? Why? In a couple of weeks I will start a new Wicket project and the estimated time to complete it is one month (at least for the initial release). I've thought maybe I could start it using current Wicket 7 and 1) provide feedback, 2) contribute to make wicket 7 stable 3) start migrating libraries I will use. But I would like to have my first release with an official version of Wicket 7. Is that too risky? -- Regards - Ernesto Reinaldo Barreiro
how to implement AjaxPagingNavigator.newNavigation in wicket 6
hi, i'm trying to migrate my app from wicket 1.4 to 6.13. and it seems AjaxPagingNavigator.newNavigation method has been deprecated. what should be used in wicket to get the same functionality. Thanks in advance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-implement-AjaxPagingNavigator-newNavigation-in-wicket-6-tp4663933.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: timing for Wicket 7?
Hi Ernesto, There won't be 7.0.0 in the next month. We will make a milestone release so users can try it and give feedback. The only thing to do before the milestone is to make the voted experimental modules stable. With this milestone release we want to get feedback for the small API changes we did. There are no other planned big changes for 7.x. I am working on markup driven component tree construction in a branch. We discuss it in dev@ but unless it is super stable and simple and approved by other devs it won't be added to 7.0.0. Martin Grigorov Wicket Training and Consulting On Fri, Jan 24, 2014 at 10:55 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Hi, What's the estimated release date for Wicket 7? Why? In a couple of weeks I will start a new Wicket project and the estimated time to complete it is one month (at least for the initial release). I've thought maybe I could start it using current Wicket 7 and 1) provide feedback, 2) contribute to make wicket 7 stable 3) start migrating libraries I will use. But I would like to have my first release with an official version of Wicket 7. Is that too risky? -- Regards - Ernesto Reinaldo Barreiro
Re: how to implement AjaxPagingNavigator.newNavigation in wicket 6
Hi, https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/markup/html/navigation/paging/AjaxPagingNavigator.java?source=cc#L124 It is not deprecated... Martin Grigorov Wicket Training and Consulting On Fri, Jan 24, 2014 at 11:01 AM, chathuraka.waas chathuraka.w...@gmail.com wrote: hi, i'm trying to migrate my app from wicket 1.4 to 6.13. and it seems AjaxPagingNavigator.newNavigation method has been deprecated. what should be used in wicket to get the same functionality. Thanks in advance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-implement-AjaxPagingNavigator-newNavigation-in-wicket-6-tp4663933.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: timing for Wicket 7?
Martin, Tanks for your answer. On Fri, Jan 24, 2014 at 10:04 AM, Martin Grigorov mgrigo...@apache.orgwrote: Hi Ernesto, There won't be 7.0.0 in the next month. Ok. We will make a milestone release so users can try it and give feedback. The only thing to do before the milestone is to make the voted experimental modules stable. I'm not planing to use any of the experimental modules. Just core + some of wicket stuff + maybe wicket bootstrap I might even decide go to production with a sufficiently stable release candidate core. For, this project there are planned latter release cycles, so I could upgrade to a release latter on. I can give it a try to Wicket 7.0 and if I do not find many hurdles stick to it. With this milestone release we want to get feedback for the small API changes we did. Ok. There are no other planned big changes for 7.x. I am working on markup driven component tree construction in a branch. We discuss it in dev@ but unless it is super stable and simple and approved by other devs it won't be added to 7.0.0. Yes I saw the discussion on dev list. I have the impression that this is the rather complex feature and that if included in Wicket 7 it might cause some delay on release. Martin Grigorov Wicket Training and Consulting On Fri, Jan 24, 2014 at 10:55 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Hi, What's the estimated release date for Wicket 7? Why? In a couple of weeks I will start a new Wicket project and the estimated time to complete it is one month (at least for the initial release). I've thought maybe I could start it using current Wicket 7 and 1) provide feedback, 2) contribute to make wicket 7 stable 3) start migrating libraries I will use. But I would like to have my first release with an official version of Wicket 7. Is that too risky? -- Regards - Ernesto Reinaldo Barreiro -- Regards - Ernesto Reinaldo Barreiro
Re: how to implement AjaxPagingNavigator.newNavigation in wicket 6
thanks for the reply. my mistake its just that the method signature has been changed. On Fri, Jan 24, 2014 at 3:24 PM, Martin Grigorov-4 [via Apache Wicket] ml-node+s1842946n4663936...@n4.nabble.com wrote: Hi, https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/markup/html/navigation/paging/AjaxPagingNavigator.java?source=cc#L124 It is not deprecated... Martin Grigorov Wicket Training and Consulting On Fri, Jan 24, 2014 at 11:01 AM, chathuraka.waas [hidden email]http://user/SendEmail.jtp?type=nodenode=4663936i=0 wrote: hi, i'm trying to migrate my app from wicket 1.4 to 6.13. and it seems AjaxPagingNavigator.newNavigation method has been deprecated. what should be used in wicket to get the same functionality. Thanks in advance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-implement-AjaxPagingNavigator-newNavigation-in-wicket-6-tp4663933.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4663936i=1 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4663936i=2 -- If you reply to this email, your message will be added to the discussion below: http://apache-wicket.1842946.n4.nabble.com/how-to-implement-AjaxPagingNavigator-newNavigation-in-wicket-6-tp4663933p4663936.html To unsubscribe from how to implement AjaxPagingNavigator.newNavigation in wicket 6, click herehttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4663933code=Y2hhdGh1cmFrYS53YWFzQGdtYWlsLmNvbXw0NjYzOTMzfC04NTAwMjE3MTc= . NAMLhttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- Thanks Regards, Chathuraka Waas -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-implement-AjaxPagingNavigator-newNavigation-in-wicket-6-tp4663933p4663938.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: timing for Wicket 7?
I'm hoping to finalise wicket 7 somewhere before the summer. But I can't guarantee that. My reasoning: - I expect Wicket 8 to be Java 8 based (lambda expressions and the new date/time APIs would make good additions to Wicket) - Wicket 8/Java 8 development should start when Java 8 is out and has good availability in open source containers (wildfly already supports java 8) - we have to get comfortable with Java 8 idioms to make the correct adjustments to Wicket, and this takes time - it takes a couple of months (2-5 ish) before we can finalise wicket 7 (solve issues, stabilise APIs) - I'd like to see the experimental modules we built in Wicket 6 to get some adoption and give us some feedback before we make wicket 7 final. This way we can fix API issues in the Wicket 7 modules (because semver). From a personal/commercial perspective it is best when we (Topicus) can integrate Wicket 7 before the summer time so we can stabilise our apps prior to getting hammered by oodles of users. Martijn On Fri, Jan 24, 2014 at 9:55 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Hi, What's the estimated release date for Wicket 7? Why? In a couple of weeks I will start a new Wicket project and the estimated time to complete it is one month (at least for the initial release). I've thought maybe I could start it using current Wicket 7 and 1) provide feedback, 2) contribute to make wicket 7 stable 3) start migrating libraries I will use. But I would like to have my first release with an official version of Wicket 7. Is that too risky? -- Regards - Ernesto Reinaldo Barreiro -- Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: timing for Wicket 7?
On Fri, Jan 24, 2014 at 2:30 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: I'm hoping to finalise wicket 7 somewhere before the summer. But I can't guarantee that. My reasoning: - I expect Wicket 8 to be Java 8 based (lambda expressions and the new date/time APIs would make good additions to Wicket) - Wicket 8/Java 8 development should start when Java 8 is out and has good availability in open source containers (wildfly already supports java 8) - we have to get comfortable with Java 8 idioms to make the correct adjustments to Wicket, and this takes time - it takes a couple of months (2-5 ish) before we can finalise wicket 7 (solve issues, stabilise APIs) - I'd like to see the experimental modules we built in Wicket 6 to get some adoption and give us some feedback before we make wicket 7 final. This way we can fix API issues in the Wicket 7 modules (because semver). From a personal/commercial perspective it is best when we (Topicus) can integrate Wicket 7 before the summer time so we can stabilise our apps prior to getting hammered by oodles of users. Early feedback is welcome even from Topicus! ;) Martijn On Fri, Jan 24, 2014 at 9:55 AM, Ernesto Reinaldo Barreiro reier...@gmail.com wrote: Hi, What's the estimated release date for Wicket 7? Why? In a couple of weeks I will start a new Wicket project and the estimated time to complete it is one month (at least for the initial release). I've thought maybe I could start it using current Wicket 7 and 1) provide feedback, 2) contribute to make wicket 7 stable 3) start migrating libraries I will use. But I would like to have my first release with an official version of Wicket 7. Is that too risky? -- Regards - Ernesto Reinaldo Barreiro -- Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: timing for Wicket 7?
Hi, On Fri, Jan 24, 2014 at 1:39 PM, Martin Grigorov mgrigo...@apache.orgwrote: On Fri, Jan 24, 2014 at 2:30 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: I'm hoping to finalise wicket 7 somewhere before the summer. But I can't guarantee that. My reasoning: - I expect Wicket 8 to be Java 8 based (lambda expressions and the new date/time APIs would make good additions to Wicket) - Wicket 8/Java 8 development should start when Java 8 is out and has good availability in open source containers (wildfly already supports java 8) - we have to get comfortable with Java 8 idioms to make the correct adjustments to Wicket, and this takes time - it takes a couple of months (2-5 ish) before we can finalise wicket 7 (solve issues, stabilise APIs) - I'd like to see the experimental modules we built in Wicket 6 to get some adoption and give us some feedback before we make wicket 7 final. This way we can fix API issues in the Wicket 7 modules (because semver). From a personal/commercial perspective it is best when we (Topicus) can integrate Wicket 7 before the summer time so we can stabilise our apps prior to getting hammered by oodles of users. Early feedback is welcome even from Topicus! ;) That was I idea when I asked the question. I would not mind running on release candidates as far as the functionality I use is stable and I get proper feedback reaction from core developers... and the price I have to pay on time for that is not to high.
Re: Wicket 6 - JavaScriptHeaderItem renders too early
I am still having this problem. The wicket:container solution leads me to
the following exception. Note that this exception is different than the one
in the prior post. I think I had a publish/refresh quirk. This is the
exception that is occurring now.
java.lang.IllegalStateException: No FilteringHeaderResponse is present in
the request cycle. This may mean that you have not decorated the header
response with a FilteringHeaderResponse. Simply calling the
FilteringHeaderResponse constructor sets itself on the request cycle
at
org.apache.wicket.markup.head.filter.FilteringHeaderResponse.get(FilteringHeaderResponse.java:165)
at
org.apache.wicket.markup.head.filter.HeaderResponseContainer.onComponentTagBody(HeaderResponseContainer.java:64)
at
org.apache.wicket.markup.html.panel.DefaultMarkupSourcingStrategy.onComponentTagBody(DefaultMarkupSourcingStrategy.java:71)
at
org.apache.wicket.Component.internalRenderComponent(Component.java:2549)
... 80 more
Entropy wrote
Browser giving me a little trouble. Apologies if I double-submitted this.
My respoonse:
I didn't even know such a website existed. Thanks.
I am trying to implement the HeaderResponseContainer and filter
suggestion. In my component I added the container:
add(new HiddenField(INTERNAL_HIDDEN_ROWS_SELECTED, new
Model()).setOutputMarkupId(true).setMarkupId(INTERNAL_HIDDEN_ROWS_SELECTED));
add(new HiddenField(INTERNAL_HIDDEN_COLUMN_SYNCH, new Model()));
add(new HeaderResponseContainer(gridCode, gridCodeFilter));
I added the HTML to my component (notice same level as those hiddens)
wicket:panel
div class=enotes
input type=hidden wicket:id=_gridRowsSelected id=_gridRowsSelected
/
input type=hidden wicket:id=_gridColSynch id=_gridColSynch /
div id=eNoteGrid
/div
/div
wicket:container wicket:id=gridCode /
/wicket:panel
And in the renderHead I do:
@Override
public void renderHead(Component comp, IHeaderResponse response) {
super.renderHead(comp, response);
callbackUrl = behavior.getCallbackUrl().toString();
//JS
response.render(JavaScriptHeaderItem.forReference(new
JavaScriptResourceReference(ExtGrid.class, ExtGridSupport.js)));
response.render(new
FilteredHeaderItem(JavaScriptContentHeaderItem.forScript(writeGridJS(),
getId() + _js), gridCodeFilter));
}
But I am getting:
Failed to handle:
wicket:container wicket:id=gridCode/
. It might be
that no resolver has been registered to handle this special tag. But it
also could be that you declared wicket:id=gridCode in your markup, but
that
you either did not add the component to your page at all, or that the
hierarchy does not match.
MarkupStream: [markup =
file:/C:/views/EquitShare_Development/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/AFMSShared/gov/usdoj/afms/shared/wicket/ext/grid/ExtGrid.html
wicket:panel
div class=enotes
input type=hidden wicket:id=_gridRowsSelected
id=_gridRowsSelected/
input type=hidden wicket:id=_gridColSynch id=_gridColSynch/
div id=eNoteGrid
/div
/div
wicket:container wicket:id=gridCode/
/wicket:panel
, index = 6, current = '
wicket:container
wicket:id=gridCode/
' (line 0, column 0)]
at
org.apache.wicket.markup.MarkupStream.throwMarkupException(MarkupStream.java:526)
at
org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1409)
at org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1554)
at
org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1529)
at
org.apache.wicket.MarkupContainer.renderAssociatedMarkup(MarkupContainer.java:689)
at
org.apache.wicket.markup.html.panel.AssociatedMarkupSourcingStrategy.renderAssociatedMarkup(AssociatedMarkupSourcingStrategy.java:76)
at
org.apache.wicket.markup.html.panel.PanelMarkupSourcingStrategy.onComponentTagBody(PanelMarkupSourcingStrategy.java:112)
at
org.apache.wicket.Component.internalRenderComponent(Component.java:2549)
at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1493)
at org.apache.wicket.Component.internalRender(Component.java:2379)
at org.apache.wicket.Component.render(Component.java:2307)
at
org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1390)
at org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1554)
at
org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1529)
at
org.apache.wicket.MarkupContainer.renderAssociatedMarkup(MarkupContainer.java:689)
at
org.apache.wicket.markup.html.panel.AssociatedMarkupSourcingStrategy.renderAssociatedMarkup(AssociatedMarkupSourcingStrategy.java:76)
at
org.apache.wicket.markup.html.panel.PanelMarkupSourcingStrategy.onComponentTagBody(PanelMarkupSourcingStrategy.java:112)
at
org.apache.wicket.Component.internalRenderComponent(Component.java:2549)
at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1493)
at
Re: Bunch of Page Expired exceptions in Wicket 6.10.0
Yes, but in my example, I was referring to how 2 different apps with different cookies are both running on localhost with different ports. I get this issue all the time on chromium when I test multiple apps all on location with different ports. I keep having to login whenever I refresh a different tab. (yeah, i know it took me 4 months to get back to this but i was busy. :-) ) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Bunch-of-Page-Expired-exceptions-in-Wicket-6-10-0-tp4661502p4663946.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
continueToOriginalDestination hacks
I'm building an app that uses oauth to login but I found that continueToOriginalDestination doesn't work when I login via twitter but it works when I use google to login. The user instead ends up in the fallback value I used: continueToOriginalDestination(); setResponsePage(MemberHome.class); The oauth code for google vs twitter is pretty much the same and before I realized it was specific to twitter, I thought it was a wicket bug. I'm trying to add another fallback method wherein I manually store the original destination value and deal with it myself. If anybody is curious I use the following setup: scribe-java for oauth a LoginPanel class that shows 2 login forms (google, twitter) form submits end in something like: throw new RedirectToUrlException(twitterLoginUrl); login panel handles the return from oauth using page parameters and upon success calls: - signIn on websession - continueToOriginalDestination(); - setResponsePage(MemberHome.class); -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/continueToOriginalDestination-hacks-tp4663947.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
