有关 JAX-RS 框架及其客户端实现的文书工作
我读了 Bill Burkes 的书“Restful Java with JAX-RS”（2009），当他写关于框架（RESTEasy、Apache CXF、Jersey）的文章时，特别是关于支持客户端实现的框架时，他说：
有很多 JAX-RS 规范领导和专家组成员感兴趣，以获得 融入 JAX-RS 2.0 的标准化客户端框架。
我说的对吗，目前还没有标准化的客户端框架？会有吗？
我考虑写一篇 60 页长的作品，讨论客户端实现方面的不同框架。最后也许是一个自己实现的原型，其中有一些好的想法。您认为这是一个值得讨论的好问题吗？您知道我在这次讨论中还可以考虑什么吗？
I read Bill Burkes book "Restful Java with JAX-RS" (2009) and when he wrote about frameworks (RESTEasy, Apache CXF, Jersey), specially about frameworks which support the client side implementation, he said:
There is a lot
of interest from the JAX-RS specification lead and expert group members to get a
standardized client framework baked into JAX-RS 2.0.
Am I right when I say, there isnt a standardized client framework yet? Will there ever be one?
I thought about writing a 60 pages long work about the different frameworks with regard to client side implementation. At the end maybe a prototype of an own implementation, with some good ideas. Do you think it's a good issue to discuss about? Do you have ideas what else I could consider in this discussion?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为，你需要非常清楚这样一篇论文的目标是什么。 IE。你的发现的有趣应用是什么。
例如，您打算将其作为输入提交给 JAX-RS 规范委员会，还是将其作为解决方案架构师的白皮书甚至科学论文发布？如果不是，那么我同意 Donal Fellows 的观点，即 60 页太多了，否则您可能需要更多的内容来建立您的方法、描述实验（包括它们与目标的关系）、分析您的发现等等在。如果你也想尝试自己创建一个客户端框架，那么你很快就会接近研究生论文的延伸......
另一方面，我确定，我们有很多实践者，他们不愿意尽可能长时间地拥抱 JAX-RS，因为没有成熟的方式来使用它使我们能够生成的服务。然而，应该可以以比 60 页报告更容易理解的形式评估不同的选项。
如果您决定继续就此发表某种论文，我（也？）也会有兴趣看到结果。
另外，我很好奇是否有任何 JAX-RS 框架支持基于从服务器传递的 URI 模板的运行时绑定的“动态”客户端。
I think, you need to be very clear on what the objective of such a paper would be. Ie. what the interesting application of your findings would be.
Do you e.g. intend to submit it as input to the JAX-RS specification board, or publish it as a white-paper for solution architects or even as a scientific paper? If not, then I agree with Donal Fellows on that 60 pages is way too much, and that you otherwise probably will need more than that to establish your methodology, describe the experiments including how they relate to the objective, analyse your findings, and so on. And if you also want to try your own hand in creating a client framework, then you will quickly come close to the extend of a postgraduate thesis...
On the other hand, am I certain, that we are many practitioners, who are reluctant to embrace JAX-RS as long, as there are no mature ways of consuming the services it enable us to produce. It should however be possible evaluate the different options in a more accessible form than a 60-page report.
If you decide to go ahead with making some sort of paper about this, I (too?) will be interested in seeing the result.
Also, I am curious of, whether any of the JAX-RS frameworks supports "dynamic" clients based on runtime binding of URI templates delivered from the server.