SOAP 和 REST Web 服务在 Java EE 中具有一种实现

发布于 2024-11-26 20:29:19 字数 382 浏览 1 评论 0原文

是否有可能（Java EE、JBoss 6）巧妙地注释 Java 代码以提供 RESTful 和 SOAP Web 服务，而无需实现两种方法？

我在想：

@Local
@Path("/service")
@WebService
public interface SomeService {
    @GET @Path("somemethod")
    @WebMethod
    public String someMethod (@QueryParam("s") String someParam);
}

请注意两者@Path和@WebService注释（不幸的是，上面的示例不起作用）。

原文

Is it possible (Java EE, JBoss 6) to cleverly annotate Java code to provide both RESTful and SOAP webservices without implementing two methods?

I'm thinking about:

@Local
@Path("/service")
@WebService
public interface SomeService {
    @GET @Path("somemethod")
    @WebMethod
    public String someMethod (@QueryParam("s") String someParam);
}

Please notice both @Path and @WebService annotations (above example does not work unfortunately).

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

各自安好 2024-12-03 20:29:19

虽然 JAX-WS 和 JAX-RS 注释可以非常愉快地在相同的方法上共存，但我发现很难相信任何经过精心调整以与 JAX-RS 一起使用的接口都可能非常适合 JAX-WS，或者 < em>反之亦然。问题不是你不能做，而是你不应该做；他们对世界有不同的模型，对于良好界面的含义也有不同的概念。

但是，如果您只是做一些琐碎的事情，例如简单的查找，它确实可以工作：

@GET
@Path("foo/{id}")
@Produces("application/xml")
@WebMethod(operationName = "DescribeFoo")
@WebResult(name = "Description")
public DescriptionOfFoo getFooDescription(
        @PathParam("id")
        @WebParam(name = "fooId")
        String id) {
    return get_the.description_of(id); // Whatever...
}

不过，我喜欢在接口上放置尽可能多的东西（检查您的框架文档以了解如何使它们工作），因为这会减少上述部分（!!）可能的注释集下降到更合理的级别。（作为参考，当事情开始变得复杂并且您在不平凡的模式中应用多个方面时，您可以轻松地为每个方法获得超过 20 个注释，其中一些与您的实现相关，一些与一个或另一个相关界面的划分可以促进理智。）

While JAX-WS and JAX-RS annotations can quite happily cohabit on the same methods, I find it hard to believe that any interface that is well-tuned for use with JAX-RS could be a good fit for JAX-WS, or vice versa. The problem isn't that you can't do it, the problem is that you shouldn't; they have a different model of the world, a different concept of what it means to be a good interface.

But if you're just doing something trivial like a simple lookup, it can indeed work:

@GET
@Path("foo/{id}")
@Produces("application/xml")
@WebMethod(operationName = "DescribeFoo")
@WebResult(name = "Description")
public DescriptionOfFoo getFooDescription(
        @PathParam("id")
        @WebParam(name = "fooId")
        String id) {
    return get_the.description_of(id); // Whatever...
}

I like to put as much as I can on interfaces though (check your framework documentation for how to make them work) as that reduces the above partial (!!) set of possible annotations down to a more sensible level. (For reference, when things start to get complicated and you're applying multiple aspects in non-trivial patterns, you can easily get to over 20 annotations per method, some of which relate to your implementation and some of which relate to one or other of your interfaces; partitioning promotes sanity.)

回复收藏 0 原文