[ 
https://issues.apache.org/jira/browse/WICKET-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212715#comment-13212715
 ] 

Josh Chappelle edited comment on WICKET-4404 at 2/21/12 4:38 PM:
-----------------------------------------------------------------

I just unzipped the wicket_cryptomapper_quickstart.zip and imported the project 
into eclipse. When I pull it up in IE9 it renders the page fine. When I click 
the link titled "Yui menu link" it does nothing. I don't see any javascript 
errors either. I have put a debug point in CryptoMapper and I know that 
mapRequest() is getting called. In fact, I see that it gets two requests(the 
other link does this as well, I assume it is a wicket internal thing and must 
be normal). In the mapRequest there is a decryptUrl method that gets called. 
Here is the returned value of decryptUrl for each link for each request.

YUI Menu Link Request 1:
?0-1.IBehaviorListener.0-menu

YUI Menu Link Request 2:
?0

Regular Ajax Link Request 1:
?0-3.IBehaviorListener.0-link

Regular Ajax Link Request 2:
wicket/bookmarkable/com.test.wicket.DestinationPage

I hope you can get the quickstart to work for you. I've run down as much of 
this thing as I know to do. The only reason I am using the "homemade" yui menu 
instead of the wicketstuff version is that we were hitting some bugs with it 
and I couldn't really get any support from the community on it. 

Also, this worked in wicket 1.4.x.

Thanks for the help.

Josh
                
      was (Author: jchappelle):
    I just unzipped the wicket_cryptomapper_quickstart.zip and imported the 
project into eclipse. When I pull it up in IE9 it renders the page fine. When I 
click the link titled "Yui menu link" it does nothing. I have put a debug point 
in CryptoMapper and I know that mapRequest() is getting called. In fact, I see 
that it gets two requests(the other link does this as well, I assume it is a 
wicket internal thing and must be normal). In the mapRequest there is a 
decryptUrl method that gets called. Here is the returned value of decryptUrl 
for each link for each request.

YUI Menu Link Request 1:
?0-1.IBehaviorListener.0-menu

YUI Menu Link Request 2:
?0

Regular Ajax Link Request 1:
?0-3.IBehaviorListener.0-link

Regular Ajax Link Request 2:
wicket/bookmarkable/com.test.wicket.DestinationPage

I hope you can get the quickstart to work for you. I've run down as much of 
this thing as I know to do. The only reason I am using the "homemade" yui menu 
instead of the wicketstuff version is that we were hitting some bugs with it 
and I couldn't really get any support from the community on it. 

Also, this worked in wicket 1.4.x.

Thanks for the help.

Josh
                  
> CryptoMapper is not successfully decoding 
> AbstractDefaultAjaxBehavior.generateCallbackScript request
> ----------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4404
>                 URL: https://issues.apache.org/jira/browse/WICKET-4404
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.4
>         Environment: IE9
>            Reporter: Josh Chappelle
>              Labels: 1.5, AbstractDefaultAjaxBehavior, cryptomapper, 
> generateCallbackScript, wicket
>         Attachments: wicket_cryptomapper_quickstart.zip
>
>
> I have a yui menu wrapper that I have written that does not work when the 
> cryptomapper is being used. It works fine otherwise. It basically outputs 
> javascript in the header and that javascript renders the dom elements. So the 
> only wicket component is a div that represents the menu. All of the items get 
> generated by the javascript. One of the attributes on the menu item is a 
> "url" attribute. In the url attribute I have "javascript: " and then the 
> javascript string that is created via the generateCallbackScript method. The 
> respond method never gets called if the cryptomapper is enabled. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to