I have the project which is designed and developed on very legacy frameworks. The frameworks which we are currently using are:
jboss-seam-2.2.1.jar
jsf-api-1.2_04-p02.jar
jsf-facelets-1.1.14.jar
jsf-impl-1.2_04-p02.jar
richfaces-impl-3.2.1.GA.jar
These are quite old frameworks, may be around 12 years old or more.
Now, we are planning to upgrade these version to the latest stable version of the frameworks.
The question is, can we directly move from jsf1.2 to jsf 2.3 ? I don't see any documentation or reference for this migration.
Along with JSF upgrade what all are the components we may need to upgrade? Any Direction ?
Thanks in advance!!!
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
I want to use OpenAM 12.0.0 for authentication with Liferay 6.2 but I could not find any documentation on how to do that? Thanks.
https://wikis.forgerock.org/confluence/display/openam/integrate+OpenAM+with+Liferay
http://www.kianworknotes.com/2013/02/how-to-integrate-openam-with-liferay.html
Hope this helps and get to moving. Cheers! :)
I would like to ask a question about wether or not I should do the migration to Liferay 6.2.
Me and my team are working since 4 month on a portal quite big developed with Liferay 6.1 (CE edition) and now, since the project publication date is still 4-5 month ahead (so I do have time), I was wondering if doing the migration to 6.2 now is a good choice.
I already tried the new version and I must say I am impressed about the new features and since now I haven't find any bugs.
Anyone had any experience on developing portlet/themes on Liferay 6.2? Is is worth it to do the migration now or shall I wait for the next ga2 release?
Any suggestion is very welcome.
Thanks
Depends mostly on the kind of work you've done on that portal. Even slight upgrades in Liferay, can have major differences in the source code. If this affects the work you've done, it will affect the upgrade too. For example, things will get difficult to update if :
You have developed custom portlets, as they will need recompilation for the new runtime
Developed Portlets that use ServiceBuilder might need more work than just a recompilation
Using Hooks (even simple jsp hooks) might need re-writing. ext hooks will almost certainly need to, and it can become a major pain
On, the other hand, if most of your work had to do with light theming and content management, it could become an relatively easy and painless upgrade.
In any case, make sure to keep a backup of your Liferay Database, because once you upgrade, there is no way to downgrade back to the initial version.
As you're using CE, my recommendation is to upgrade as soon as possible. Reason is that there are no more updates for 6.1, now that 6.2 is out. If you're going live in 5 months, you'd be on a version that's unsupported for half a year at the date of publication.
The alternative is to go to EE, which is supported for ~5 years from release, e.g. you'll have several years of support in front of you. However, as Liferay is paying my salary, note that I might be biased...
Of course, being unsupported "by Liferay" does not mean that you won't be able to fix any bugs or issues, but you'll have to do this on your own, and sooner or later you should upgrade anyway... If you're not yet live, I'm recommending to do it sooner.
Liferay 6.2 does not (yet) support as many marketplace apps as Liferay 6.1. Also Liferay 6.2 CE has bugs, and patches are available only to EE subscribers; this forced us to use Liferay 6.1 CE instead of 6.2 CE.
You will have issues if you are using the Vaadin framework under Liferay.
Liferay 6.2 CE does not support Vaadin out of the box ... it is delivered with Vaadin 6.8, but it is broken - your portlet code will break.
You would have to consider moving to Vaadin 7.1 at best ... and that is a non-trivial code migration as many items have been deprecated between 6.8 and 7.
I went that route and the learning curve was unexpectedly steep.
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.