无状态的故障恢复是最简单的方法，但也是作用最有限的方法，因为该方法在故障服务器与备用服务器之间没有维护任何状态。
Stateless failover is the simplest approach but also the least useful approach given that the approach maintains no state between the failed server and the backup server.
所有使用WSDL发布的操作都是无状态的，它在消息实例间没有相关性。
All operations exposed using WSDL are stateless. It doesn't have a feature of correlating between message instances.
当服务请求没有与之前或之后的请求的隐含相关关系时，就使用无状态范围。
The stateless scope is used when service requests have no implied correlation with prior and future requests.
虽然据我所知还没有标准，但是浏览器和搜索引擎都认为GET请求服务的链接是无状态的。
Although this is not covered under a standard as far as I know, browsers and search engines expect links, which are served by GET requests, to be stateless.
当然，无状态trait没有初始化的问题。
Of course, stateless traits don't have any issues with initialization.
无状态的意思是，对Web服务的调用与之前的互操作没有相关性，并且不为以后的互操作而保存当前活动的信息。
Stateless means that an invocation to the Web service has no correlation to prior interactions, and no information from the current activity is saved for future interactions.
专用或无状态的bean没有这个问题，因为一旦您请求一个这样的bean，它就是您的了。
Dedicated, or stateful, beans don't have that problem, because once you request one, it's yours.
技术预览版使用无状态会话bean与JNDI名称 /ibm/events/access/EventAccess 绑定来实现入口点的方法没有改变。
The entry point is unchanged from the technical preview that is by using a stateless session bean bound with the JNDI name /ibm/events/access/EventAccess.
没有单独的无状态会话bean。
延续服务器提供了一个有状态的编程模型，同时又没有舍弃无状态所固有的可伸缩性，从而使Web应用程序开发更加容易。
By offering a stateful programming model without giving up the scalability inherent in statelessness, continuation servers make Web application development much easier.
延续服务器提供了一个有状态的编程模型，同时又没有舍弃无状态所固有的可伸缩性，从而使Web应用程序开发更加容易。
By offering a stateful programming model without giving up the scalability inherent in statelessness, continuation servers make Web application development much easier.
应用推荐