[jira] Commented: (WICKET-647) New Wicket Portlet support

["Senthil Durai (JIRA)" <ji...@apache.org>]

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

Senthil Durai commented on WICKET-647:
--------------------------------------

Hello Ate Douma,

I was about to create an application with wicket, spring, hibernate, ibatis and mssql but we are stopped not to use wicket
because wicket doesn't support portlet(JSR-168). I don't have good experience in portlet projects. but i love wicket.

I tried using wicket 1.3 beta 2 and deployed in websphere 6.1 but my application is not working. 
But the same application works in tomcat and jetty. So i have used wicket 1.2.6 for my new application.

The suggested technology for my application is JSF, spring, hibernate, mssql with DOJO. can you comment on this?

If you strongly recommend wicket instead of JSF and DOJO for portlet please give me comparison and a basic sample portlet configuration.

Thanks,
Senthil Durai
ssenthildurai@yahoo.com



> New Wicket Portlet support
> --------------------------
>
>                 Key: WICKET-647
>                 URL: https://issues.apache.org/jira/browse/WICKET-647
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket-portlet
>    Affects Versions: 1.3.0-beta2
>         Environment: Jetspeed-2.1.1-beta1, Tomcat 5.5, Servlet API 2.4, JDK 1.4 & Java 5
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>
> I'm providing a new solution for Wicket Portlet support, see also my initial proposal on the wicket-dev list: http://www.nabble.com/A-new-proposal-for-Wicket-Portlet-support-tf3836652.html
> As this solution will require a few (but not very much) changes to Wicket core, I'll create a separate branch first to let everyone involved review and test it out.
> I'll also create separate sub tasks in JIRA to record the changes required and the new features provided so each can be reviewed individually and we can have step-by-step discussions how to proceed in bringing this solution into the main trunk.
> Note: as current Wicket development is getting close to the 1.3.0 release, I don't expect all of this to be merged into the trunk until after the 1.3.0 release.
> But some of my proposed changes really are very light and non-intrusive, so I can imagine (and hope) those can be integrated in the trunk even before the 1.3.0 release.
> That definitely would make it easier for me to provide portlet support to my own development team using the wicket core trunk and only a few additional patches.
>  

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