Websphere Java版本 [英] Websphere Java version

问题描述

如果节点是使用Java 7构建的，那么Java 6应用程序可以在Webpshere 8.5上运行吗?我有一个EAR，它是使用Java6开发的，并使用EA部署在Websphere 8.5上，但Web服务始终提供404.
谢谢.

Can a Java 6 application work on Webpshere 8.5 if the nodes are built using Java 7? I have an EAR which was developed using Java6 and deployed on Websphere 8.5 using EA but the Webservice always gives 404.
Thanks.

推荐答案

对于版本"的含义及其如何应用于JavaEE应用程序，这里存在一些困惑:

There is a confusion here about the meaning of "version" and how it applies to JavaEE applications:

已选择运行服务器的JVM版本.

There is the version of the JVM which is selected to run the server.

有JavaEE规范级别，用于对应用程序内的XML文档(web.xml，application.xml，ejb-jar.xml等)进行编码.

There is the JavaEE specification level used to encode XML documents (web.xml, application.xml, ejb-jar.xml, etc) which are within an application.

服务器支持JavaEE规范级别.

There is the JavaEE specification level which is supported by the server.

为应用程序中打包的类设置了Java编译器级别.

There is the java compiler level which is set for classes packaged within an application.

从技术上讲，没有与应用程序关联的特定版本.应用程序在Java 7上的意思是应用程序的类已编译为java7"，或"XML描述符设置为JavaEE7可用的版本"，或应用程序的功能需要一个支持以下内容的容器: JavaEE7".

There is, technically speaking, no specific version associated with an application. That an application is at Java 7 can mean "the classes of the application were compiled to java7", or, "the XML descriptors are set to the versions available to JavaEE7", or, "the function of the application requires a container which supports JavaEE7".

一个关键细节是，与WebSphere一起运行时，它是服务器，服务器决定应用程序运行于哪个JavaEE规范，而不是应用程序的任何功能.

A key detail is that when running with WebSphere, its the server which decides to which JavaEE specification the application is run, not any feature of the application.

我猜在最初的问题中，"Java 6应用程序"表示该应用程序已编译为java6，并且该应用程序功能仅限于java6中可用的功能.在所有WebSphere v7.0，v8.0，v8.5和v9.0(在所有服务级别)上都可以使用.

I'm guessing that in the original question, "Java 6 application" means the application was compiled to java6 and that the application features are limited to those available in java6. That should work on all of WebSphere v7.0, v8.0, v8.5, and v9.0 (at all service levels).

使用分布式拓扑(具有DMGr节点和多个应用程序服务器节点)时，需要考虑一些复杂问题.一种常见的麻烦是，一个或多个应用程序服务器节点的版本低于DMgr节点的版本.这是受支持的方案(在支持多少版本差异方面有一些限制).当拓扑结构(联合节点的集合)从特定的WebSphere版本逐渐迁移到更高的版本，并且在迁移过程中可以使用多种节点版本时，这种情况很典型.在这种情况下，DMgr会跟踪应用程序服务器节点的版本并限制对应用程序的处理，以确保该部署对部署了该应用程序的所有应用程序服务器节点均有效.

There are some complications to consider when using a distributed topology (having a DMGr node and more than one application server nodes). A frequent complication is that one or more of the application server nodes is at a lower version than the DMgr node. This is a supported scenario (with some limits on how big of a version difference is supported). The scenario is typical when a topology (a collection of federated nodes) is being migrated gradually from a particular WebSphere version to a higher version, and during the migration a mixture of node versions is available. When this is the case, the DMgr tracks the version of the application server nodes and constrains processing of the application to ensure the deployment is valid to all of the application server nodes to which the application is deployed.

由于JavaEE级别由应用程序服务器版本设置，并且由于通常更高版本的应用程序服务器实现更高的JavaEE级别，因此在应用程序服务器版本之间进行迁移时，应用程序 可以发挥不同的作用.如果不更详细地研究正在发生的确切故障，就无法知道是否是该问题的原因.

Since the JavaEE level is set by the application server version, and since, generally, higher versions of the application server implement higher JavaEE levels, applications can function differently when migrated between application server versions. Whether this is the case for this question cannot be known without looking in more detail at the exact failure which is occurring.

这篇关于Websphere Java版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！