I started to read about wicket integration with liferay. I found very old information that wicket portlet is no longer supported, but wicket version 1.5.6 works fine with liferay 6.0. What about Liferay 6.2?
Just yesterday a user from the community created a Pull Request to fix the support for Liferay: https://github.com/wicketstuff/core/pull/476.
The Pull Request is for WicketStuff 7.x though. You are very welcome to port the fixes to wicket-6.x branch and we will add them for WicketStuff 6.23.0.
WicketStuff 1.5.x is not maintained anymore.
Apache Wicket version 6.x, 7.x and 8.x supports JSR286 portlets.
Please see the following wiki of how to use the apache wicket portlet bridge.
https://github.com/wicketstuff/core/wiki/Portlet
Related
How do we upgrade the Struts version to the latest in Liferay 6.2 CE?
If you are thinking of updating the struts version for the Liferay OOTB Portlets, then I have some very bad news for you -- You can't.
For your own portlets I think you can use Struts-2.
Will it be possible to let us know your requirement, so that the community might be able to help with an alternative.
I have a portlet that worked fine on Liferay 6.1 portal but when I deploy it on Liferay 5.2.3
my configuration page did not even open.
How should I make it work ?
Here is a nice authoritative answer to a very similar question.
The portlets of newer versions are not designed to work on older installation of Liferay. Since they are compiled using the latest plugins-sdk and the also the different jars which have changed since the last version.
So if you want the newer version portlet to work with any older version then you have to compile the portlet with an older version of Liferay with that plugins-SDK. And I am sure there would be a lot of classes and jsp-tags in the Liferay 6.1 portlet which would not work in Liferay 5.2.3.
I am upgrading Liferay from 5.2 to 6.1. I want to know similar to core liferay, for theme also we have to follow two steps up-gradation (i.e from 5.2 to 6.0 then 6.0 to 6.1) or we can directly go for 5.2 to 6.1 theme upgrade.
The theme doesn't require any sort of upgrade process so you'll only need to rewrite it once.
Basically you'll just need to make sure that the theme is using 6.1 API and AUI.
The most complicated of the two being migrating from jQuery to AUI (YUI).
Here is a "rosetta stone" to get you started: http://www.jsrosettastone.com/
The upgrade is not like the core liferay.
Steps (more of a check-list) to look for when upgrading themes:
1) You have to change the liferay-look-and-feel.xml's <version>6.1+</version>.
2) You would need to manually include jQuery, as now it is not part of Liferay (Alloy UI is now a part). You can include them through the template files (*.vm).
3) There are a lot of customizations in the template files (portal_normal.vm, portlet.vm, navigation.vm etc) from 5.2 to 6.1, so if you have done customizations to these then you would have to again customize them.
4) Also a lot of CSS changes have happened since 5.2, infact 6.1 UI is almost completely different from 5.2. So you will have to again style liferay html elements as it now uses alloy UI JSP tags to render them.
Hope this helps.
Can someone please help me out with the Oracle ADF faces application which I'm trying to deploy on Websphere 7.0? Do I need to apply any fixpacks on WAS? I'm trying to migrate this project from Websphere 6.1 to Websphere 7.0.
In Websphere 6.1, after removing jsf implementation jar files and providing them as part of WEB-INF\lib and changing the classloader to PARENT_LAST, the application was working fine.
For websphere 7.0, I can't seem to get the application working. It always picks up the Sun's JSF implementation. I've also tried the shared library concept but to no success.
Regards,
Zahir
The Oracle documentation lists a certification for WAS 7.0.0.13 ND. So you need FixPack 13 or later.
As the WebSphere Application Server 7 is a full blown JEE5 server it requires/has JSF 1.2 support. You can switch between the built in Sun and MyFaces implementation if required.
You should probably make sure that the ADF version you are using is certified for WAS 7. The ADF release notes tell that ADF supports JSF 2.0. The WAS 7 only comes with JSF 1.2. Exchanging the JSF version with placing the JSF 2 libs into WEB-INF/lib works well for our projects in conjunction with the 'PARENT_LAST' classloading policy. Make sure that you set the policy either for the whole application or for both the application and the web module.
ADF Faces is a Java based framework and it will run on WebSphere but, you have to add the required libraries first. The easiest way to prepare WebSphere to run ADF Faces application is through JDeveloper. Alternatively, you can google Oracle JRF (Java Runtime Framework) and install that on your WebSphere, before running the ADF Faces application.
I have developed a JSF 2.0 application and tested it on Apache Tomcat 6.0. The problem is that the official server can only have version 5.5 installed. So I tried to deploy it as it was but I kept getting the JasperException. I figured out that the problem probably lies with the standard.jar and jstl.jar. How can I deploy it then? How to downgrade the application?
Thanks for any help, links or tutorials.
Best Regards.
JSF2.0 requires Tomcat 6.0 or later.
If you use the JSF-RI 1.2, you can run JSF 1.2 with tomcat 5.5
EDITED:
I read that in version 5.5.20 it doesn't work properly. Tomcat 5.5.17 and Tomcat 5.0.28 are fine with JSF1.2
I have used Mojarra 2.0.3-b03 on Tomcat 5.5.28 and it works well so far. All basic facelet tags work fine so far (h:dataTable, f:ajax, etc.)
Currently trying to use RichFaces 4 (still under development though) but seems lot of components not ready yet.