Java Help

[Aashiqui]

Bhayya i need small help eppudu nannu project lo migrate cheyamanru prime faces 3. to 5.0 so other than jar upgrade code side emi cheyali ela cheyali koncham inputs cheppara... bec i didnt do any migration till now... Thanks in advance..!

[spidereddy]

ltt

[spidereddy]

java guys..come here n help this kid

[MeetFriendz]

ltt

[RunRaajaRun123]

Upgrade lo code chnages em undav max

Aa kotha upgrade lo konni methods deprciate konni emo errors throw chesthaayi avi kotha jar ki compatoble ga change cheyytame untadhi anukunta max

I have onlu 2 yrs exp naku telsindhi cheppa

[ZuniorVentiyar]

underlaying JSF version enti??????? it based on JSF version also .... 

 

 

Primefaces provide detailed migration guild for each relese follow that ... u r on 3.5 .... u have to check 4.X version and 5.x version migration points ....

 

Also if you are using elite version of primefaces ... mail them asking about check list for migration or if you are using opensource version check migration guild below 

 

 

https://code.google.com/p/primefaces/wiki/MigrationGuide

[worstandhra]

Bhayya i need small help eppudu nannu project lo migrate cheyamanru prime faces 3. to 5.0 so other than jar upgrade code side emi cheyali ela cheyali koncham inputs cheppara... bec i didnt do any migration till now... Thanks in advance..!

 

Start building using the Maven POM.

First try to upgrade the pom.xml with PrimeFaces Version 5.0

Make sure you remove the old jars. Build with new pom.xml

Once all the jars are pulled by Maven (from Nexus source), automatically the Eclipse will show the compilation errors.

 

How ever fixing all the compilation errors will not ensure a stable build.

Mostly the deployment will fail. Most of them are fixed by removing old jars or adding new jars. 

[worstandhra]

Bhayya i need small help eppudu nannu project lo migrate cheyamanru prime faces 3. to 5.0 so other than jar upgrade code side emi cheyali ela cheyali koncham inputs cheppara... bec i didnt do any migration till now... Thanks in advance..!

 

Most probably the following will be affected:

1. Hibernate, if the present version of Hibernate you are using is not compatible with PrimeFaces 5.0

2. Mostly you will need JSF2.0 which come with its own jars, so a JAR conflict will occur and you should be resolve them.

3. validation framework needs some code changes and if you can Google using the error text, you can easily find the solutions

4. Front-end side, I believe you may need upgrade of jQuery versions as well.

[ZuniorVentiyar]

wat hibernate does with Primefaces bhayaa .... theluskundam ani adigaa ....

Most probably the following will be affected:

1. Hibernate, if the present version of Hibernate you are using is not compatible with PrimeFaces 5.0

2. Mostly you will need JSF2.0 which come with its own jars, so a JAR conflict will occur and you should be resolve them.

3. validation framework needs some code changes and if you can Google using the error text, you can easily find the solutions

4. Front-end side, I believe you may need upgrade of jQuery versions as well.

 

[worstandhra]

wat hibernate does with Primefaces bhayaa .... theluskundam ani adigaa ....

 

Yeah, most of the Java-based projects have some sort of Persistence Layer. In this case there is no possibility of Spring DAO.

Since its JSF PrimeFaces, mostly the persistence Layer will be by Hibernate though there are other versions of JPA that can be integrated.

[VenkatD]

wat hibernate does with Primefaces bhayaa .... theluskundam ani adigaa ....

Gud question ... Lttt

[ZuniorVentiyar]

sorry neenu adigindhi ... primefaces upgarde ki hibernate layer tho (pesistance layer) endhuku compatability issues vosthayi ani adiga .. based on u r point below 

 

1. Hibernate, if the present version of Hibernate you are using is not compatible with PrimeFaces 5.0 --???????

 

 

Yeah, most of the Java-based projects have some sort of Persistence Layer. In this case there is no possibility of Spring DAO.

Since its JSF PrimeFaces, mostly the persistence Layer will be by Hibernate though there are other versions of JPA that can be integrated.

 

[ZuniorVentiyar]

hibernate just merely required an entity to work..... you will createJPA / Hibernate  entity based on u r business logic ....  I don't see any integration point between persistence layer and presentation layer ????? 

 

am I miss anything bhayaaa???

 

Yeah, most of the Java-based projects have some sort of Persistence Layer. In this case there is no possibility of Spring DAO.

Since its JSF PrimeFaces, mostly the persistence Layer will be by Hibernate though there are other versions of JPA that can be integrated.

 

[worstandhra]

sorry neenu adigindhi ... primefaces upgarde ki hibernate layer tho (pesistance layer) endhuku compatability issues vosthayi ani adiga .. based on u r point below 

 

1. Hibernate, if the present version of Hibernate you are using is not compatible with PrimeFaces 5.0 --???????

 

Yeah, got the question. Hibernate 4 differs from its previous versions in lot many ways.

As far as I remember, when passing parameters, it is strict w.r.t Char, String formats.

Also I think the Hibernate 4 Criteria params will only accept java.sql.Date instead of java.util.Date.

As far as I remember its all to do with DataTypes but are very easy to fix. 

 

Yeah, I got it, My arg is wrong. Even though you migrate to PrimeFaces 5.0, mostly it will give backwards compatibility from hibernate 4 to 3 to some of its previous versions as well.

[worstandhra]

hibernate just merely required an entity to work..... you will createJPA / Hibernate  entity based on u r business logic ....  I don't see any integration point between persistence layer and presentation layer ????? 

 

am I miss anything bhayaaa???

 

Hmmmm...ledhu boss.

Hibernate represents your whole of the DB in terms of Java.

So lot of conversion/re-conversions needed. Also Transaction-Management, caching plus lots others...