用于细分和整合的 UI 技术（门户替代方案）
我正在寻找一种最好基于 Java 的技术，该技术能够：
- 分离开发人员之间的开发任务，并且不需要他们访问所有 UI 来进行开发和测试。我想创建单独的小组，由他们自己开发用户界面。
- 将最终结果合并为一个连贯的应用程序。
是的，我知道，这就是门户和 portlet 容器的用途，但是我正在寻找替代技术解决方案 - 如果有的话。
例如，我可以想到以下内容：
- Spring MVC 在范围上有明确的分离和“聪明”的合并过程
- Struts 操作和页面在范围上有明确的分离并配置合并
更新：我还没有指定更多的要求，但我需要 SEO、友好的 url，并且不考虑 Wicket（因为很难找到开发人员）和 JSF（因为它有我不喜欢的限制）。
I'm looking for a preferably Java-based technology that is able to:
- Separate development tasks between developers and does not requires them to access all the UI for development and testing. I'd like to create separate groups who develop the UI on their own.
- Consolidate the end results as a coherent application.
Yeah, I know, this is what portals and portlet containers are for, however I'm looking for alternative technology solutions - if there is any.
For example I can think of the followings:
- Spring MVC with clear separations on the scopes and "clever" merge process
- Struts actions and pages with clear separations on the scopes and merge of the configuration
Update: I haven't specified a few more requirements, but I need SEO, friendly urls, and do not consider Wicket (because it is hard to find developers) and JSF (because it has limitations I do not like).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们使用 Vexi - 这里是 演示 - 取得了很大成功，主要是因为我们维护了它。文档相当详尽，但目前在线组织得不够好，并且由于 Sourceforge 的更改，该网站已损坏（感谢 SF.net）。
SEO 并不是真正的功能，因为应用程序是从浏览器“启动”的，而不是存在于浏览器内部。但这绝对是一种替代技术！
很遗憾我无法向您展示我目前正在开发的应用程序，因为它们看起来很棒。不过，我们对 Vexi 的在线资料很糟糕。
We use Vexi - here's a demo - with a lot of success, mainly because we maintain it. Documentation is fairly thorough but not well organized online at the moment and the website is broken due to Sourceforge changes (thanks SF.net).
SEO is not really a feature because the applications 'launch' out of the browser rather than exist inside them. However it is definitely an alternative technology!
It's a shame I can't show you the apps I'm working on at the moment, because they look great. Our online profile for Vexi is dire though.
我得出的结论是，我们的方式将基于 SpringMVC， 进一步的讨论可能会在 Spring 论坛上继续
I've concluded that our way would be SpringMVC-based, further discussion might continue at Spring forum