Gan...@j4fry.org
unread,Feb 3, 2009, 3:12:17 AM2/3/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to j4fry
This thread was moved from our old sourceforge forum:
Upgrading from MyFaces 1.1.5 to JSF 1.2 RI
By: ganesh (ganeshpuriProject Admin) - 2008-03-25 04:21
Hi,
When upgrading the example project I encountered 7 issues:
- Using the same tag attribute for a JSF tag twice was silently
ignored with 1.1.5 and now throws an exception with 1.2
- Using less columnClasses than columns in a panelGrid rendered the
remaining columns without CSS class with 1.1.5 and now repeats the
columnClasses for the remaining columns with 1.2
- MyFaces 1.1.5 rendered either a name or and id attribute for each
tag, so scripts could always identify them. 1.2 RI renders
commandLinks with neither name nor id, imposing minor scripting
changes.
- MyFaces 1.1.5 updated the model with null, when a radio button not
clicked and the bean property is a String, the 1.2 RI updates with
"".
- 1.2 RI writes an exception stacktrace to the log when a phase
listener throws a bug. MyFaces 1.1.5 was silently ignoring them.
- When a bean implemented Map and a bean property was set through DI
in faces-config, MyFaces 1.1.5 called Map.put(). 1.2 RI doesn't, so
implementing a separate setter for upgrading was necessary.
- When a property of a bean in session scope is set through DI (faces-
config) and the property is a bean in request scope this would
silently upgrade the ssecond beans life to session scope. MyFaces
1.1.5 would ignore this while 1.2 RI throws an exception.
Greetz,
Ganesh