关于 Spring Web MVC 应用程序中简单 StringTemplate 视图解析的建议？
我正在将 Spring MVC 应用程序从 Tiles/EL 视图分辨率设置迁移到 StringTemplate 视图分辨率设置。根据我到目前为止的调查，我收集了两种可能的方法：
1）对于需要解析的每个视图，有 1 个处理布局的文件，即：
$layout/layout(content=exampleContent())$
和另一个实际提供内容的文件（上面的 exampleContent() ）：
<h1>Hello world!</h1>
<a href="#">This a link</a>
这种方法看起来很简单，但令人烦恼的是，对于大多数视图，我们必须创建 2 个文件。理想情况下，我们希望大多数视图只需要创建 1 个文件。
2) 另一种方法是使用 StringTemplateGroups。我对它们还不是很熟悉，但它们似乎可以用于处理布局分辨率。与上述方法相比，这对我来说吸引力稍差一些，因为我们不仅必须为每个视图编辑 2 个文件，而且除基本 StringTemplate 语法之外，这 2 个文件还需要学习 StringTemplateGroup 语法。我希望学习曲线尽可能平坦，认知负荷尽可能低。
想法？我对 StringTemplateGroups 完全没有根据吗？有没有我不知道的更简单的解决方案？感谢您的任何反馈:)
I'm migrating my Spring MVC app from a Tiles/EL view resolution setup to a StringTemplate view resolution setup. From my investigation so far I've gathered there are 2 possible approaches:
1) For each view that needs to be resolved, have 1 file which handles layout, i.e:
$layout/layout(content=exampleContent())$
and another file which actually provides the content (exampleContent() above):
<h1>Hello world!</h1>
<a href="#">This a link</a>
This approach seems simple enough, but it's annoying that for most views that we would have to create 2 files. Ideally we would like for most views to only require creating 1 file.
2) The other approach would be to use StringTemplateGroups. I'm not very familiar with them yet, but it seems like they could be used for handling layout resolution. This is a little bit less appealing to me than the above approach because not only would we have to edit 2 files for each view, but on top of that the 2 files would require learning StringTemplateGroup syntax in addition to basic StringTemplate syntax. I'd prefer to keep the learning curve as flat as possible and the cognitive load as low as possible.
Thoughts? Am I totally off-base about StringTemplateGroups? Is there an even simpler solution that I don't know about? Thanks for any feedback :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您使用了聪明的视图解析策略，您将只需要更新字符串模板组文件。如果逻辑视图名称设置为“path/to/stringtemplate/file/desiredtemplate”，您可以提取 stringtemplate 文件名、所需模板并填充模型中的属性。
听起来 StringTemplateGroup 是网络应用程序的最佳选择。
If you used a clever view resolution strategy you would only ever need to update the string template group files. If the logical view name was set to "path/to/stringtemplate/file/desiredtemplate" you could extract the stringtemplate file name, the desired template and populate the attributes from the Model.
It sounds like StringTemplateGroup is your best bet with a web app.