You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README
+11-8Lines changed: 11 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -67,28 +67,31 @@ To upgrade your existing Grails projects you must run "grails upgrade" for each
67
67
68
68
There are some unavoidable issues that may affect you when upgrading to 0.5 from a previous version:
69
69
70
-
1. Your custom taglibs that call other tags will need to be changed. Tags called from within a tag now return a string containing the content instead of writing to out, so you must do something like:
70
+
1. If you have an old default index.jsp, it will not function correctly due to a change in a property name. Remove the file if you have not customized it, or change the reference to the "controllers" property to "controllerClasses"
71
+
72
+
2. Your custom taglibs that call other tags will need to be changed. Tags called from within a tag now return a string containing the content instead of writing to out, so you must do something like:
71
73
72
74
out << theOtherTag(attrs)
73
75
74
-
2. Your taglibs, if they call their own closures as if they are methods, will not function correctly if the closure has less than 3 arguments. Change such code to:
76
+
3. Your taglibs, if they call their own non-tag closures as if they are methods, will not function correctly if the closure has less than 3 arguments. Change such code to:
75
77
76
78
yourClosureName.call(args)
77
79
78
-
3. Tag bodies return strings instead of writing to out, so you must change code that calls body() to:
80
+
4. Tag bodies return strings instead of writing to out, so you must change code that calls body() to:
79
81
80
82
out << body()
81
83
82
-
4. View loading mechanisms have changed, so if you need to load a view directly or check for its existence, you must now use a resource loader:
84
+
5. View loading mechanisms have changed, so if you need to load a view directly or check for its existence, you must now use a resource loader:
0 commit comments