Serban,

If you make the change below in StatelessWebRequestCodingStrategy the
component should be found in the page.  It's a copy from
BookmarkableListenerInterfaceRequestTarget#processEvents.  Jolira noted this
might be needed in their comments.


private static Component getComponent(final Page page, final String
componentPath) {
                final String pageRelativeComponentPath =
Strings.afterFirstPathComponent(componentPath, PATH_SEPARATOR);
                 Component component = page.get(pageRelativeComponentPath);

                
                if(component == null) {
                        page.prepareForRender(false);
                        component = page.get(pageRelativeComponentPath);
                        
                        // See {@link
                        //
BookmarkableListenerInterfaceRequestTarget#processEvents(RequestCycle)}
                        // We make have to try to look for the component twice, 
if we hit the
                        // same condition.
                        if (component == null) {
                                throw new WicketRuntimeException("unable to 
find component with path " +
pageRelativeComponentPath + " on stateless page " + page
                                                + " it could be that the 
component is inside a repeater make your
component return false in getStatelessHint()");
                        }
                }
                

                return component;
}

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Stateless-Wicket-and-Ajax-tp3348266p3350985.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

Reply via email to