After a long time, again i started GXT coding, upgrading old application with new versions of GXT & GWT. When i replaced gxt 3.x jar with 2.x, got so many errors, thought all are related to imports, but most of the panels, layouts, multiselectcombo, models and checkboxlistview not there. Expecting favorable response from members.
Here you'll find informations about the migration from GXT 2.x to GXT 3.x:
Migration Guide
Hope that helps.
Related
I have installed intellij IDEA Ultimate Edition latest version and started to test the compatibility of it with primefaces version 6.2.
If it could be compatible with primeface we are gonna switch from eclips to intellij.
unfortunatly i cann't figure out how to get code autocomplition to work for primefaces.
I have done alreaday the following.
created maven project.
added primeface dependency in pom.
Added primeface framework by right clicking on the project and choosing Add framework support....
Does any one know how to fix this issue?
Does anyone know the best IDEA for working with primeface?
I did solve it by the following. I got inspiration from here.
Added primeface framework by right clicking on the project and choosing Add framework support....
Added JSF facet to my web modules from File | Project Structure | Modules - module - JSF facet Ctrl+Shift+Alt+S
Restarting intellij IDEA
Quickly looking into this issue revealed this link, https://www.jetbrains.com/help/idea/preparing-for-jsf-application-development.html.
The website states that in order to enable support for JSF development, you need the Ultimate edition.
I would suggest taking a look at NetBeans. It is continuously developed alongside new implementations of Java EE (and soon Jakarta EE) and is therefore the go-to IDE environment for JavaEE development. Everything works pretty much out of the box.
Can RichFaces (either 3.x or 4.x) and PrimeFaces (either 3.5 or 4.0) be used in the same JSF 2.x application? Will they coexist nicely?
My goal is migrating from RichFaces 3.x to PrimeFaces. I would like to start by using PrimeFaces for a new submodule of my web application, and eventually migrate everything.
It would be fairly easy to set up a simple hello-world sized project and try it out; I am asking here because I wish to know if there are some problems when doing this on real-life sized projects.
I'm using java 1.7_07 which include javafx 2.2.1.
When I try to import the package javafx.scene.control.Pagination Netbeans doesn't find it. The class is present in the API documentation, I can't see the reason.
Check your javafx version: How to get the version number of JavaFX?
You may use Java Platform in NetBeans settings being setup to older JavaFX and Pagination is a relatively new control.
Our project currently uses the very old Java Studio Creator framework and now has new requirements and plans for future deployments which require the application to finally remove JSC and migrate to either 1.8.x or 2.0 of IceFaces.
A migration to 1.8.x seems to be the safest and most reliable option to take to me. Would delaying and not taking on the challenge of a migration JSF 2.0 make sense or should a migration directly to IceFaces 2.0 be used instead?
That <webuijsf:xxx> component library is called "Woodstock". Now you have new and solid keyword. ICEFaces was officially been pointed as recommended replacement of Woodstock projects when Woodstock was officially been abandoned and discontinued.
Woodstock to ICEFaces migration
Woodstock to ICEFaces porting guide
Woodstock to ICEFaces component migration matrix
ICEFaces 2 tutorials and examples
I personally recommend you to just take the ICEFaces migration path. It's well documented. Also, when you migrate to "plain" JSF 2.0, you'll have to redo the entire look'n'feel as "plain" JSF components does not ship with any bundled CSS. Going to ICEFaces 1.8 or 2.0 doesn't really matter that much. To take advantage of new JSF 2.0 features behind ICEFaces 2.0 you'll only have to change a lot of other things afterwards, but even without that, you should already have a working project.
I'm fairly new to JSF and Richfaces.
I'm looking to upgrade our system from JSF 1.1.2 to the latest 2.0. Also looking at upgrading our Richfaces 3.0 to 3.3
Under the lib folder for old projects we currently have the following:
ajax4jsf-1.1.1.1.jar
commons-beanutils-1.7.0.0.jar
commons-collections-3.3.1.0.jar
commons-digester-1.6.0.0.jar
commons-logging-1.1.1.0.jar
jsf-api-1.1.2.0.jar
jsf-facelets-1.1.12.0.jar
jsf-impl-1.1.2.0.jar
jstl-1.1.2.0.jar
richfaces-3.0.1.1.jar
This is what I have added:
richfaces-api-3.3.3.Final (Added)
richfaces-impl-3.3.3.Final (Added)
richfaces-ui-3.3.3.Final (Added)
So what I'm looking for is info on what Jars I can remove and what Jars I'm missing that need to be added.
Thanks
Hmm, before talking about the libs... What's your goal using jsf 2.0 and rf 3.3? I am asking because rf 3.3 does not really make use of jsf 2.0. As the jsf 2.0 roadmap for richfaces says
The goal of JSF 2.0 support in the 3.3.3 release is to run your existing RichFaces 3.3.X applications in a JSF 2.0/EE6 environment with little or no changes.
See this link: jsf 2.0 roadmap for richfaces
OK, back to your libs... I don't remember them by heart, but at least you should change jsf-api and jsf-impl to 2.x versions and drop the old stuff. I would have a look at a rf 3.3 demo project, what is contained there.
You can also just use RichFaces Maven archetype and create a project with everything you need.