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
Currently it is pretty unclear which features of Rythm are fully supported and which PlayRythm features are supported. Is there a roadmap which PlayRythm features are supposed to be migrated to Spring MVC?
As a sidenote, is there a particular reason why PlayRythm has @msg(...)/&(...) for i18n and this project uses @message?
The text was updated successfully, but these errors were encountered:
Rythm Templat Engine features is fully supported e.g. @extends, @args, @section, etc..., but do not cover PlayRythm supported features e.g. &{i18n.code} or @url(Application.index), because Play Framework has many magic features and very hard to implement those in Spring Framework.
For the @message is not match PlayRythm i18n @msg syntax. Solution is create a JavaTag and extends com.ctlok.springframework.web.servlet.view.rythm.tag.Message then override getName() method to return "msg" and register in Rythm Engine. Next version may be support @message and @msg syntax for i18n message.
I will create a document for developer to know which Rythm Template Engine features is supported and help developer easily migrate form Play Framework to Spring Web MVC.
Currently it is pretty unclear which features of Rythm are fully supported and which PlayRythm features are supported. Is there a roadmap which PlayRythm features are supposed to be migrated to Spring MVC?
As a sidenote, is there a particular reason why PlayRythm has
@msg(...)/&(...)
for i18n and this project uses@message
?The text was updated successfully, but these errors were encountered: