文档库 最新最全的文档下载
当前位置:文档库 › 计算机科学与技术毕业设计(论文)外文翻译

计算机科学与技术毕业设计(论文)外文翻译

计算机科学与技术毕业设计(论文)外文翻译
计算机科学与技术毕业设计(论文)外文翻译

本科毕业设计(论文) 外文翻译(附外文原文)

系 ( 院 ):信息科学与工程学院

课题名称:学生信息管理系统

专业(方向):计算机科学与技术(应用)

7.1 Enter ActionMappings

The Model 2 architecture (see chapter 1) encourages us to use servlets and Java- Server Pages in the same application. Under Model 2, we start by calling a servlet.

The servlet handles the business logic and directs control to the appropriate page

to complete the response.

The web application deployment descriptor (web.xml) lets us map a URL pattern

to a servlet. This can be a general pattern, like *.do, or a specific path, like saveRecord.do.

Some applications implement Model 2 by mapping a servlet to each business operation. This approach works, but many applications involve dozens or hundreds

of business operations. Since servlets are multithreaded, instantiating so manyservlets is not the best use of server resources. Servlets are designed to handle any

number of parallel requests. There is no performance benefit in simply creating

more and more servlets.

The servlet’s primary job is to interact with the container and HTTP. Handling

a business operation is something that a servlet could delegate to another component. Struts does this by having the ActionServlet delegate the business operation

to an object. Using a servlet to receive a request and route it to a handler is known

as the Front Controller pattern [Go3].

Of course, simply delegating the business operation to another component

does not solve the problem of mapping URIs [W3C, URI] to business operations.

Our only way of communicating with a web browser is through HTTP requests and URIs. Arranging for a URI to trigger a business operation is an essential part of developing a web application.

Meanwhile, in practice many business operations are handled in similar ways.

Since Java is multithreaded, we could get better use of our server resources if we

could use the same Action object to handle similar operations. But for this to

work, we might need to pass the object a set of configuration parameters to use

with each operation.

So what’s the bottom line? To implement Model 2 in an efficient and flexible

way, we need to:

Enter ActionMappings 195

? Route requests for our business operations to a single servlet

? Determine which business operation is related to the request

? Load a multithreaded helper object to handle the business operation

? Pass the helper object the specifics of each request along with any configuration detail used by this operation

This is where ActionMappings come in.

7.1.1 The ActionMapping bean

An ActionMapping (org.apache.struts.action.ActionMapping) describes how

the framework handles each discrete business operation (or action). In Struts,

each ActionMapping is associated with a specific URI through its path property. When a request comes in, the ActionServlet uses the path property to select the corresponding ActionMapping. The set of ActionMapping objects is kept in an ActionMappings collection (org.apache.struts.action.ActionMappings). Originally, the ActionMapping object was used to extend the Action object

rather than the Action class. When used with an Action, a mapping gives a specific Action object additional responsibilities and new functionality. So, it was essentially

an Action decorator [Go4]. Along the way, the ActionMapping evolved into an

object in its own right and can be used with or without an Action.

DEFINITION The intent of the decorator pattern is to attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing

for extending functionality [Go4].

The ActionMappings are usually created through the Struts configuration file.

For more about this file, see chapter 4.

7.1.2 The ActionMappings catalog

The ActionMappings catalog the business logic available to a Struts application.

When a request comes in, the servlet finds its entry in the ActionMappings catalog

and pulls the corresponding bean.

The ActionServlet uses the ActionMapping bean to decide what to do next. It

may need to forward control off to another resource. Or it may need to populate

and validate an ActionForm bean. At some point, it may have to pass control to an Action object, and when the Action returns, it may have to look up an Action-

Forward associated with this mapping.

196 CHAPTER 7

Designing with ActionMappings

The ActionMapping works like a routing slip for the servlet. Depending on

how the mapping is filled out, the request could go just about anywhere.

The ActionMappings represent the core design of a Struts application. If you

want to figure out how a Struts application works, start with the ActionMappings. If

you want to figure out how to write a new Struts application, start with the Action- Mappings. The mappings are at the absolute center of every Struts application.

In this chapter, we take a close look at the ActionMapping properties and

explore how they help you design the flow of a Struts application.

1.0 vs 1.1 In Struts 1.1, ActionMapping subclasses ActionConfig (org.apache. struts.config.ActionConfig) and adds API methods required for

backward compatibility. ActionMapping is not deprecated, and how the

hierarchy will be handled in future releases has not been determined.

For now, we refer to the ActionMapping class, but you should note that

in Struts 1.1 all of the action properties are actually defined by the ActionConfig

super class. The ActionMapping class otherwise works the

same way in both versions.

7.2 ActionMapping properties

Table 7.1 describes the base ActionMapping properties. As with other configuration components, developers may extend ActionMapping to provide additional

properties.

Table 7.1 The base ActionMapping properties

Property Description

path The URI path from the request used to select this mapping. (API command) forward The context-relative path of the resource that should serve this request via a forward.

Exactly one of the forward, include, or type properties must be specified.

or

include The context-relative path of the resource that should serve this request via an

include. Exactly one of the forward, include, or type properties must be specified.

or

type Optionally specifies a subclass of

org.apache.struts.action.ActionMapping

that should be used when instantiating this mapping.

className The fully qualified name of the Action class used by this mapping. Since

Struts 1.1

ActionMapping properties 197

In the sections that follow, we take a look at each of these properties.

7.2.1 The path property

The ActionMapping URI, or path, will look to the user like just another file on

the web server. But it does not represent a file. It is a virtual reference to our ActionMapping.

Because it is exposed to other systems, the path is not really a logical name, like

those we use with ActionForward. The path can include slashes and an extension—

as if it referred to a file system—but they are all just part of a single name.

The ActionMappings themselves are a “flat” namespace with no type of internal

hierarchy whatsoever. They just happen to use the same characters that we are

used to seeing in hierarchical file systems.

name The name of the form bean, if any, associated with this action. This is not the class

name. It is the logical name used in the form bean configuration.

roles The list of security roles that may access this mapping.

scope The identifier of the scope (request or session) within which the form bean, if any,

associated with this mapping will be created.

validate Set to true if the validate method of the form bean (if any) associated with this

mapping should be called.

input Context-relative path of the input form to which control should be returned if

a validation

error is encountered. This can be any URI: HTML, JSP, VM, or another Action- Mapping.

parameter General-purpose configuration parameter that can be used to pass extra information

to the Action selected by this ActionMapping.

attribute Name of the request-scope or session-scope attribute under which our form bean is

accessed, if it is other than the bean's specified name.

prefix Prefix used to match request parameter names to form bean property names, if any.

suffix Suffix used to match request parameter names when populating the properties of

our ActionForm bean, if any.

unknown Can be set to true if this mapping should be configured as the default for this application

(to handle all requests not handled by another mapping). Only one mapping

can be defined as the default unknown mapping within an application.

forwards(s) Block of ActionForwards for this mapping to use, if any.

exception(s) Block of ExceptionHandlers for this mapping to use, if any.

Table 7.1 The base ActionMapping properties (continued)

Property Description

Since

Struts 1.1

Since

Struts 1.1

198 CHAPTER 7

Designing with ActionMappings

Of course, it can still be useful to treat your ActionMappings as if they were

part of a hierarchy and group related commands under the same "folder." The

only restriction is that the names must match whatever pattern is used in the application’s deployment description (web.xml) for the ActionServlet. This is usually

