[CONF] Apache Wicket: Companies that provide services (page edited)
Page Edited : WICKET : Companies that provide services Companies that provide services has been edited by Niclas Hedhman (Dec 19, 2006). (View changes) Content: List of companies that provide commercial services for Wicket. Wicket Support Services Wicket Support is a company that provides training, consultations and commercial support for Wicket. Jayway is a premier Java consulting group that via its Malaysian subsidiary provides services for Wicket development, especially running Wicket in OSGi environments. Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request Unsubscribe or edit your notifications preferences
[jira] Created: (WICKET-178) Uncaught exception guesing urls using CryptedUrlWebRequestCodingStrategy
Uncaught exception guesing urls using CryptedUrlWebRequestCodingStrategy
Key: WICKET-178
URL: http://issues.apache.org/jira/browse/WICKET-178
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.2.3
Environment: Windows XP
Reporter: Craig Lenzen
Priority: Minor
When used the CryptedUrlWebRequestCodingStrategy strategy in my wicket
application I get an uncaught exception when trying to hack urls in the browser
address bar.
Configuration:
@Override
protected IRequestCycleProcessor newRequestCycleProcessor() {
return new CompoundRequestCycleProcessor(new
CryptedUrlWebRequestCodingStrategy(
new WebRequestCodingStrategy()),
null,
null,
null,
null);
} // newRequestCycleProcessor
Exception:
java.lang.ArrayIndexOutOfBoundsException: 81
at wicket.util.crypt.Base64UrlSafe.decodeBase64(Base64UrlSafe.java:367)
at wicket.util.crypt.AbstractCrypt.decryptUrlSafe(AbstractCrypt.java:87)
at
wicket.protocol.http.request.CryptedUrlWebRequestCodingStrategy.decodeURL(CryptedUrlWebRequestCodingStrategy.java:256)
at
wicket.protocol.http.request.CryptedUrlWebRequestCodingStrategy.decode(CryptedUrlWebRequestCodingStrategy.java:91)
at wicket.Request.getRequestParameters(Request.java:163)
at wicket.RequestCycle.step(RequestCycle.java:992)
at wicket.RequestCycle.steps(RequestCycle.java:1084)
at wicket.RequestCycle.request(RequestCycle.java:454)
at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
I'd except that this exception would be caught an a user is taken to a user
friendly error page, possibly the default error page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (WICKET-177)
[ http://issues.apache.org/jira/browse/WICKET-177?page=all ] Matej Knopp reassigned WICKET-177: -- Assignee: Juergen Donnerstag > > > Key: WICKET-177 > URL: http://issues.apache.org/jira/browse/WICKET-177 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 2.0 >Reporter: Matej Knopp > Assigned To: Juergen Donnerstag > > In wicket examples, when I go to the simple tree page > http://localhost:8080/we/ajax?wicket:bookmarkablePage=:wicket.examples.ajax.builtin.tree.SimpleTreePage > and after that go to the tree table page > http://localhost:8080/we/ajax?wicket:bookmarkablePage=:wicket.examples.ajax.builtin.tree.TreeTablePage > I get this exception > WicketMessage: The component [MarkupContainer [Component id = > -_autolink_2, page = wicket.examples.ajax.builtin.tree.TreeTablePage, > path = > 2:-:--child1:--extend2:-_link_1:-_autolink_2.AutoLinkResolver$AutolinkBookmarkablePageLink, > isVisible = true, isVersioned = true]] has the same wicket:id as another > component already rendered at the same level > Root cause: > wicket.markup.MarkupException: The component [MarkupContainer [Component id = > -_autolink_2, page = wicket.examples.ajax.builtin.tree.TreeTablePage, > path = > 2:-:--child1:--extend2:-_link_1:-_autolink_2.AutoLinkResolver$AutolinkBookmarkablePageLink, > isVisible = true, isVersioned = true]] has the same wicket:id as another > component already rendered at the same level > at wicket.DebugHelper.onBeginComponentRender(DebugHelper.java:69) > at wicket.Page.componentRendered(Page.java:347) > at wicket.Component.rendered(Component.java:2021) > at wicket.Component.render(Component.java:1736) > at wicket.MarkupContainer.renderNext(MarkupContainer.java:1380) > at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) > at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) > at wicket.Component.renderComponent(Component.java:1968) > at wicket.MarkupContainer.onRender(MarkupContainer.java:919) > at wicket.Component.render(Component.java:1724) > at > wicket.markup.resolver.WicketLinkResolver.resolve(WicketLinkResolver.java:74) > at wicket.MarkupContainer.renderNext(MarkupContainer.java:1405) > at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) > at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) > at wicket.Component.renderComponent(Component.java:1968) > at wicket.MarkupContainer.onRender(MarkupContainer.java:919) > at wicket.Component.render(Component.java:1724) > at > wicket.markup.resolver.MarkupInheritanceResolver.resolve(MarkupInheritanceResolver.java:61) > at wicket.MarkupContainer.renderNext(MarkupContainer.java:1405) > at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) > at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) > at wicket.Component.renderComponent(Component.java:1968) > at wicket.MarkupContainer.onRender(MarkupContainer.java:919) > at wicket.Component.render(Component.java:1724) > at > wicket.markup.resolver.MarkupInheritanceResolver.resolve(MarkupInheritanceResolver.java:61) > at wicket.MarkupContainer.renderNext(MarkupContainer.java:1405) > at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) > at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) > at wicket.Component.renderComponent(Component.java:1968) > at wicket.MarkupContainer.onRender(MarkupContainer.java:919) > at wicket.Component.render(Component.java:1724) > at wicket.MarkupContainer.renderNext(MarkupContainer.java:1380) > at wicket.MarkupContainer.renderAll(MarkupContainer.java:936) > at wicket.Page.onRender(Page.java:1046) > at wicket.Component.render(Component.java:1724) > at wicket.Component.render(Component.java:1678) > at wicket.Page.renderPage(Page.java:1169) > at > wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:229) > at > wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:53) > at > wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:65) > at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:944) > at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:973) > at wicket.RequestCycle.step(RequestCycle.java:1054) > at wicket.RequestCycle.steps(RequestCycle.java:1125) > at wicket.RequestCycle.request(RequestCycle.java:470) > at wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:232) > at wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:122) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473) > at org.mortbay.jetty.servlet.Servlet
[jira] Created: (WICKET-177)
http://issues.apache.org/jira/browse/WICKET-177 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 2.0 Reporter: Matej Knopp In wicket examples, when I go to the simple tree page http://localhost:8080/we/ajax?wicket:bookmarkablePage=:wicket.examples.ajax.builtin.tree.SimpleTreePage and after that go to the tree table page http://localhost:8080/we/ajax?wicket:bookmarkablePage=:wicket.examples.ajax.builtin.tree.TreeTablePage I get this exception WicketMessage: The component [MarkupContainer [Component id = -_autolink_2, page = wicket.examples.ajax.builtin.tree.TreeTablePage, path = 2:-:--child1:--extend2:-_link_1:-_autolink_2.AutoLinkResolver$AutolinkBookmarkablePageLink, isVisible = true, isVersioned = true]] has the same wicket:id as another component already rendered at the same level Root cause: wicket.markup.MarkupException: The component [MarkupContainer [Component id = -_autolink_2, page = wicket.examples.ajax.builtin.tree.TreeTablePage, path = 2:-:--child1:--extend2:-_link_1:-_autolink_2.AutoLinkResolver$AutolinkBookmarkablePageLink, isVisible = true, isVersioned = true]] has the same wicket:id as another component already rendered at the same level at wicket.DebugHelper.onBeginComponentRender(DebugHelper.java:69) at wicket.Page.componentRendered(Page.java:347) at wicket.Component.rendered(Component.java:2021) at wicket.Component.render(Component.java:1736) at wicket.MarkupContainer.renderNext(MarkupContainer.java:1380) at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) at wicket.Component.renderComponent(Component.java:1968) at wicket.MarkupContainer.onRender(MarkupContainer.java:919) at wicket.Component.render(Component.java:1724) at wicket.markup.resolver.WicketLinkResolver.resolve(WicketLinkResolver.java:74) at wicket.MarkupContainer.renderNext(MarkupContainer.java:1405) at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) at wicket.Component.renderComponent(Component.java:1968) at wicket.MarkupContainer.onRender(MarkupContainer.java:919) at wicket.Component.render(Component.java:1724) at wicket.markup.resolver.MarkupInheritanceResolver.resolve(MarkupInheritanceResolver.java:61) at wicket.MarkupContainer.renderNext(MarkupContainer.java:1405) at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) at wicket.Component.renderComponent(Component.java:1968) at wicket.MarkupContainer.onRender(MarkupContainer.java:919) at wicket.Component.render(Component.java:1724) at wicket.markup.resolver.MarkupInheritanceResolver.resolve(MarkupInheritanceResolver.java:61) at wicket.MarkupContainer.renderNext(MarkupContainer.java:1405) at wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:974) at wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:908) at wicket.Component.renderComponent(Component.java:1968) at wicket.MarkupContainer.onRender(MarkupContainer.java:919) at wicket.Component.render(Component.java:1724) at wicket.MarkupContainer.renderNext(MarkupContainer.java:1380) at wicket.MarkupContainer.renderAll(MarkupContainer.java:936) at wicket.Page.onRender(Page.java:1046) at wicket.Component.render(Component.java:1724) at wicket.Component.render(Component.java:1678) at wicket.Page.renderPage(Page.java:1169) at wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:229) at wicket.request.compound.DefaultResponseStrategy.respond(DefaultResponseStrategy.java:53) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:65) at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:944) at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:973) at wicket.RequestCycle.step(RequestCycle.java:1054) at wicket.RequestCycle.steps(RequestCycle.java:1125) at wicket.RequestCycle.request(RequestCycle.java:470) at wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:232) at wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:122) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635) at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at org.mortbay.http.HttpServer.service(HttpServer.java:954) at org.mortbay.http.HttpConnection.service(HttpConnection.java:814) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:9
[jira] Commented: (WICKET-175) Page.onDetach is called by each ComponentResourceRequestTarget
[ http://issues.apache.org/jira/browse/WICKET-175?page=comments#action_12459755 ] Matej Knopp commented on WICKET-175: I think every component should be prepared that the detach method can be called twice, or even without calling attach first. Or perhaps we need something like "attached" flag for every component. But on ajax request, we should really call page.detach only once (after the request is done). There's no need to call detach on any component twice in one request. > Page.onDetach is called by each ComponentResourceRequestTarget > -- > > Key: WICKET-175 > URL: http://issues.apache.org/jira/browse/WICKET-175 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 2.0, 1.3 >Reporter: Alastair Maw > > ComponentResourceRequestTarget#detach(RequestCycle) calls > page#internalDetach() > This results in Page#onDetach() being called as many times as there are > images or whatever on your page, which seems entirely wrong. Mentioned this > to ivaynberg on IRC and he said: "we should have theadlocal guards". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-175) Page.onDetach is called by each ComponentResourceRequestTarget
[ http://issues.apache.org/jira/browse/WICKET-175?page=comments#action_12459753 ] Johan Compagner commented on WICKET-175: and we also don't like that detached is called twice (see other bug) so we have here a bit of a problem. If we don't care about that, then the fix shouldn't be to hard. > Page.onDetach is called by each ComponentResourceRequestTarget > -- > > Key: WICKET-175 > URL: http://issues.apache.org/jira/browse/WICKET-175 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 2.0, 1.3 >Reporter: Alastair Maw > > ComponentResourceRequestTarget#detach(RequestCycle) calls > page#internalDetach() > This results in Page#onDetach() being called as many times as there are > images or whatever on your page, which seems entirely wrong. Mentioned this > to ivaynberg on IRC and he said: "we should have theadlocal guards". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-175) Page.onDetach is called by each ComponentResourceRequestTarget
[ http://issues.apache.org/jira/browse/WICKET-175?page=comments#action_12459742 ] Matej Knopp commented on WICKET-175: I also think we should only attach the rendered component, and detach the whole page. Because when attaching the component, we don't really know what components really are attached. > Page.onDetach is called by each ComponentResourceRequestTarget > -- > > Key: WICKET-175 > URL: http://issues.apache.org/jira/browse/WICKET-175 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 2.0, 1.3 >Reporter: Alastair Maw > > ComponentResourceRequestTarget#detach(RequestCycle) calls > page#internalDetach() > This results in Page#onDetach() being called as many times as there are > images or whatever on your page, which seems entirely wrong. Mentioned this > to ivaynberg on IRC and he said: "we should have theadlocal guards". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-175) Page.onDetach is called by each ComponentResourceRequestTarget
[ http://issues.apache.org/jira/browse/WICKET-175?page=comments#action_12459709 ] Martijn Dashorst commented on WICKET-175: - Why attach the page? no need to do that... Just call detach on the page and process all children. I sure as hell don't want to start attaching models for the sake of detaching them directly afterwards. > Page.onDetach is called by each ComponentResourceRequestTarget > -- > > Key: WICKET-175 > URL: http://issues.apache.org/jira/browse/WICKET-175 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 2.0, 1.3 >Reporter: Alastair Maw > > ComponentResourceRequestTarget#detach(RequestCycle) calls > page#internalDetach() > This results in Page#onDetach() being called as many times as there are > images or whatever on your page, which seems entirely wrong. Mentioned this > to ivaynberg on IRC and he said: "we should have theadlocal guards". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-175) Page.onDetach is called by each ComponentResourceRequestTarget
[
http://issues.apache.org/jira/browse/WICKET-175?page=comments#action_12459701 ]
Igor Vaynberg commented on WICKET-175:
--
i see two ways to do this
in ajax attach the entire page, and then detach it
or
attach only the rendering components and then detach them, that means the logic
should not be
if (attached) { detach(); detachchildren(); } but rather if (attached) {
detach(); } detachchildren(); and detachchildren having the same if (attached)
guard for every child.
> Page.onDetach is called by each ComponentResourceRequestTarget
> --
>
> Key: WICKET-175
> URL: http://issues.apache.org/jira/browse/WICKET-175
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 2.0, 1.3
>Reporter: Alastair Maw
>
> ComponentResourceRequestTarget#detach(RequestCycle) calls
> page#internalDetach()
> This results in Page#onDetach() being called as many times as there are
> images or whatever on your page, which seems entirely wrong. Mentioned this
> to ivaynberg on IRC and he said: "we should have theadlocal guards".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-175) Page.onDetach is called by each ComponentResourceRequestTarget
[ http://issues.apache.org/jira/browse/WICKET-175?page=comments#action_12459663 ] Martijn Dashorst commented on WICKET-175: - The problem is that in ajax requests the page is not detached at all, even though its models can be attached by components down the hierarchy. So the check on isAttached is not correct as the page may not be attached, but its models are. > Page.onDetach is called by each ComponentResourceRequestTarget > -- > > Key: WICKET-175 > URL: http://issues.apache.org/jira/browse/WICKET-175 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 2.0, 1.3 >Reporter: Alastair Maw > > ComponentResourceRequestTarget#detach(RequestCycle) calls > page#internalDetach() > This results in Page#onDetach() being called as many times as there are > images or whatever on your page, which seems entirely wrong. Mentioned this > to ivaynberg on IRC and he said: "we should have theadlocal guards". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WICKET-175) Page.onDetach is called by each ComponentResourceRequestTarget
[
http://issues.apache.org/jira/browse/WICKET-175?page=comments#action_12459662 ]
Johan Compagner commented on WICKET-175:
we already had a save guard in page:
public void internalDetach()
{
if (attached)
{
super.internalDetach();
attached = false;
}
}
That was requested by martijn. (see other bug about detached called to many
times)
but then martijn itself rolled it back again for WICKET-112
And i already warned this would be happening that the boolean did also
prevent components from detaching that where "outside" of the page touched.
But ComponentResourceRequestTarget is just wrong in this method:
public void detach(RequestCycle requestCycle)
{
page.internalDetach();
}
It just calls page.internalDetach() without an attach call first. So you can
call detach on page but don't want an attach..
I think it should call detach directy on the component not on the page.
> Page.onDetach is called by each ComponentResourceRequestTarget
> --
>
> Key: WICKET-175
> URL: http://issues.apache.org/jira/browse/WICKET-175
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 2.0, 1.3
>Reporter: Alastair Maw
>
> ComponentResourceRequestTarget#detach(RequestCycle) calls
> page#internalDetach()
> This results in Page#onDetach() being called as many times as there are
> images or whatever on your page, which seems entirely wrong. Mentioned this
> to ivaynberg on IRC and he said: "we should have theadlocal guards".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WICKET-176) Introduce AjaxFormElementValidatingBehavior
[ http://issues.apache.org/jira/browse/WICKET-176?page=all ] Erik van Oosten updated WICKET-176: --- Attachment: AjaxFormComponentValidatingBehavior.java Attached another version. This version has comments and is more in line with AjaxFormValidatingBehavior (finds feedback panels automatically and has throttleDelay parameter). Unlike the previous version, this version is not tested and not even compiled yet. > Introduce AjaxFormElementValidatingBehavior > --- > > Key: WICKET-176 > URL: http://issues.apache.org/jira/browse/WICKET-176 > Project: Wicket > Issue Type: New Feature > Components: wicket >Affects Versions: 1.2.3 >Reporter: Erik van Oosten > Attachments: AjaxFormComponentValidatingBehavior.java, > AjaxFormComponentValidatingBehavior.java > > > There is currently no easy way to validate a single form element using Ajax. > Please add attached code to the Wicket-core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (WICKET-176) Introduce AjaxFormElementValidatingBehavior
[ http://issues.apache.org/jira/browse/WICKET-176?page=all ] Erik van Oosten updated WICKET-176: --- Attachment: AjaxFormComponentValidatingBehavior.java I found out that AjaxFormComponentValidatingBehavior is a better name for the class. > Introduce AjaxFormElementValidatingBehavior > --- > > Key: WICKET-176 > URL: http://issues.apache.org/jira/browse/WICKET-176 > Project: Wicket > Issue Type: New Feature > Components: wicket >Affects Versions: 1.2.3 >Reporter: Erik van Oosten > Attachments: AjaxFormComponentValidatingBehavior.java > > > There is currently no easy way to validate a single form element using Ajax. > Please add attached code to the Wicket-core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WICKET-176) Introduce AjaxFormElementValidatingBehavior
Introduce AjaxFormElementValidatingBehavior --- Key: WICKET-176 URL: http://issues.apache.org/jira/browse/WICKET-176 Project: Wicket Issue Type: New Feature Components: wicket Affects Versions: 1.2.3 Reporter: Erik van Oosten There is currently no easy way to validate a single form element using Ajax. Please add attached code to the Wicket-core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
