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

capo edited comment on WICKET-1105 at 10/26/07 3:19 PM:
---------------------------------------------------------------

Test portlets for bug reproduction.

Steps:
1. unzip file
2. 'mvn eclipse:eclipse' (for eclipse of course)
3. run 'TestPortal' bean like java application (in src/test/java folder)
4. type in your browser 'http://localhost:8083/portlet1' for good behavior
5. type in your browser 'http://localhost:8083/portlet2' for bad behavior


      was (Author: capo):
    Test portlets for bug reproduction.

Steps:
1. unzip file
2. 'mvn eclipse:eclipse' (for eclipse of course)
3. run 'TestPortal' bean like java application (in src/test/java folder)
4. type in your browser 'http://localhost:8083/portlet1' for bad behavior
5. type in your browser 'http://localhost:8083/portlet2' for bad behavior

  
> Missing javascript header referencies in Wicket portlet
> -------------------------------------------------------
>
>                 Key: WICKET-1105
>                 URL: https://issues.apache.org/jira/browse/WICKET-1105
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-portlet
>         Environment: wicket trunk revision 588784
> JDK 1.5.0_13-b05
> Maven version: 2.0.7
>            Reporter: Michal Capo
>         Attachments: wicket-portlets-test.zip
>
>
> I have two wicket portlets using RatingPanel they are almost same. There is 
> one difference in the markup.
> First:
> <head>
>       <link rel="stylesheet" type="text/css" href="style.css"/>
> </head>
> <html>
>       <span wicket:id="rating"></span>
> </html>
> Second:
> <html>
>       <span wicket:id="rating"></span>
> </html>
> In first one is request executed via ajax. In second one not. In first one 
> rendered page contains reference to 'wicket-ajax.js' file but in the second 
> not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to