Find all needed information about Wicket 6 Portlet Support. Below you can see links where you can find everything you want to know about Wicket 6 Portlet Support.
https://issues.apache.org/jira/browse/WICKET-647
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 …
https://issues.apache.org/jira/browse/WICKET-1620
WICKET-2387 Failure using a Redirect strategy in a Websphere Portal 6.1 Portlet due to response already committed. Resolved; Options. Show All; ... create javadoc for existing portal imeplementation: Closed: Ate Douma: 2. Upgrade Wicket Portlet Support to only use native Portlet API 2.0 : Resolved: Ate Douma: 3. Add optional support for ...
https://developer.jboss.org/thread/125649
Jan 21, 2008 · I have been trying to make Wicket (1.3.0) work with Jboss Portal (Jboss AS 4.2.2 and Portal 2.6.1. or 2.6.3.) for 2 weeks. Everything is ok, except AJAX calling. (This portlet works like charm on Jetspeed2, so the wicket portlet should be OK.) So let's see what we know... Ajax Request reaches the server, and it gives me a respond too.
http://wicket.apache.org/start/wicket-6.x.html
For example it is not possible to use Wicket Extensions 1.5 in a Wicket 6 project, or Wicket CDI 6.19 in a Wicket 7 project. The same goes for 3rd party libraries: make sure you always use a compatible version of your 3rd party library.
http://issues.apache.org/jira/browse/WICKET-1132
I created 2 simple Links a AjaxLink and a 'normal' link in a portlet. I deployed this portlet on Liferay. The normal link works fine. But the Ajax links doesn't work. In the generated HTML the url's look like this.
http://apache-wicket.1842946.n4.nabble.com/Roadmap-for-Wicket-6-td3777610.html
In order to start discussing what will constitute Wicket Next and where we want to take our beloved framework, I'll start off with my wish list: 1. Java 6 as a minimum requirement for *all* of wicket 2. Servlet API 3.0 as a minimum requirement 3. JavaEE 6 support for at least CDI 4. Proper OSGi support 5. Ajax refactoring to use JQuery and provide proper JQuery integration in core 6.
Need to find Wicket 6 Portlet Support information?
To find needed information please read the text beloow. If you need to know more you can click on the links to visit sites with more detailed data.