either /do/* or *.do, but any similar pattern can be used.

If you are working in a team environment, different team members can be

given different ActionMapping namespaces to use. Some people may be working

with the /customer ActionMappings, others may be working with the /vendor ActionMappings. This may also relate to the Java package hierarchy the team is

using. Since the ActionMapping URIs are logical constructs, they can be organized

in any way that suits your project.

With Struts 1.1, these types of namespaces can be promoted to application

modules. Each team can work independently on its own module, with its own set

of configuration files and presentation pages. Configuring your application to use multiple modules is covered in chapter 4.

DEFINITION The web runs on URIs, and most URIs map to physical files. If you want to change the resource, you change the corresponding file. Some URIs, like

Struts actions, are virtual references. They do not have a corresponding

file but are handled by a programming component. To change the resource,

we change how the component is programmed. But since the

path is a URI and interacts with other systems outside our control, the

path is not a true logical reference—the name of an ActionForward, for

instance. We can change the name of an ActionForward without consulting

other systems. It’s an internal, logical reference. If we change the

path to an ActionMapping, we might need to update other systems that

refer to the ActionMapping through its public URI.

7.2.2 The forward property

When the forward property is specified, the servlet will not pass the request to an Action class but will make a call to RequestDispatcher.forward. Since the operation

does not use an Action class, it can be used to integrate Struts with other

resources and to prototype systems. The forward, include, and type properties

are mutually exclusive. (See chapter 6 for more information.)

7.2.3 The include property

When the include property is specified, the servlet will not pass the request to an Action class but will make a call to RequestDispatcher.include. The operation

ActionMapping properties 199

does not use an Action class and can be used to integrate Struts with other components. The forward, include, and type properties are mutually exclusive. (See

chapter 6 for more information.)

7.2.4 The type property

Most mappings will specify an Action class type rather than a forward or include.

An Action class may be used by more than one mapping. The mappings may specify

form beans, parameters, forwards, or exceptions. The forward, include, and

type properties are mutually exclusive.

7.2.5 The className property

When specified, className is the fully qualified Java classname of the ActionMapping subclass that should be used for this object. This allows you to use your own ActionMapping subclass with specialized methods and properties. See also

section 7.4.

7.2.6 The name property

This property specifies the logical name for the form bean, as given in the formbean segment of the Struts configuration file. By default, this is also the name to

be used when placing the form bean in the request or session context. Use the

attribute property of this class to specify a different attribute key.

7.2.7 The roles property

This property is a comma-delimited list of the security role names that are allowed access to this ActionMapping object. By default, the same system that is used with standard container-based security is applied to the list of roles given here. This

means you can use action-based security in lieu of specifying URL patterns in the deployment descriptor, or you can use both together.

The security check is handled by the processRoles method of the Request- Processor (org.apache.struts.action.RequestProcessor). By subclassing RequestProcessor, you can also use the roles property with application-based security. See chapter 9 for more about subclassing RequestProcessor.

7.2.8 The scope property

The ActionForm bean can be stored in the current request or in the session scope (where it will be available to additional requests). While most developers use

request scope for the ActionForm, the framework default is session scope. To

make request the default, see section 7.4.

Since

Struts 1.1

Since

Struts 1.1

200 CHAPTER 7

Designing with ActionMappings

7.2.9 The validate property

An important step in the lifecycle of an ActionForm is to validate its data before offering it to the business layer. When the validate property for a mapping is true, the ActionServlet will call the ActionForm’s validate method. If validate returns false, the request is forwarded to the resource given by the input property.

Often, developers will create a pair of mappings for each data entry form. One

mapping will have validate set to false, so you can create an empty form. The

other has validate set to true and is used to submit the completed form.

NOTE Whether or not the ActionForm validate method is called does not relate

to the ActionServlet’s validating property. That switch controls

how the Struts configuration file is processed.

7.2.10 The input property

When validate is set to true, it is important that a valid path for input be provided. This is where control will pass should the ActionForm validate method

return false. Often, this is the address for a presentation page. Sometimes it will

be another Action path (with validate set to false) that is required to generate

data objects needed by the page.

NOTE The input path often leads back to the page that submitted the request.

While it seems natural for the framework to return the request to where

it originated, this is not a simple task in a web application. A request is often

passed from component to component before a response is sent back

to the browser. The browser only knows the path it used to retrieve the

input page, which may or may not also be the correct path to use for the

input property. While it may be possible to try and generate a default input

page based on the HTTP referrer attribute, the Struts designers

deemed that approach unreliable.

inputForward

In Struts 1.0, the ActionMapping input property is always a literal URI. In

Struts 1.1, it may optionally be the name of an ActionForward instead. The ActionForward is retrieved and its path property is used as the input property.

This can be a global or local ActionForward.

To use ActionForwards here instead of literal paths, set the inputForward

attribute on the element for this module to true:

Since

Struts 1.1

ActionMapping properties 201

For more about configuring Struts, see chapter 4. For more about ActionForwards,

see chapter 6.

7.2.11 The parameter property

The generic parameter property allows Actions to be configured at runtime. Several

of the standard Struts Actions make use of this property, and the standard

Scaffold Actions often use it, too. The parameter property may contain a URI, the name of a method, the name of a class, or any other bit of information an Action

may need at runtime. This flexibility allows some Actions to do double and triple

duty, slashing the number of distinct Action classes an application needs on hand.

Within an Action class, the parameter property is retrieved from the mapping

passed to perform:

parameter = mapping.getParameter();

Multiple parameters

While multiple parameters are not supported by the standard ActionMappings

class, there are some easy ways to implement this, including using HttpUtils, a StringTokenizer, or a Properties file (java.util.Properties).

HttpUtils. Although deprecated as of the Servlet API 2.3 specification, the

HttpUtils package (javax.servlet.http.HttpUtils) provides a static method that parses any string as if it were a query string and returns a Hashtable

(java.util.Hashtable):

Hashtable parameters = parseQueryString(parameter);

The parameter property for your mapping then becomes just another query string, because you might use it elsewhere in the Struts configuration. stringTokenizer. Another simple approach is to delimit the parameters using the token of your choice—such as a comma, colon, or semicolon—and use the StringTokenizer to read them back:

StringTokenizer incoming =

new StringTokenizer(mapping.getParameter(),";");

int i = 0;

String[] parameters = new String[incoming.countTokens()]; while (incoming.hasMoreTokens()) {

parameters[i++] = incoming.nextToken().trim();

}

202 CHAPTER 7

Designing with ActionMappings

Properties file. While slightly more complicated than the others, another popular approach to providing multiple parameters to an ActionMapping is with a standard Properties files (java.util.Properties). Depending on your needs, the Properties file could be stored in an absolute location in your file system or anywhere on your application’s CLASSPATH.

The Commons Scaffold package [ASF, Commons] provides a ResourceUtils package (https://www.wendangku.net/doc/766966372.html,mons.scaffold.util.ResourceUtils) with methods for

loading a Properties file from an absolute location or from your application’s CLASSPATH.

7.2.12 The attribute property

From time to time, you may need to store two copies of the same ActionForm in

the same context at the same time. This most often happens when ActionForms

are being stored in the session context as part of a workflow. To keep their names from conflicting, you can use the attribute property to give one ActionForm bean a different name.

An alternative approach is to define another ActionForm bean in the configuration, using the same type but under a different name.

7.2.13 The prefix and suffix properties

Like attribute, the prefix and suffix properties can be used to help avoid naming conflicts in your application. When specified, these switches enable a

prefix or suffix for the property name, forming an alias when it is populated

from the request.

If the prefix this was specified, then

thisName=McClanahan

becomes equivalent to

name=McClanahan

for the purpose of populating the ActionForm. Either or both parameters would call getName("McClanahan");

This does not affect how the properties are written by the tag extensions. It affects how the autopopulation mechanism perceives them in the request.

Nested components 203

7.2.14 The unknown ActionMapping

While surfing the Web, most of us have encountered the dreaded 404— page not found message. Most web servers provide some special features for processing requests for unknown pages, so webmasters can steer users in the right direction. Struts offers a similar service for ActionMapping 404s—the unknown ActionMapping. In the Struts configuration file, you can specify one ActionMapping to

receive any requests for an ActionMapping that would not otherwise be matched:

name="/debug"

forward="/pages/debug.jsp"/>

When this option is not set, a request for an ActionMapping that cannot be

matched throws

400 Invalid path /notHere was requested

Note that by a request for an ActionMapping, we mean a URI that matches the prefix or suffix specified for the servlet (usually /do/* or *.do). Requests for other URI patterns, good or bad, will be handled by other servlets or by the container:

/do/notHere (goes to the unknown ActionMapping)

/notHere.txt (goes to the container)

7.3 Nested components

The ActionMapping properties are helpful when it comes to getting an Action to

run a business operation. But they tell only part of the story. There is still much to

do when the Action returns.

An Action may have more than one outcome. We may need to register several ActionForwards so that the Action can take its pick.

7.3.1 Local forwards

In the normal course, an ActionMapping is used to select an Action object to handle the request. The Action returns an ActionForward that indicates which page

should complete the response.

The reason we use ActionForwards is that, in practice, presentation pages are

either often reused or often changed, or both. In either case, it is good practice to encapsulate the page’s location behind a logical name, like “success” or “failure.”

The ActionForward object lets us assign a logical name to any given URI.

204 CHAPTER 7

Designing with ActionMappings

Of course, logical concepts like success or failure are often relative. What represents success to one Action may represent failure to another. Each Action-

Mapping can have its own set of local ActionForwards. When the Action asks for a forward (by name), the local set is checked before trying the global forwards. See chapter 6 for more about ActionForwards.

Local forwards are usually specified in the Struts configuration file. See chapter

4 for details.

7.3.2 Local exceptions

Most often, an application’s exception handlers (org.apache.struts.action. ExceptionHandler) can be declared globally. However, if a given ActionMapping needs to handle an exception differently, it can have its own set of local exception handlers that are checked before the global set.

Local exceptions are usually specified in the Struts configuration file. See

chapter 4 for details.

7.4 Rolling your own ActionMapping

While ActionMapping provides an impressive array of properties, developers may also provide their own subclass with additional properties or methods. In

Struts 1.0, this is configured in the deployment descriptor (web.xml) for the ActionServlet:

mapping

app.MyActionMapping

In Struts 1.1, this is configured in the Struts configuration file as an attribute to the element:

Individual mappings may also be set to use another type through the className attribute:

For more about configuring Struts, see chapter 4.

Since

Struts 1.1

Summary 205

The framework provides two base ActionMapping classes, shown in table 7.2. They can be selected as the default or used as a base for your own subclasses.

The framework default is SessionActionMapping, so scope defaults to session. Subclasses that provide new properties may set them in the Struts configuration using a standard mechanism:

Using this standard mechanism helps developers avoid subclassing the Action- Servlet just to recognize the new properties when it digests the configuration file. This is actually a feature of the Digester that Struts simply inherits.

7.5 Summary

Sun’s Model 2 architecture teaches that servlets and JavaServer Pages should be used together in the same application. The servlets can handle flow control and data acquisition, and the JavaServer Pages can handle the HTML.

Struts takes this one step further and delegates much of the flow control and

data acquisition to Action objects. The application then needs only a single servlet

to act as a traffic cop. All the real work is parceled out to the Actions and the

Struts configuration objects.

Like servlets, Actions are efficient, multithreaded singletons. A single Action

object can be handling any number of requests at the same time, optimizing your server’s resources.

To get the most use out of your Actions, the ActionMapping object is used as a decorator for the Action object. It gives the Action a URI, or several URIs, and a

way to pass different configuration settings to an Action depending on which URI

is called.

In this chapter, we took a close look at the ActionMapping properties and

explained each property’s role in the scheme of things. We also looked at extending

the standard ActionMapping object with custom properties—just in case your

scheme needs even more things.

Table 7.2 The default ActionMapping classes

ActionMapping Description

org.apache.struts.action.SessionActionMapping Defaults the scope property to session

org.apache.struts.action.RequestActionMapping Defaults the scope property to request

206 CHAPTER 7

Designing with ActionMappings

In chapter 8, the real fun begins. The configuration objects covered so far are

mainly a support system. They help the controller match an incoming request

with a server-side operation. Now that we have the supporting players, let’s meet the Struts diva: the Action object.

7.1 进入ActionMapping

Model 2 架构(第1章)鼓励在同一个应用中使用servlet和JSP页面。在Model 2下,我们

从调用一个servlet开始。

Servlet 处理业务逻辑并将控制转到相应的页面来完成响应。web应用部署描述符(web.xml) 让我们可以映射一个URL模板给一个servlet。这可以是一个常用的模板格式,象

*.do, 或者特别的路径, 象saveRecord.do。某些应用通过给每个业务操作映射一个Servlet来实

现Model 2。这种方法可以工作,但许多应用也涉及到大量的业务操作。因为servlet 是多线

程的,实例化这么多servlet 显然不是使用服务器资源的最好方式。Servlet设计来可以处理大

量的并行请求。简单的创建很多servlet并没有什么性能优势。

Servlet的主要工作是和容器和HTTP进行交互。处理业务操作是servlet代表其它组件干的

事情。Struts 通过使ActionServlet 代表其他对象的业务操作来做这些事情。用servlet 接受

请求并路由到一个处理器(称为前端控制器模式[Go3])。

当然, 简单的代表其他对象的业务操作并没有解决映射URI [W3C, URI] 到业务操作

的问

题。我们和Web浏览器进行通信能使用的唯一途径是HTTP 请求和URI。如何组织URI 来触

发业务操作是开发web 应用的关键部分。

同时,在实际应用中,许多业务操作都以相似的方式来进行处理。因为Java 是多线程

的,如果我们使用同一个Action 对象来处理相似的操作,就能更好的利用服务器资源。但

是要让它能工作,我们可能需要向对象传递一些配置参数,以便和每个操作一起使用。所以,底线是什么?为以一种灵活和有效的方式实现Model 2,我们需要路由对业务操作的请求到一个servlet

决定哪个业务操作和请求相关

装入多线程的helper 对象来处理业务操作

将每个请求特定的配置细节传递给helper对象。

这样,ActionMapping出场了!

7.1.1 ActionMapping bean

ActionMapping (org.apache.struts.action.ActionMapping) 描述了框架是如何处

理每一离散的业务操作(或action)。在Struts中,每个ActionMapping 通过其path 属性和

一个特定的URI 相关。

当一个请求到来,ActionServlet 使用path 属性来选择对应的ActionMapping。一系列

ActionMapping 对象被放在一个ActionMappings 集合之中

(org.apache.struts.action.ActionMappings)。原本, ActionMapping 对象用来扩展

Action 对象而不是Action 类。当和Action使用时,mapping 给了一个特定的Action 对象一

些额外的职责和新的功能。所以本质上来说,Action 是一个装饰器(decorator [Go4])。通

过这种方式,ActionMapping 以自己的方式发展为一个对象,可以和Action一起使用,也

可以不。

Struts In Action

DEFINITION

装饰器模式(decorator pattern)的意图是为一个对象动态的附加上额外的职责和功能。Decorator

在扩展功能时提供了一个除子类化外的选择。[Go4].

ActionMapping通常通过Struts 配置文件创建。更多信息,参见第4章。

7.1.2 ActionMapping 目录

ActionMapping将对Struts 应用有效的业务逻辑进行编目。当一个请求到达时,servlet 在

ActionMapping目录中查找条目,来调用相应的bean。ActionServlet 使用ActionMapping bean

来决定接下来该做什么。它也许需要将控制转发到其他资源。或者也许它需要组装并且校验

一个ActionForm bean。某些时候,它也许会将控制传递给一个Action 对象,并且当Action 返

回时,它可能会查找和这个mapping相关的ActionForward。

ActionMapping工作起来就像是servlet的一个路由联络。取决于mapping 如何被填充,可

能被传递到上述的任何地方。ActionMapping表达了Struts 应用的核心设计。如果你想知道

一个Struts 应用是如何工作的,可以从ActionMapping开始着手。如果你想知道如何编写一

个新的Struts 应用,也请从ActionMapping开始。Mapping处于每个Struts 应用的绝对核心。

在本章,我们将详细讨论ActionMapping 属性,并展示他们如何有助于设计Struts 应用的流

程。

1.0 vs 1.1

在Struts 1.1中, ActionMapping 子类化了ActionConfig

(org.apache.struts.config.ActionConfig) 类,并因向后兼容添加了API 方法。ActionMapping 已经不推荐,但后继版本中类的层次还没有决定。

当前,我们引用ActionMapping 类,但你应该注意到在Struts 1.1中,所有的action 属性实际上

都在ActionConfig超类中有定义。ActionMapping类可以工作在两个版本下。

7.2 ActionMapping 属性

表7.1 描述了基本的属性。当和其他配置组件一起,开发人员可以扩展ActionMapping to 提

供附加的属性。

属性说明

path

来自于请求的URI路径,用来选择该mapping。(API command)

forward

上下文相关的资源路径,通过一个forward服务这个请求。

实际上是forward, include, type 属性的一个,必须标明。

include

上下文相关的资源路径,通过一个include服务这个请求。

实际上是forward, include, type 属性的一个,必须标明。

type 可选,表明一个org.apache.struts.action.ActionMapping的子类名称,在实例化这个mapping

Struts In Action

时使用。

classname 该Mapping使用的Action 类的全限定名称

name

与该Mapping相关的form bean的名称,如果有。这不是类名称。而是在form bean 配置中

使用的逻辑名称。

roles 可以存取该mapping的安全角色列表.

scope 范围(请求或会话)识别符,如果有,与该mapping相关的forma Bean在其中创建

validate 如果与该mapping相关的form bean的validate 方法(如果有)要被调用,设置为true.

input

输入表单的上下文相关的路径,如果校验错误,控制应该被返回到该表单。可以是任何:

HTML, JSP, VM, 或者另一个ActionMapping。

parameter 通用配置参数,用来向ActionMapping选定的Action传递额外的参数信息。.

attribute

请求-范围或者会话-范围的属性名称,form bean 在下面被访问。如果它是bean'特定名称

外的名称。

prefix 用来匹配请求参数名称到form bean 属性名称的前缀,如果有

suffix 在组装Actionform bean属性时,用来匹配请求参数名称的后缀,如果有。

unknown

如果该mapping 要被配置为应用的缺省mapping(处理那些没有被其它mapping处理的

请求),可设置为true。在一个应用中仅有一个mapping 可定义为缺省unknown mapping。

forwards(s) 该mapping使用的ActionForward,如果有

exception(s) 该mapping使用的ExceptionHandler如果有

表7.1 ActionMapping 基本属性

在接下来的一节,我们将详细讨论每个属性。

7.2.1 path属性

ActionMapping URI,或者path,对用户来说就象web server上的一个文件。但实际上它并

不代表一个文件。它是一个对ActionMapping的虚拟引用。

因为它暴露给其他系统,path 并不真正是个逻辑名称,就想那些我们在ActionForward使

用的一样。path 可以包括反斜杠和扩展名--如果他引用到一个文件系统—但他们都只是一

个单一名称的一部分。

ActionMapping自身是一个“平面的” 名称空间,完全没有一个内部层次关系。They just happen to 使用the same characters that we are 使用d to seeing in hierarchical 文件systems.

当然, 这对处理ActionMapping仍然是有帮助的,就象他们是一个层次关系或者在同一个"文

件夹."下的相关命令组的一部分。唯一的限制是名称必须匹配于在应用部署描述文件中为

ActionServlet指定的样式。这通常是/do/*或者*.do,但是其他相似的样式也可以使用。如果

你在一个团队环境中工作,不同的团队可能有不同的ActionMapping 名称空间使用。某些

人可能工作于/customer ActionMapping, 而另一些可能工作于/vendor ActionMapping。

这也可能和各个团队使用的Java 包的层次相关。因为ActionMapping URI是逻辑的构

毕业设计外文翻译资料

外文出处: 《Exploiting Software How to Break Code》By Greg Hoglund, Gary McGraw Publisher : Addison Wesley Pub Date : February 17, 2004 ISBN : 0-201-78695-8 译文标题: JDBC接口技术 译文: JDBC是一种可用于执行SQL语句的JavaAPI(ApplicationProgrammingInterface应用程序设计接口)。它由一些Java语言编写的类和界面组成。JDBC为数据库应用开发人员、数据库前台工具开发人员提供了一种标准的应用程序设计接口,使开发人员可以用纯Java语言编写完整的数据库应用程序。 一、ODBC到JDBC的发展历程 说到JDBC,很容易让人联想到另一个十分熟悉的字眼“ODBC”。它们之间有没有联系呢?如果有,那么它们之间又是怎样的关系呢? ODBC是OpenDatabaseConnectivity的英文简写。它是一种用来在相关或不相关的数据库管理系统(DBMS)中存取数据的,用C语言实现的,标准应用程序数据接口。通过ODBCAPI,应用程序可以存取保存在多种不同数据库管理系统(DBMS)中的数据,而不论每个DBMS使用了何种数据存储格式和编程接口。 1.ODBC的结构模型 ODBC的结构包括四个主要部分:应用程序接口、驱动器管理器、数据库驱动器和数据源。应用程序接口:屏蔽不同的ODBC数据库驱动器之间函数调用的差别,为用户提供统一的SQL编程接口。 驱动器管理器:为应用程序装载数据库驱动器。 数据库驱动器:实现ODBC的函数调用,提供对特定数据源的SQL请求。如果需要,数据库驱动器将修改应用程序的请求,使得请求符合相关的DBMS所支持的文法。 数据源:由用户想要存取的数据以及与它相关的操作系统、DBMS和用于访问DBMS的网络平台组成。 虽然ODBC驱动器管理器的主要目的是加载数据库驱动器,以便ODBC函数调用,但是数据库驱动器本身也执行ODBC函数调用,并与数据库相互配合。因此当应用系统发出调用与数据源进行连接时,数据库驱动器能管理通信协议。当建立起与数据源的连接时,数据库驱动器便能处理应用系统向DBMS发出的请求,对分析或发自数据源的设计进行必要的翻译,并将结果返回给应用系统。 2.JDBC的诞生 自从Java语言于1995年5月正式公布以来,Java风靡全球。出现大量的用java语言编写的程序,其中也包括数据库应用程序。由于没有一个Java语言的API,编程人员不得不在Java程序中加入C语言的ODBC函数调用。这就使很多Java的优秀特性无法充分发挥,比如平台无关性、面向对象特性等。随着越来越多的编程人员对Java语言的日益喜爱,越来越多的公司在Java程序开发上投入的精力日益增加,对java语言接口的访问数据库的API 的要求越来越强烈。也由于ODBC的有其不足之处,比如它并不容易使用,没有面向对象的特性等等,SUN公司决定开发一Java语言为接口的数据库应用程序开发接口。在JDK1.x 版本中,JDBC只是一个可选部件,到了JDK1.1公布时,SQL类包(也就是JDBCAPI)

软件开发概念和设计方法大学毕业论文外文文献翻译及原文

毕业设计(论文)外文文献翻译 文献、资料中文题目:软件开发概念和设计方法文献、资料英文题目: 文献、资料来源: 文献、资料发表(出版)日期: 院(部): 专业: 班级: 姓名: 学号: 指导教师: 翻译日期: 2017.02.14

外文资料原文 Software Development Concepts and Design Methodologies During the 1960s, ma inframes and higher level programming languages were applied to man y problems including human resource s yste ms,reservation s yste ms, and manufacturing s yste ms. Computers and software were seen as the cure all for man y bu siness issues were some times applied blindly. S yste ms sometimes failed to solve the problem for which the y were designed for man y reasons including: ?Inability to sufficiently understand complex problems ?Not sufficiently taking into account end-u ser needs, the organizational environ ment, and performance tradeoffs ?Inability to accurately estimate development time and operational costs ?Lack of framework for consistent and regular customer communications At this time, the concept of structured programming, top-down design, stepwise refinement,and modularity e merged. Structured programming is still the most dominant approach to software engineering and is still evo lving. These failures led to the concept of "software engineering" based upon the idea that an engineering-like discipl ine could be applied to software design and develop ment. Software design is a process where the software designer applies techniques and principles to produce a conceptual model that de scribes and defines a solution to a problem. In the beginning, this des ign process has not been well structured and the model does not alwa ys accurately represent the problem of software development. However,design methodologies have been evolving to accommo date changes in technolog y coupled with our increased understanding of development processes. Whereas early desig n methods addressed specific aspects of the

电气专业毕业设计外文翻译

附录1:外文资料翻译 A1.1外文资料题目 26.22 接地故障电路开关 我们目前为止报道的接地方法通常是充分的, 但更加进一步的安全措施在某些情况下是必要的。假设例如, 有人将他的手指伸进灯口(如Fig.26.45示)。虽然金属封入物安全地接地, 但那人仍将受到痛苦的震动。或假设1个120V 的电炉掉入游泳池。发热设备和联络装置将导致电流流入在水池中的危害,即使电路的外壳被安全地接地,现在已经发展为当这样的事件发生时,设备的电源将被切断。如果接地电流超过5mA ,接地开关将在5 ms 内跳掉,这些装置怎么运行的? 如Fig.26.46所示,一台小变流器缠绕上导线 ,第二步是要连接到可能触发开合120 V 线的一台敏感电子探测器。 在正常情况下流过导体的电流W I 与中性点上的电流N I 准切的相等,因此流经核心的净潮流(N W I I -)是零。 结果,在核心没有产生电流,导致的电压F E 为零,并且开关CB 没有动作。 假设如果某人接触了一个终端(图Fig.26.45示),故障电流F I 将直接地从载电线漏到地面,这是可能发生的。如果绝缘材料在马达和它的地面封入物之间断开,故障电流也会被产生。在以下任何情况下,流经CT 的孔的净潮流等于F I 或L I ,不再是零。电流被产生,并且产生了可以控制CB 开关的电压F E 。 由于5 mA 不平衡状态只必须被检测出,变压器的核心一定是非常有渗透性的在低通量密度。 Supermalloy 是最为常用的,因为它有相对渗透性典型地70000在通量密度仅4mT 。 26.23 t I 2是导体迅速发热的因素 它有时发生于导体短期内电流远大于正常值的情况下,R I 2损失非常大并且导体的温度可以在数秒内上升几百度。例如,当发生严重短路时,在保险丝或开关作用之前,会有很大的电流流过导体和电缆。 此外,热量没有时间被消散到周围,因此导体的温度非常迅速地增加。 在这些情况下什么是温度上升? 假设导体有大量m ,电阻R 和热量热容量c 。 而且,假设电流是I ,并且那它流动在t 少于15秒期间。 在导体上引起的热 Rt I Q 2= 从Eq.3.17,在功率一定的情况下我们可以计算导体上升的温度差:

毕业设计外文翻译附原文

外文翻译 专业机械设计制造及其自动化学生姓名刘链柱 班级机制111 学号1110101102 指导教师葛友华

外文资料名称: Design and performance evaluation of vacuum cleaners using cyclone technology 外文资料出处:Korean J. Chem. Eng., 23(6), (用外文写) 925-930 (2006) 附件: 1.外文资料翻译译文 2.外文原文

应用旋风技术真空吸尘器的设计和性能介绍 吉尔泰金,洪城铱昌,宰瑾李, 刘链柱译 摘要:旋风型分离器技术用于真空吸尘器 - 轴向进流旋风和切向进气道流旋风有效地收集粉尘和降低压力降已被实验研究。优化设计等因素作为集尘效率,压降,并切成尺寸被粒度对应于分级收集的50%的效率进行了研究。颗粒切成大小降低入口面积,体直径,减小涡取景器直径的旋风。切向入口的双流量气旋具有良好的性能考虑的350毫米汞柱的低压降和为1.5μm的质量中位直径在1米3的流量的截止尺寸。一使用切向入口的双流量旋风吸尘器示出了势是一种有效的方法,用于收集在家庭中产生的粉尘。 摘要及关键词:吸尘器; 粉尘; 旋风分离器 引言 我们这个时代的很大一部分都花在了房子,工作场所,或其他建筑,因此,室内空间应该是既舒适情绪和卫生。但室内空气中含有超过室外空气因气密性的二次污染物,毒物,食品气味。这是通过使用产生在建筑中的新材料和设备。真空吸尘器为代表的家电去除有害物质从地板到地毯所用的商用真空吸尘器房子由纸过滤,预过滤器和排气过滤器通过洁净的空气排放到大气中。虽然真空吸尘器是方便在使用中,吸入压力下降说唱空转成比例地清洗的时间,以及纸过滤器也应定期更换,由于压力下降,气味和细菌通过纸过滤器内的残留粉尘。 图1示出了大气气溶胶的粒度分布通常是双峰形,在粗颗粒(>2.0微米)模式为主要的外部来源,如风吹尘,海盐喷雾,火山,从工厂直接排放和车辆废气排放,以及那些在细颗粒模式包括燃烧或光化学反应。表1显示模式,典型的大气航空的直径和质量浓度溶胶被许多研究者测量。精细模式在0.18?0.36 在5.7到25微米尺寸范围微米尺寸范围。质量浓度为2?205微克,可直接在大气气溶胶和 3.85至36.3μg/m3柴油气溶胶。

STC89C52处理芯片-毕业论文外文翻译

中文翻译 STC89C52处理芯片 电气工程的研究和解决方案中心(ceers) 艾哈迈德为吉.波特 首要性能: 与MCS-51单片机产物兼容、8K字节在系统可编程视频存储器、1000次擦拭周期,全静态操作:0Hz~33Hz、三级加密程序存储器,32个可编程I/O接口线、三个16位定时器(计数器),八个中断源、低功能耗空闲和掉电模式、掉电后间断可唤醒,看门狗定时器、双数值指针,掉电标示符。 关键词:单片机,UART串行通道,掉电标示符等 前言 可以说,二十世纪跨越了三个“点”的时代,即电气时代,电子时代和现已进入的电脑时代。不过,这种电脑,通常指的是个人计算机,简称PC机。还有就是把智能赋予各种机械的单片机(亦称微控制器)。顾名思义,这种计算机的最小系统只用了一片集成电路,即可进行简单的运算可控制。因为它体积小,通常都是藏在被控机械的内部里面。它在整个装置中,起着有如人类头脑的作用,他出了毛病,整个装置就会瘫痪。现在,单片机的种类和适用领域已经十分广泛,如智能仪表、实施工控、通讯设备、导航系统、家用电器等。各种产品一旦用上了单片机,就你能起到产品升级换代的功效,常在产品名称前冠以形容词——“智能型”,如智能洗衣机等。接下来就是关于国产STC89C52单片机的一些基本参数。 功能特性描述: STC89C52单片机是一种低功耗、高性能CMOS8位微控制器,具有8K在系统可编程视频播放存贮器使用高密度非易失性存储器技术制造,与工业80C51 产物指令和引脚完全兼容。片上反射速度允许程序存储器在系统可编程,也适用于常规的程序编写器。在其单芯片上,拥有灵敏小巧的八位中央处理器和在线系统可编程反射,这些使用上STC89C52微控制器为众多嵌入式的控制应用系统提供高度矫捷的、更加有用的解决方案。STC89C52微控制器具有以下的标准功效:8K字节的反射速度,256字节的随机存取储存器,32位I/O串口线,看门狗定时器,2个数值指针,三个16 为定时器、计数器,一个6向量2级间断结构,片内晶振及钟表电路。另外,STC89C52可降至0HZ静态逻辑操作,支持两种软件可选择节电模式、间断继续工作。空闲模式下,CPU停止工作,允许RAM、定时器/计数器、串口、间断继续工作。掉电保护体式格局下,RAM内容被生成,振动器被冻结,单片机一切的工作停止,直到下一个间断或者硬件复位为止。8位微型控制器8K字节在系统中可编程FlashSTC89C52.。

毕业设计外文翻译

毕业设计(论文) 外文翻译 题目西安市水源工程中的 水电站设计 专业水利水电工程 班级 学生 指导教师 2016年

研究钢弧形闸门的动态稳定性 牛志国 河海大学水利水电工程学院,中国南京,邮编210098 nzg_197901@https://www.wendangku.net/doc/766966372.html,,niuzhiguo@https://www.wendangku.net/doc/766966372.html, 李同春 河海大学水利水电工程学院,中国南京,邮编210098 ltchhu@https://www.wendangku.net/doc/766966372.html, 摘要 由于钢弧形闸门的结构特征和弹力,调查对参数共振的弧形闸门的臂一直是研究领域的热点话题弧形弧形闸门的动力稳定性。在这个论文中,简化空间框架作为分析模型,根据弹性体薄壁结构的扰动方程和梁单元模型和薄壁结构的梁单元模型,动态不稳定区域的弧形闸门可以通过有限元的方法,应用有限元的方法计算动态不稳定性的主要区域的弧形弧形闸门工作。此外,结合物理和数值模型,对识别新方法的参数共振钢弧形闸门提出了调查,本文不仅是重要的改进弧形闸门的参数振动的计算方法,但也为进一步研究弧形弧形闸门结构的动态稳定性打下了坚实的基础。 简介 低举升力,没有门槽,好流型,和操作方便等优点,使钢弧形闸门已经广泛应用于水工建筑物。弧形闸门的结构特点是液压完全作用于弧形闸门,通过门叶和主大梁,所以弧形闸门臂是主要的组件确保弧形闸门安全操作。如果周期性轴向载荷作用于手臂,手臂的不稳定是在一定条件下可能发生。调查指出:在弧形闸门的20次事故中,除了极特殊的破坏情况下,弧形闸门的破坏的原因是弧形闸门臂的不稳定;此外,明显的动态作用下发生破坏。例如:张山闸,位于中国的江苏省,包括36个弧形闸门。当一个弧形闸门打开放水时,门被破坏了,而其他弧形闸门则关闭,受到静态静水压力仍然是一样的,很明显,一个动态的加载是造成的弧形闸门破坏一个主要因素。因此弧形闸门臂的动态不稳定是造成弧形闸门(特别是低水头的弧形闸门)破坏的主要原是毫无疑问。

本科毕业设计方案外文翻译范本

I / 11 本科毕业设计外文翻译 <2018届) 论文题目基于WEB 的J2EE 的信息系统的方法研究 作者姓名[单击此处输入姓名] 指导教师[单击此处输入姓名] 学科(专业 > 所在学院计算机科学与技术学院 提交日期[时间 ]

基于WEB的J2EE的信息系统的方法研究 摘要:本文介绍基于工程的Java开发框架背后的概念,并介绍它如何用于IT 工程开发。因为有许多相同设计和开发工作在不同的方式下重复,而且并不总是符合最佳实践,所以许多开发框架建立了。我们已经定义了共同关注的问题和应用模式,代表有效解决办法的工具。开发框架提供:<1)从用户界面到数据集成的应用程序开发堆栈;<2)一个架构,基本环境及他们的相关技术,这些技术用来使用其他一些框架。架构定义了一个开发方法,其目的是协助客户开发工程。 关键词:J2EE 框架WEB开发 一、引言 软件工具包用来进行复杂的空间动态系统的非线性分析越来越多地使用基于Web的网络平台,以实现他们的用户界面,科学分析,分布仿真结果和科学家之间的信息交流。对于许多应用系统基于Web访问的非线性分析模拟软件成为一个重要组成部分。网络硬件和软件方面的密集技术变革[1]提供了比过去更多的自由选择机会[2]。因此,WEB平台的合理选择和发展对整个地区的非线性分析及其众多的应用程序具有越来越重要的意义。现阶段的WEB发展的特点是出现了大量的开源框架。框架将Web开发提到一个更高的水平,使基本功能的重复使用成为可能和从而提高了开发的生产力。 在某些情况下,开源框架没有提供常见问题的一个解决方案。出于这个原因,开发在开源框架的基础上建立自己的工程发展框架。本文旨在描述是一个基于Java的框架,该框架利用了开源框架并有助于开发基于Web的应用。通过分析现有的开源框架,本文提出了新的架构,基本环境及他们用来提高和利用其他一些框架的相关技术。架构定义了自己开发方法,其目的是协助客户开发和事例工程。 应用程序设计应该关注在工程中的重复利用。即使有独特的功能要求,也

毕业设计外文翻译原文.

Optimum blank design of an automobile sub-frame Jong-Yop Kim a ,Naksoo Kim a,*,Man-Sung Huh b a Department of Mechanical Engineering,Sogang University,Shinsu-dong 1,Mapo-ku,Seoul 121-742,South Korea b Hwa-shin Corporation,Young-chun,Kyung-buk,770-140,South Korea Received 17July 1998 Abstract A roll-back method is proposed to predict the optimum initial blank shape in the sheet metal forming process.The method takes the difference between the ?nal deformed shape and the target contour shape into account.Based on the method,a computer program composed of a blank design module,an FE-analysis program and a mesh generation module is developed.The roll-back method is applied to the drawing of a square cup with the ˉange of uniform size around its periphery,to con?rm its validity.Good agreement is recognized between the numerical results and the published results for initial blank shape and thickness strain distribution.The optimum blank shapes for two parts of an automobile sub-frame are designed.Both the thickness distribution and the level of punch load are improved with the designed blank.Also,the method is applied to design the weld line in a tailor-welded blank.It is concluded that the roll-back method is an effective and convenient method for an optimum blank shape design.#2000Elsevier Science S.A.All rights reserved. Keywords:Blank design;Sheet metal forming;Finite element method;Roll-back method

电气毕业设计外文文献

外文文献: The Intelligent Building One of the benefits of the rapid evolution of information technology has been the development of systems that can measure, evaluate, and respond to change。An enhanced ability to control change has sparked developments in the way we design our physical environment, in particular, the buildings in which we work。As a result, we are witnessing significant growth in the area of "Intelligent Buildings"--buildings that incorporate information technology and communication systems, making them more comfortable, secure, productive, and cost-effective What is an Intelligent Building? An Intelligent Building is one equipped with the telecommunications infrastructure that enables it to continuously respond and adapt to changing conditions, allowing for a more efficient use of resources and increasing the comfort and security of its occupants。An Intelligent Building provides these benefits through automated control systems such as: heating, ventilation, and air-conditioning (HVAC);fire safety;security;and energy/lighting management。For example, in the case of a fire, the fire alarm communicates with the security system to unlock the doors。The security system communicates with the HVAC system to regulate the flow of air to prevent the fire from spreading。 What benefits do Intelligent Buildings offer their owners and occupants? The introduction in the workplace of computers printers photocopiers, and fax machines has increased indoor pollution。Electrical and telecommunications facilities in office buildings are under pressure to satisfy the demands created by the rapid growth of computer and networking technologies。These factors have a definite impact on productivity. New technology can be used to create Intelligent Buildings that address these problems by providing a healthier, more productive, and less energy-intensive work environment。As these are critical factors for business

毕业设计外文翻译格式实例.

理工学院毕业设计(论文)外文资料翻译 专业:热能与动力工程 姓名:赵海潮 学号:09L0504133 外文出处:Applied Acoustics, 2010(71):701~707 附件: 1.外文资料翻译译文;2.外文原文。

附件1:外文资料翻译译文 基于一维CFD模型下汽车排气消声器的实验研究与预测Takeshi Yasuda, Chaoqun Wua, Noritoshi Nakagawa, Kazuteru Nagamura 摘要目前,利用实验和数值分析法对商用汽车消声器在宽开口喉部加速状态下的排气噪声进行了研究。在加热工况下发动机转速从1000转/分钟加速到6000转/分钟需要30秒。假定其排气消声器的瞬时声学特性符合一维计算流体力学模型。为了验证模拟仿真的结果,我们在符合日本工业标准(JIS D 1616)的消声室内测量了排气消声器的瞬态声学特性,结果发现在二阶发动机转速频率下仿真结果和实验结果非常吻合。但在发动机高阶转速下(从5000到6000转每分钟的四阶转速,从4200到6000转每分钟的六阶转速这样的高转速范围内),计算结果和实验结果出现了较大差异。根据结果分析,差异的产生是由于在模拟仿真中忽略了流动噪声的影响。为了满足市场需求,研究者在一维计算流体力学模型的基础上提出了一个具有可靠准确度的简化模型,相对标准化模型而言该模型能节省超过90%的执行时间。 关键字消声器排气噪声优化设计瞬态声学性能 1 引言 汽车排气消声器广泛用于减小汽车发动机及汽车其他主要部位产生的噪声。一般而言,消声器的设计应该满足以下两个条件:(1)能够衰减高频噪声,这是消声器的最基本要求。排气消声器应该有特定的消声频率范围,尤其是低频率范围,因为我们都知道大部分的噪声被限制在发动机的转动频率和它的前几阶范围内。(2)最小背压,背压代表施加在发动机排气消声器上额外的静压力。最小背压应该保持在最低限度内,因为大的背压会降低容积效率和提高耗油量。对消声器而言,这两个重要的设计要求往往是互相冲突的。对于给定的消声器,利用实验的方法,根据距离尾管500毫米且与尾管轴向成45°处声压等级相近的排气噪声来评估其噪声衰减性能,利用压力传感器可以很容易地检测背压。 近几十年来,在预测排气噪声方面广泛应用的方法有:传递矩阵法、有限元法、边界元法和计算流体力学法。其中最常用的方法是传递矩阵法(也叫四端网络法)。该方

本科毕业设计外文翻译

Section 3 Design philosophy, design method and earth pressures 3.1 Design philosophy 3.1.1 General The design of earth retaining structures requires consideration of the interaction between the ground and the structure. It requires the performance of two sets of calculations: 1)a set of equilibrium calculations to determine the overall proportions and the geometry of the structure necessary to achieve equilibrium under the relevant earth pressures and forces; 2)structural design calculations to determine the size and properties of thestructural sections necessary to resist the bending moments and shear forces determined from the equilibrium calculations. Both sets of calculations are carried out for specific design situations (see 3.2.2) in accordance with the principles of limit state design. The selected design situations should be sufficiently Severe and varied so as to encompass all reasonable conditions which can be foreseen during the period of construction and the life of the retaining wall. 3.1.2 Limit state design This code of practice adopts the philosophy of limit state design. This philosophy does not impose upon the designer any special requirements as to the manner in which the safety and stability of the retaining wall may be achieved, whether by overall factors of safety, or partial factors of safety, or by other measures. Limit states (see 1.3.13) are classified into: a) ultimate limit states (see 3.1.3); b) serviceability limit states (see 3.1.4). Typical ultimate limit states are depicted in figure 3. Rupture states which are reached before collapse occurs are, for simplicity, also classified and

毕业设计外文资料翻译译文

附件1:外文资料翻译译文 包装对食品发展的影响 一个消费者对某个产品的第一印象来说包装是至关重要的,包括沟通的可取性,可接受性,健康饮食形象等。食品能够提供广泛的产品和包装组合,传达自己加工的形象感知给消费者,例如新鲜包装/准备,冷藏,冷冻,超高温无菌,消毒(灭菌),烘干产品。 食物的最重要的质量属性之一,是它的味道,其影响人类的感官知觉,即味觉和嗅觉。味道可以很大程度作退化的处理和/或扩展存储。其他质量属性,也可能受到影响,包括颜色,质地和营养成分。食品质量不仅取决于原材料,添加剂,加工和包装的方法,而且其预期的货架寿命(保质期)过程中遇到的分布和储存条件的质量。越来越多的竞争当中,食品生产商,零售商和供应商;和质量审核供应商有显着提高食品质量以及急剧增加包装食品的选择。这些改进也得益于严格的冷藏链中的温度控制和越来越挑剔的消费者。 保质期的一个定义是:在食品加工和包装组合下,在食品的容器和条件,在销售点分布在特定系统的时间能保持令人满意的食味品质。保质期,可以用来作为一个新鲜的概念,促进营销的工具。延期或保质期长的产品,还提供产品的使用时间,方便以及减少浪费食物的风险,消费者和/或零售商。包装产品的质量和保质期的主题是在第3章中详细讨论。 包装为消费者提供有关产品的重要信息,在许多情况下,使用的包装和/或产品,包括事实信息如重量,体积,配料,制造商的细节,营养价值,烹饪和开放的指示,除了法律准则的最小尺寸的文字和数字,有定义的各类产品。消费者寻求更详细的产品信息,同时,许多标签已经成为多语种。标签的可读性是为视障人士的问题,这很可能成为一个对越来越多的老年人口越来越重要的问题。 食物的选择和包装创新的一个主要驱动力是为了方便消费者的需求。这里有许多方便的现代包装所提供的属性,这些措施包括易于接入和开放,处置和处理,产品的知名度,再密封性能,微波加热性,延长保质期等。在英国和其他发达经济体显示出生率下降和快速增长的一个相对富裕的老人人口趋势,伴随着更加苛

毕业设计外文翻译

毕业设计(论文) 外文文献翻译 题目:A new constructing auxiliary function method for global optimization 学院: 专业名称: 学号: 学生姓名: 指导教师: 2014年2月14日

一个新的辅助函数的构造方法的全局优化 Jiang-She Zhang,Yong-Jun Wang https://www.wendangku.net/doc/766966372.html,/10.1016/j.mcm.2007.08.007 非线性函数优化问题中具有许多局部极小,在他们的搜索空间中的应用,如工程设计,分子生物学是广泛的,和神经网络训练.虽然现有的传统的方法,如最速下降方法,牛顿法,拟牛顿方法,信赖域方法,共轭梯度法,收敛迅速,可以找到解决方案,为高精度的连续可微函数,这在很大程度上依赖于初始点和最终的全局解的质量很难保证.在全局优化中存在的困难阻碍了许多学科的进一步发展.因此,全局优化通常成为一个具有挑战性的计算任务的研究. 一般来说,设计一个全局优化算法是由两个原因造成的困难:一是如何确定所得到的最小是全球性的(当时全球最小的是事先不知道),和其他的是,如何从中获得一个更好的最小跳.对第一个问题,一个停止规则称为贝叶斯终止条件已被报道.许多最近提出的算法的目标是在处理第二个问题.一般来说,这些方法可以被类?主要分两大类,即:(一)确定的方法,及(ii)的随机方法.随机的方法是基于生物或统计物理学,它跳到当地的最低使用基于概率的方法.这些方法包括遗传算法(GA),模拟退火法(SA)和粒子群优化算法(PSO).虽然这些方法有其用途,它们往往收敛速度慢和寻找更高精度的解决方案是耗费时间.他们更容易实现和解决组合优化问题.然而,确定性方法如填充函数法,盾构法,等,收敛迅速,具有较高的精度,通常可以找到一个解决方案.这些方法往往依赖于修改目标函数的函数“少”或“低”局部极小,比原来的目标函数,并设计算法来减少该?ED功能逃离局部极小更好的发现. 引用确定性算法中,扩散方程法,有效能量的方法,和积分变换方法近似的原始目标函数的粗结构由一组平滑函数的极小的“少”.这些方法通过修改目标函数的原始目标函数的积分.这样的集成是实现太贵,和辅助功能的最终解决必须追溯到

电气自动化专业毕业论文英文翻译

电厂蒸汽动力的基础和使用 1.1 为何需要了解蒸汽 对于目前为止最大的发电工业部门来说, 蒸汽动力是最为基础性的。 若没有蒸汽动力, 社会的样子将会变得和现在大为不同。我们将不得已的去依靠水力发电厂、风车、电池、太阳能蓄电池和燃料电池,这些方法只能为我们平日用电提供很小的一部分。 蒸汽是很重要的,产生和使用蒸汽的安全与效率取决于怎样控制和应用仪表,在术语中通常被简写成C&I(控制和仪表 。此书旨在在发电厂的工程规程和电子学、仪器仪表以 及控制工程之间架设一座桥梁。 作为开篇,我将在本章大体描述由水到蒸汽的形态变化,然后将叙述蒸汽产生和使用的基本原则的概述。这看似简单的课题实际上却极为复杂。这里, 我们有必要做一个概述:这本书不是内容详尽的论文,有的时候甚至会掩盖一些细节, 而这些细节将会使热力学家 和燃烧物理学家都为之一震。但我们应该了解,这本书的目的是为了使控制仪表工程师充 分理解这一课题,从而可以安全的处理实用控制系统设计、运作、维护等方面的问题。1.2沸腾:水到蒸汽的状态变化 当水被加热时,其温度变化能通过某种途径被察觉(例如用温度计 。通过这种方式 得到的热量因为在某时水开始沸腾时其效果可被察觉,因而被称为感热。 然而,我们还需要更深的了解。“沸腾”究竟是什么含义?在深入了解之前,我们必须考虑到物质的三种状态:固态,液态,气态。 (当气体中的原子被电离时所产生的等离子气体经常被认为是物质的第四种状态, 但在实际应用中, 只需考虑以上三种状态固态,

物质由分子通过分子间的吸引力紧紧地靠在一起。当物质吸收热量,分子的能量升级并且 使得分子之间的间隙增大。当越来越多的能量被吸收,这种效果就会加剧,粒子之间相互脱离。这种由固态到液态的状态变化通常被称之为熔化。 当液体吸收了更多的热量时,一些分子获得了足够多的能量而从表面脱离,这个过程 被称为蒸发(凭此洒在地面的水会逐渐的消失在蒸发的过程中,一些分子是在相当低的 温度下脱离的,然而随着温度的上升,分子更加迅速的脱离,并且在某一温度上液体内部 变得非常剧烈,大量的气泡向液体表面升起。在这时我们称液体开始沸腾。这个过程是变为蒸汽的过程,也就是液体处于汽化状态。 让我们试想大量的水装在一个敞开的容器内。液体表面的空气对液体施加了一定的压 力,随着液体温度的上升,便会有足够的能量使得表面的分子挣脱出去,水这时开始改变 自身的状态,变成蒸汽。在此条件下获得更多的热量将不会引起温度上的明显变化。所增 加的能量只是被用来改变液体的状态。它的效用不能用温度计测量出来,但是它仍然发生 着。正因为如此,它被称为是潜在的,而不是可认知的热量。使这一现象发生的温度被称为是沸点。在常温常压下,水的沸点为100摄氏度。 如果液体表面的压力上升, 需要更多的能量才可以使得水变为蒸汽的状态。 换句话说, 必须使得温度更高才可以使它沸腾。总而言之,如果大气压力比正常值升高百分之十,水必须被加热到一百零二度才可以使之沸腾。

模具毕业设计外文翻译

冷冲模具使用寿命的影响及对策 冲压模具概述 冲压模具--在冷冲压加工中,将材料(金属或非金属)加工成零件(或半成品)的一种特殊工艺装备,称为冷冲压模具(俗称冷冲模)。冲压--是在室温下,利用安装在压力机上的模具对材料施加压力,使其产生分离或塑性变形,从而获得所需零件的一种压力加工方法。 冲压模具的形式很多,一般可按以下几个主要特征分类: 1.根据工艺性质分类 (1)冲裁模沿封闭或敞开的轮廓线使材料产生分离的模具。如落料模、冲孔模、切断模、切口模、切边模、剖切模等。 (2)弯曲模使板料毛坯或其他坯料沿着直线(弯曲线)产生弯曲变形,从而获得一定角度和形状的工件的模具。 (3)拉深模是把板料毛坯制成开口空心件,或使空心件进一步改变形状和尺寸的模具。 (4)成形模是将毛坯或半成品工件按图凸、凹模的形状直接复制成形,而材料本身仅产生局部塑性变形的模具。如胀形模、缩口模、扩口模、起伏成形模、翻边模、整形模等。 2.根据工序组合程度分类 (1)单工序模在压力机的一次行程中,只完成一道冲压工序的模具。 (2)复合模只有一个工位,在压力机的一次行程中,在同一工位上同时完成两道或两道以上冲压工序的模具。 (3)级进模(也称连续模)在毛坯的送进方向上,具有两个或更多的工位,在压力机的一次行程中,在不同的工位上逐次完成两道或两道以上冲压工序的模具。 冲冷冲模全称为冷冲压模具。 冷冲压模具是一种应用于模具行业冷冲压模具及其配件所需高性能结构陶瓷材料的制备方法,高性能陶瓷模具及其配件材料由氧化锆、氧化钇粉中加铝、镨元素构成,制备工艺是将氧化锆溶液、氧化钇溶液、氧化镨溶液、氧化铝溶液按一定比例混合配成母液,滴入碳酸氢铵,采用共沉淀方法合成模具及其配件陶瓷材料所需的原材料,反应生成的沉淀经滤水、干燥,煅烧得到高性能陶瓷模具及其配件材料超微粉,再经过成型、烧结、精加工,便得到高性能陶瓷模具及其配件材料。本发明的优点是本发明制成的冷冲压模具及其配件使用寿命长,在冲压过程中未出现模具及其配件与冲压件产生粘结现象,冲压件表面光滑、无毛刺,完全可以替代传统高速钢、钨钢材料。 冷冲模具主要零件 冷冲模具是冲压加工的主要工艺装备,冲压制件就是靠上、下模具的相对运动来完成的。加工时由于上、下模具之间不断地分合,如果操作工人的手指不断进入或停留在模具闭合区,便会对其人身安全带来严重威胁。

毕业设计(论文)外文资料翻译〔含原文〕

南京理工大学 毕业设计(论文)外文资料翻译 教学点:南京信息职业技术学院 专业:电子信息工程 姓名:陈洁 学号: 014910253034 外文出处:《 Pci System Architecture 》 (用外文写) 附件: 1.外文资料翻译译文;2.外文原文。 指导教师评语: 该生外文翻译没有基本的语法错误,用词准确,没 有重要误译,忠实原文;译文通顺,条理清楚,数量与 质量上达到了本科水平。 签名: 年月日 注:请将该封面与附件装订成册。

附件1:外文资料翻译译文 64位PCI扩展 1.64位数据传送和64位寻址:独立的能力 PCI规范给出了允许64位总线主设备与64位目标实现64位数据传送的机理。在传送的开始,如果回应目标是一个64位或32位设备,64位总线设备会自动识别。如果它是64位设备,达到8个字节(一个4字)可以在每个数据段中传送。假定是一串0等待状态数据段。在33MHz总线速率上可以每秒264兆字节获取(8字节/传送*33百万传送字/秒),在66MHz总线上可以528M字节/秒获取。如果回应目标是32位设备,总线主设备会自动识别并且在下部4位数据通道上(AD[31::00])引导,所以数据指向或来自目标。 规范也定义了64位存储器寻址功能。此功能只用于寻址驻留在4GB地址边界以上的存储器目标。32位和64位总线主设备都可以实现64位寻址。此外,对64位寻址反映的存储器目标(驻留在4GB地址边界上)可以看作32位或64位目标来实现。 注意64位寻址和64位数据传送功能是两种特性,各自独立并且严格区分开来是非常重要的。一个设备可以支持一种、另一种、都支持或都不支持。 2.64位扩展信号 为了支持64位数据传送功能,PCI总线另有39个引脚。 ●REQ64#被64位总线主设备有效表明它想执行64位数据传送操作。REQ64#与FRAME#信号具有相同的时序和间隔。REQ64#信号必须由系统主板上的上拉电阻来支持。当32位总线主设备进行传送时,REQ64#不能又漂移。 ●ACK64#被目标有效以回应被主设备有效的REQ64#(如果目标支持64位数据传送),ACK64#与DEVSEL#具有相同的时序和间隔(但是直到REQ64#被主设备有效,ACK64#才可被有效)。像REQ64#一样,ACK64#信号线也必须由系统主板上的上拉电阻来支持。当32位设备是传送目标时,ACK64#不能漂移。 ●AD[64::32]包含上部4位地址/数据通道。 ●C/BE#[7::4]包含高4位命令/字节使能信号。 ●PAR64是为上部4个AD通道和上部4位C/BE信号线提供偶校验的奇偶校验位。 以下是几小结详细讨论64位数据传送和寻址功能。 3.在32位插入式连接器上的64位卡

相关文档
相关文档 最新文档