低开销 Java Web 服务容器？
我想提供基于 Java 的 Web 服务，但不需要成熟的 J2EE 应用程序服务器的功能。我希望它尽快启动，尽管这不是一个硬性要求。 Web 服务将处理多个连接并需要访问 Oracle 数据库，因此它至少需要一个线程池和数据库连接池。稍后我可能想在上面放一个JSP接口，以提供内部维护接口。
我已经使用 Apache CXF 堆栈查看了 Jetty，但看起来我必须在对 Web 服务进行编码之前进行大量配置 - 这值得吗？它还能起作用吗？我是否应该忘记复杂性并简单地使用 JBoss/Weblogic/etc 并忍受臃肿和额外的启动时间？
I want to provide a Java-based Web Service, but I don't require the features of a full-blown J2EE Application Server. I would like it to start as quickly as possible, though that's not a hard requirement. The Web Service will handle multiple connections and require access to an Oracle database so it will at least require a thread pool and database connection pool. I may want to put a JSP interface onto it later to provide an internal maintainence interface.
I have looked at Jetty with an Apache CXF stack, but it looks like I'll have to do a fair amount configuration before even coding the web service - Will it be worth it? Will it even work? Should I forget about the complexity and simply go with JBoss/Weblogic/etc and put up with the bloat and extra start-up time?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我会在 Jetty、Tomcat 或 GlassFish v3 上使用 JAX-WS RI（我不同意这里表达的其他观点以及根据我使用 GFv3、GFv3 的实际经验）提供了高效的开发环境）。
请不要使用 Axis 2（我什至不会谈论它的架构和可怕的部署模型以及打包地狱，只需看看 JAX-WS RI 2.1 基准详细信息）。
I'd go with JAX-WS RI on Jetty, Tomcat or GlassFish v3 (I do not agree with other opinions expressed here and according to my practical experience with GFv3, GFv3 offers a highly productive environment for development).
And please, don't go Axis 2 (I won't even talk about its architecture and horrible deployment model and packaging hell, just have a look at the JAX-WS RI 2.1 benchmark details).
设置 Tomcat 6 + Axis 2 相当简单。我不建议在您的场景中使用 JBoss/Glassfish/etc - 开销远远超过唯一的好处 - 不涉及额外的设置。
Setting up Tomcat 6 + Axis 2 is fairly easy. I wouldn't recommend using JBoss/Glassfish/etc for your scenario - the overhead far outweighs the only benefit - no additional setup involved.
我正在使用嵌入式 jetty 来公开许多 jax-ws web 服务。工作得很好，配置只是从码头上去掉我不需要的东西。
I am using embedded jetty for exposing a number of jax-ws webservices. Works pretty well, and configuration involved just stripping off things I didn't need from jetty.