5.3 to 6.x
-
- Posts: 2
- Joined: 05 Apr 2016, 03:53
Que tengo que setear para migrar de primefaces 5.3 a 6.x pero quisiera que fuesen mas especificos y que no me envien a la guia, por favor.
Puedes consultar la guía de Github: https://github.com/primefaces/primeface ... tion-Guide
Atentamente,
Atentamente,
-
- Posts: 2
- Joined: 05 Apr 2016, 03:53
En la guia solo dice
5.3 to 6.0
If manually included, the primefaces.js include must be changed to include core.js and components.js
The same also applies for the MenuRenderers of all PrimeFaces Layouts (before new layout versions will be released). Please change
@ResourceDependency(library="primefaces", name="primefaces.js")
to
@ResourceDependency(library="primefaces", name="core.js"), @ResourceDependency(library="primefaces", name="components.js")
Following components were migrated from PrimeFaces Extensions to PrimeFaces:
InputNumber
Timeline
Knob
KeyFilter
ImportConstants
ImportEnum
ImportConstants: className has been renamed to type
Search Expressions: SEF was refactored to skip unrendered components per default. If you would like to search for unrendered components in your application, please pass SearchExpressionFacade#Options#VISIT_UNRENDERED as option.
"last" facet for resources: before 6.0, it was possible to use the last facade inside any tag to add resources. We never implemented this feature so it was just a random feature as the facet always belongs to the direct parent. Please use the "last" facet only in h:head.
Dynamic Resource Loading: We reimplemented this feature, so that it will even work for other libraries like PrimeFaces Extensions. If you dynamically add components via Java code, please make sure you create the component via the #createComponent API:
ColorPicker colorPicker = (ColorPicker) FacesContext.getCurrentInstance().getApplication().createComponent(ColorPicker.COMPONENT_TYPE);
instead:
ColorPicker colorPicker = new ColorPicker();
Per default, DataTable now skips processing child components for some events like paging. If you need child processing, you can set skipChildren="false" on p:ajax.
GMap Rectangles: SouthWest and NorthEast was rendered the wrong direction. You probably need to switch the constructor parameters of LatLngBounds now.
ContextMenu: p:contextMenu must be placed AFTER the target component (e.g. datatable) in the xhtml now.
CommandButton: onclick will not be rendered if disable is set to false. This may cause unexpected behavior if the component is enabled on the client.
pero donde tengo que hacer el cambio? favor ser mas especificos
5.3 to 6.0
If manually included, the primefaces.js include must be changed to include core.js and components.js
The same also applies for the MenuRenderers of all PrimeFaces Layouts (before new layout versions will be released). Please change
@ResourceDependency(library="primefaces", name="primefaces.js")
to
@ResourceDependency(library="primefaces", name="core.js"), @ResourceDependency(library="primefaces", name="components.js")
Following components were migrated from PrimeFaces Extensions to PrimeFaces:
InputNumber
Timeline
Knob
KeyFilter
ImportConstants
ImportEnum
ImportConstants: className has been renamed to type
Search Expressions: SEF was refactored to skip unrendered components per default. If you would like to search for unrendered components in your application, please pass SearchExpressionFacade#Options#VISIT_UNRENDERED as option.
"last" facet for resources: before 6.0, it was possible to use the last facade inside any tag to add resources. We never implemented this feature so it was just a random feature as the facet always belongs to the direct parent. Please use the "last" facet only in h:head.
Dynamic Resource Loading: We reimplemented this feature, so that it will even work for other libraries like PrimeFaces Extensions. If you dynamically add components via Java code, please make sure you create the component via the #createComponent API:
ColorPicker colorPicker = (ColorPicker) FacesContext.getCurrentInstance().getApplication().createComponent(ColorPicker.COMPONENT_TYPE);
instead:
ColorPicker colorPicker = new ColorPicker();
Per default, DataTable now skips processing child components for some events like paging. If you need child processing, you can set skipChildren="false" on p:ajax.
GMap Rectangles: SouthWest and NorthEast was rendered the wrong direction. You probably need to switch the constructor parameters of LatLngBounds now.
ContextMenu: p:contextMenu must be placed AFTER the target component (e.g. datatable) in the xhtml now.
CommandButton: onclick will not be rendered if disable is set to false. This may cause unexpected behavior if the component is enabled on the client.
pero donde tengo que hacer el cambio? favor ser mas especificos
-
- Posts: 11
- Joined: 23 Apr 2012, 17:58
Pues si, si la guía lo dice, entonces es solo eso.
Nosotros migramos hace un tiempo y no se rompió nada.
Si debes cambiar (como dice la guia) la forma de resolver las librerías, y ya está
Actualiza tu librería, y pruébalo.
Nosotros migramos hace un tiempo y no se rompió nada.
Si debes cambiar (como dice la guia) la forma de resolver las librerías, y ya está
Actualiza tu librería, y pruébalo.
-
- PrimeFaces Core Developer
- Posts: 3979
- Joined: 03 Dec 2010, 14:11
- Location: Bavaria, DE
- Contact:
use english plz.
Thomas Andraschko
PrimeFaces | PrimeFaces Extensions
Apache Member | OpenWebBeans, DeltaSpike, MyFaces, BVal, TomEE
Sponsor me: https://github.com/sponsors/tandraschko
Blog: http://tandraschko.blogspot.de/
Twitter: https://twitter.com/TAndraschko
PrimeFaces | PrimeFaces Extensions
Apache Member | OpenWebBeans, DeltaSpike, MyFaces, BVal, TomEE
Sponsor me: https://github.com/sponsors/tandraschko
Blog: http://tandraschko.blogspot.de/
Twitter: https://twitter.com/TAndraschko
-
- Posts: 1
- Joined: 16 Nov 2018, 00:58
La gente parece tonta o se hace, o simplemente no quiere ayudar a los demás, deben ser los típicos amargados que tienen miedo a la competencia, malos programadores, en fin, como dice el post principal, no es facil, porque en la guia por ejemplo dice :
Yo estoy en plena migracion de 5.3 a 6.0 , luego seguiré subiendo versiones hasta el 6.2. pásame tu correo electronico por privado y te digo como lo hice y me funcionó, pero como estos no te queiren ayudar, yo igual no voy a darles la información, que se busquen la vida, per oa ti si te voy ayudar men.
y para el que dice en ingles, "use traslator from google "
lo cual no hay en el proyecto ese @ResourceDependency, en fin.Please change
@ResourceDependency(library="primefaces", name="primefaces.js")
to
@ResourceDependency(library="primefaces", name="core.js"), @ResourceDependency(library="primefaces", name="components.js")
Yo estoy en plena migracion de 5.3 a 6.0 , luego seguiré subiendo versiones hasta el 6.2. pásame tu correo electronico por privado y te digo como lo hice y me funcionó, pero como estos no te queiren ayudar, yo igual no voy a darles la información, que se busquen la vida, per oa ti si te voy ayudar men.
y para el que dice en ingles, "use traslator from google "
-
- Information
-
Who is online
Users browsing this forum: No registered users and 48 guests