下载文档原格式
外文原文computerThe modern world of high technology could not have come about except for the development of the computer. Different types and sizes of computers find uses throughout society in the storage and handling of data, from secret governmental files to banking transactions to private household accounts. Computers have opened up a new era in manufacturing through the techniques of automation, and they have enhanced modern communication systems. They are essential tools in almost every field of research and applied technology, from constructing models of the universe to producing tomorrow’s weather reports, and technique use has in itself opened up new areas of conjecture. Database services and computer networks make available a great variety of information sources. The same advanced techniques also make the invasions of privacy and restricted information sources possible, and computer crime has become one of the many risks that society must face if it is to enjoy the benefits of modern technology.A computer is an electronic device that can receive a set of instructions, or program, and then carry out this program by performing calculations on numerical data or by compiling and correlating other forms of information. The type of computers are mainly inclusive of Microcomputer, Minicomputer, Mainframe Computer and Supercomputer, etc. Microminiaturization , the effort to compress more circuit elements into smaller and smaller chip space is becoming the major trend in computer development. Besides, researchers are trying to develop more powerful and more advanced computers.Any customers all pass the operate system to use the calculator, not direct carry on the operation to the hardware of the calculators. The operate system is a bridge that communicates the customer and calculator. Every general-purpose computer must have an operating system to run other programs. Operating systems perform basic tasks and provide a software platform. The choice of operating systems determines to a great extent of the applications. Therefore OS is very important.The operate system is in the charge of Computer resource control program to execute system software. Say in a specific way，the OS is the most basic in the calculator software system, also constituting the part most importantly, it is responsible for the management and controls the calculator system in all hardware resources and the software resources, can make of various resources matched with mutually, moderating to work with one accord, full develop its function, exaltation the efficiency of the system, still take the interface function of the customer and the calculator system at the same time, use the calculator to provide the convenience for the customer. The operate system is a huge management control procedure, including 5 management functions mostly: Progress and processing the machine manage, the homework manage, saving management, equipments management, document management. Divide the line from the function, the tiny machine operate system can is divided into the single mission operate system, single many mission operate systems of customer and many mission operate systems of multi-user of single customer. At present there are several kinds of OS on the computer which are DOS, OS/2, UNIX, XENIX, LINUX, Window2000, Netware etc.In order for a computer to perform the required task, it must be given instructions in a language that it understands. However, the computer’s own binary based language, or machine language, is difficult for humans to use. Therefore, people devised an assembly language to shorten and simplify the process. In order to make a computer more friendly to use, programmers invented high level languages, such as COBOL, FORTRAN, ASSEMBLER, PASCAL, C++, etc, which made the computers easier to use. For the time being, HTML and XML are very useful languages as well.The database is often used to describe a collection of related data that is organized into an integrated, sophisticated structure that provides different people with varied access to the same data. A database management system is an extremely complex set of software programs that controls the organization, storage and retrieval of data in a database. A successful DBMS is often characterized with the four principal features: (1)Data Security and Integrity; (2)Interactive query; (3)Interactive data Entry and Updating; (4)Data Independence. The intelligent databases are becoming more popular in that they canprovide more validation. The researches on new types of database systems are underway.计算机倘若不是伴随着计算机的发展，现代世界的高端技术不可能出现。
文档从互联网中收集，已重新修正排版，word格式支持编辑，如有帮助欢迎下载支持。
实用文档毕业设计说明书英文文献及中文翻译学专JA V A programming language and JA V A platform The Java programming language and platform have emerged as major technologies for performing e-business functions. Java programming standards have enabled portability of applications and the reuse of application components across computing platforms. Sun Microsystems' Java Community Process continues to be a strong base for the growth of the Java infrastructure and language standards. This growth of open standards creates new opportunities for designers and developers of applications and services .Applications of JavaJava uses many familiar programming concepts and constructs and allows portability by providing a common interface through an external Java Virtual Machine (JVM). A virtual machine is a self-contained operating environment, created by a software layer that behaves as if it were a separate computer. Benefits of creating virtual machines include better exploitation of powerful computing resources and isolation of applications to preventcross-corruption and improve security.The JVM allows computing devices with limited processors or memory to handle more advanced applications by calling up software instructions inside the JVM to perform most of the work. This also reduces the size and complexity of Java applications because many of the core functions and processing instructions were built into the JVM. As a result, software developers no longer need to re-create the same application for every operating system. Java also provides security by instructing the application to interact with the virtual machine, which served as a barrier between applications and the core system, effectively protecting systems from malicious code.Among other things, Java is tailor-made for the growing Internet because it makes it easy to develop new, dynamic applications that could make the most of the Internet's power and capabilities. Java is now an open standard, meaning that no single entity controls its development and the tools for writing programs in the language are available to everyone. The power of open standards like Java is the ability to break down barriers and speed up progress.Today, you can find Java technology in networks and devices that range from the Internet and scientific supercomputers to laptops and cell phones, from Wall Street market simulators to home game players and credit cards. There are over 3 million Java developers and now there are several versions of the code. Most large corporations have in-house Java developers. In addition, the majority of key software vendors use Java in their commercial applications (Lazaridis, 2003).ApplicationsJava on the World Wide WebJava has found a place on some of the most popular websites in the world and the uses of Java continues to grow. Java applications not only provide unique user interfaces, they also help to power the backend of websites. Everybody is probably familiar with eBay and Amazon have been Java pioneers on the World Wide Web.eBayFounded in 1995, eBay enables e-commerce on a local, national and international basis with an array of Web sites.You can find it on eBay, even if you didn't know it existed. On a typical day, more than 100 million items are listed on eBay in tens of thousands of categories. on eBay; the world's largest online marketplace.eBay uses Java almost everywhere. To address some security issues, eBay chose Sun Microsystems' Java System Identity Manager as the platform for revamping its identity management system. The task at hand was to provide identity management for more than 12,000 eBay employees and contractors.Now more than a thousand eBay software developers work daily with Java applications. Java's inherent portability allows eBay to move to new hardware to take advantage of new technology, packaging, or pricing, without having to rewrite Java code.Amazon has created a Web Service application that enables users to browse their product catalog and place orders. uses a Java application that searches the Amazon catalog for books whose subject matches a user-selected topic. The application displays ten books that match the chosen topic, and shows the author name, book title, listprice, Amazon discount price, and the cover icon. The user may optionally view one review per displayed title and make a buying decision.Java in Data Warehousing & MiningAlthough many companies currently benefit from data warehousing to support corporate decision making, new business intelligence approaches continue to emerge that can be powered by Java technology. Applications such as data warehousing, data mining, Enterprise Information Portals and Knowledge Management Systems are able to provide insight into customer retention, purchasing patterns, and even future buying behavior.These applications can not only tell what has happened but why and what may happen given certain business conditions; As a result of this information growth, people at all levels inside the enterprise, as well as suppliers, customers, and others in the value chain, are clamoring for subsets of the vast stores of information to help them make business decisions. While collecting and storing vast amounts of data is one thing, utilizing and deploying that data throughout the organization is another.The technical challenges inherent in integrating disparate data formats, platforms, and applications are significant. However, emerging standards such as the Application Programming Interfaces that comprise the Java platform, as well as Extendable Markup Language technologies can facilitate the interchange of data and the development of next generation data warehousing and business intelligence applications. While Java technology has been used extensively for client side access and to presentation layer challenges, it is rapidly emerging as a significant tool for developing scaleable server side programs. The Java2 Platform, Enterprise Edition (J2EE) provides the object, transaction, and security support for building such systems.Metadata IssuesOne of the key issues that business intelligence developers must solve is that of incompatible metadata formats. Metadata can be defined as information about data or simply "data about data." In practice, metadata is what most tools, databases, applications, and other information processes use to define, relate, and manipulate data objects within their own environments. It defines the structure and meaning of data objects managed by an applicationso that the application knows how to process requests or jobs involving those data objects. Developers can use this schema to create views for users. Also, users can browse the schema to better understand the structure and function of the database tables before launching a query.To address the metadata issue, a group of companies have joined to develop the Java Metadata Interface (JMI) API. The JMI API permits the access and manipulation of metadata in Java with standard metadata services. JMI is based on the Meta Object Facility (MOF) specification from the Object Management Group (OMG). The MOF provides a model and a set of interfaces for the creation, storage, access, Metamodel and metadata interchange is done via XML and uses the XML Metadata Interchange (XMI) specification, also from the OMG. JMI leverages Java technology to create an end-to-end data warehousing and business intelligence solutions framework.Enterprise JavaBeansA key tool provided by J2EE is Enterprise JavaBeans (EJB), an architecture for the development of component-based distributed business applications. Applications written using the EJB architecture are scalable, transactional, secure, and multi-user aware. These applications may be written once and then deployed on any server platform that supportsJ2EE. The EJB architecture makes it easy for developers to write components, since they do not need to understand or deal with complex, system-level details such as thread management, resource pooling, and transaction and security management. This allows for role-based development where component assemblers, platform providers and application assemblers can focus on their area of responsibility further simplifying application development.Data Storage & AccessData stored in existing applications can be accessed with specialized connectors. Integration and interoperability of these data sources is further enabled by the metadata repository that contains metamodels of the data contained in the sources, which then can be accessed and interchanged uniformly via the JMI API. These metamodels capture the essential structure and semantics of business components, allowing them to be accessed and queried via the JMI API or to be interchanged via XML. Through all of these processes, the J2EEinfrastructure ensures the security and integrity of the data through transaction management and propagation and the underlying security architecture.To consolidate historical information for analysis of sales and marketing trends, a data warehouse is often the best solution. In this example, data can be extracted from the operational systems with a variety of Extract, Transform and Load tools (ETL). The metamodels allow EJBs designed for filtering, transformation, and consolidation of data to operate uniformly on data from diverse data sources as the bean is able to query the metamodel to identify and extract the pertinent fields. Queries and reports can be run against the data warehouse that contains information from numerous sources in a consistent, enterprise-wide fashion through the use of the JMI API.Java in Industrial SettingsMany people know Java only as a tool on the World Wide Web that enables sites to perform some of their fancier functions such as interactivity and animation. However, the actual uses for Java are much more widespread. Since Java is an object-oriented language, the time needed for application development is minimal.In addition, Java's automatic memory management and lack of pointers remove some leading causes of programming errors. Most importantly, application developers do not need to create different versions of the software for different platforms. The advantages available through Java have even found their way into hardware. The emerging new Java devices are streamlined systems that exploit network servers for much of their processing power, storage, content, and administration.Benefits of JavaThe benefits of Java translate across many industries, and some are specific to the control and automation environment. Java's ability to run on any platform enables the organization to make use of the existing equipment while enhancing the application.IntegrationWith few exceptions, applications running on the factory floor were never intended to exchange information with systems in the executive office, but managers have recently discovered the need for that type of information. Before Java, that often meant bringingtogether data from systems written on different platforms in different languages at different times. Integration was usually done on a piecemeal basis, once it worked, was unique to the two applications it was tying together. Additional integration required developing a brand new system from scratch, raising the cost of integration.ScalabilityAnother benefit of Java in the industrial environment is its scalability. Even when internal compatibility is not an issue, companies often face difficulties when suppliers with whom they share information have incompatible systems. This becomes more of a problem as supply-chain management takes on a more critical role which requires manufacturers to interact more with offshore suppliers and clients. The greatest efficiency comes when all systems can communicate with each other and share information seamlessly. Since Java is so ubiquitous, it often solves these problems.Dynamic Web Page DevelopmentJava has been used by both large and small organizations for a wide variety of applications beyond consumer oriented websites. Sandia, a multiprogram laboratory of the U.S. Department of Energy's National Nuclear Security Administration, has developed a unique Java application. The lab was tasked with developing an enterprise-wide inventory tracking and equipment maintenance system that provides dynamic Web pages.ConclusionOpen standards have driven the e-business revolution. As e-business continues to develop, various computing technologies help to drive its evolution. The Java programming language and platform have emerged as major technologies for performing e-business functions. the time needed for application development is minimal. Java also encourages good software engineering practices with clear separation of interfaces and implementations as well as easy exception handling. Java's automatic memory management and lack of pointers remove some leading causes of programming errors. The advantages available through Java have also found their way into hardware. The emerging new Java devices are streamlined systems that exploit network servers for much of their processing power, storage, content, and administration.。
About the T utorialXML stands for Ex tensible M arkup L anguage and is a text-based markup language derived from Standard Generalized Markup Language (SGML).This tutorial will teach you the basics of XML. The tutorial is divided into sections such as XML Basics, Advanced XML, and XML tools. Each of these sections contain related topics with simple and useful examples.AudienceThis reference has been prepared for beginners to help them understand the basic to advanced concepts related to XML. This tutorial will give you enough understanding on XML from where you can take yourself to a higher level of expertise. PrerequisitesBefore proceeding with this tutorial, you should have basic knowledge of HTML and JavaScript.Copyright & DisclaimerCopyright 2018 by Tutorials Point (I) Pvt. Ltd.All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher.We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or inthistutorial,******************************************T able of ContentsAbout the Tutorial (i)Audience (i)Prerequisites (i)Copyright & Disclaimer (i)Table of Contents (ii)XML BASICS (1)1.XML – Overview (2)XML Usage (2)What is Markup? (3)Is XML a Programming Language? (3)2.XML – Syntax (4)3.XML – Documents (9)Document Prolog Section (9)Document Elements Section (10)4.XML – Declaration (11)5.XML – Tags (14)Start Tag (14)End Tag (14)Empty Tag (14)XML Tags Rules (15)6.XML – Elements (16)Empty Element (16)XML Elements Rules (17)7.XML – Attributes (18)Attribute Types (19)Element Attribute Rules (20)8.XML – Comments (21)XML Comments Rules (21)9.XML – Character Entities (22)Types of Character Entities (22)10.XML – CDATA Sections (24)CDATA Rules (25)11.XML – Whitespaces (26)Significant Whitespace (26)Insignificant Whitespace (26)12.XML – Processing (27)Processing Instructions Rules (28)13.XML – Encoding (29)Encoding Types (29)14.XML – Validation (31)Well-formed XML Document (31)Valid XML Document (32)ADVANCE XML (33)15.XML – DTDs (34)Internal DTD (34)External DTD (36)Types (37)16.XML – Schemas (39)Definition Types (40)17.XML – Tree Structure (42)18.XML – DOM (45)19.XML – Namespaces (47)Namespace Declaration (47)20.XML – Databases (48)XML Database Types (48)XML- Enabled Database (48)XML TOOLS (50)21.XML – Viewers (51)Text Editors (51)Firefox Browser (52)Chrome Browser (52)Errors in XML Document (52)22.XML – Editors (54)Open Source XML Editors (54)23.XML – Parsers (55)24.XML – Processors (56)Types (56)XML Basics11.XML stands for E xtensible M arkup L anguage. It is a text-based markup language derived from Standard Generalized Markup Language (SGML).XML tags identify the data and are used to store and organize the data, rather than specifying how to display it like HTML tags, which are used to display the data. XML is not going to replace HTML in the near future, but it introduces new possibilities by adopting many successful features of HTML.There are three important characteristics of XML that make it useful in a variety of systems and solutions:∙XML is extensible: XML allows you to create your own self-descriptive tags or language, that suits your application.∙XML carries the data, does not present it: XML allows you to store the data irrespective of how it will be presented.∙XML is a public standard: XML was developed by an organization called the World Wide Web Consortium (W3C) and is available as an open standard.XML UsageA short list of XML usage says it all:∙XML can work behind the scene to simplify the creation of HTML documents for large web sites.∙XML can be used to exchange the information between organizations and systems.∙XML can be used for offloading and reloading of databases.∙XML can be used to store and arrange the data, which can customize your data handling needs.∙XML can easily be merged with style sheets to create almost any desired output.∙Virtually, any type of data can be expressed as an XML document.2What is Markup?XML is a markup language that defines set of rules for encoding documents in a format that is both human-readable and machine-readable. So, what exactly is a markup language? Markup is information added to a document that enhances its meaning in certain ways, in that it identifies the parts and how they relate to each other. More specifically, a markup language is a set of symbols that can be placed in the text of a document to demarcate and label the parts of that document.Following example shows how XML markup looks, when embedded in a piece of text:This snippet includes the markup symbols, or the tags such as <message>...</message> and <text>... </text>. The tags <message> and </message> mark the start and the end of the XML code fragment. The tags <text> and </text> surround the text Hello, world!. Is XML a Programming Language?A programming language consists of grammar rules and its own vocabulary which is used to create computer programs. These programs instruct the computer to perform specific tasks. XML does not qualify to be a programming language as it does not perform any computation or algorithms. It is usually stored in a simple text file and is processed by special software that is capable of interpreting XML.32.In this chapter, we will discuss the simple syntax rules to write an XML document. Following is a complete XML document:You can notice, there are two kinds of information in the above example: ∙Markup, like <contact-info>∙The text, or the character data, Tutorials Point and (040) 123-4567The following diagram depicts the syntax rules to write different types of markup and text in an XML document.Let us see each component of the above diagram in detail.4XML DeclarationThe XML document can optionally have an XML declaration. It is written as follows:Where version is the XML version and encoding specifies the character encoding used in the document.Syntax Rules for XML Declaration∙The XML declaration is case sensitive and must begin with "<?xml>" where "xml"is written in lower-case.∙If the document contains XML declaration, then it strictly needs to be the first statement of the XML document.∙The XML declaration strictly needs be the first statement in the XML document.∙An HTTP protocol can override the value of encoding that you put in the XML declaration.T ags and ElementsAn XML file is structured by several XML-elements, also called XML-nodes or XML-tags. The names of XML-elements are enclosed in triangular brackets < > as shown below:Syntax Rules for Tags and ElementsElement Syntax: Each XML-element needs to be closed either with start or with end elements as shown below:or in simple-cases, just this way:Nesting of Elements: An XML-element can contain multiple XML-elements as its children, but the children elements must not overlap. i.e., an end tag of an element must have the same name as that of the most recent unmatched start tag.56The following example shows incorrect nested tags:The following example shows correct nested tags:Root Element: An XML document can have only one root element. For example, following is not a correct XML document, because both the x andy elements occur at the top level without a root element:The following example shows a correctly formed XML document:Case Sensitivity: The names of XML-elements are case-sensitive. That means the name of the start and the end elements need to be exactly in the same case.For example, <contact-info> is different from <Contact-Info>.XML AttributesAn attribute specifies a single property for the element, using a name/value pair. An XML-element can have one or more attributes. For example:Here href is the attribute name and / is attribute value.Syntax Rules for XML Attributes∙Attribute names in XML (unlike HTML) are case sensitive. That is,HREF and href are considered two different XML attributes.∙Same attribute cannot have two values in a syntax. The following example shows incorrect syntax because the attribute b is specified twice:∙Attribute names are defined without quotation marks, whereas attribute values must always appear in quotation marks. Following example demonstrates incorrect xml syntax:In the above syntax, the attribute value is not defined in quotation marks.XML ReferencesReferences usually allow you to add or include additional text or markup in an XML document. References always begin with the symbol "&" which is a reserved character and end with the symbol ";". XML has two types of references:∙Entity References: An entity reference contains a name between the start and the end delimiters. For example, & where amp is name. The name refers toa predefined string of text and/or markup.∙Character References: These contain references, such as A, contains a hash mark (“#”) followed by a number. The number always refers to the Unicode code of a character. In this case, 65 refers to alphabet "A".XML T extThe names of XML-elements and XML-attributes are case-sensitive, which means the name of start and end elements need to be written in the same case. To avoid character encoding problems, all XML files should be saved as Unicode UTF-8 or UTF-16 files.Whitespace characters like blanks, tabs and line-breaks between XML-elements and between the XML-attributes will be ignored.Some characters are reserved by the XML syntax itself. Hence, they cannot be used directly. To use them, some replacement-entities are used, which are listed below:783.An XML document is a basic unit of XML information composed of elements and other markup in an orderly package. An XML document can contain a wide variety of data. For example, database of numbers, numbers representing molecular structure or a mathematical equation.XML Document ExampleA simple document is shown in the following example:The following image depicts the parts of XML document.Document Prolog SectionDocument Prolog comes at the top of the document, before the root element. This section contains:∙XML declaration∙Document type declarationYou can learn more about XML declaration in this chapter : XML Declaration.Document Elements SectionDocument Elements are the building blocks of XML. These divide the document into a hierarchy of sections, each serving a specific purpose. You can separate a document into multiple sections so that they can be rendered differently, or used by a search engine. The elements can be containers, with a combination of text and other elements.9You can learn more about XML elements in this chapter : XML Elements104.This chapter covers XML declaration in detail. XML declaration contains details that prepare an XML processor to parse the XML document. It is optional, but when used, it must appear in the first line of the XML document.SyntaxFollowing syntax shows XML declaration:Each parameter consists of a parameter name, an equals sign (=), and parameter value inside a quote. Following table shows the above syntax in detail:11RulesAn XML declaration should abide with the following rules:∙If the XML declaration is present in the XML, it must be placed as the first line in the XML document.∙If the XML declaration is included, it must contain version number attribute.∙The parameter names and values are case-sensitive.∙The names are always in lower case.∙The order of placing the parameters is important. The correct order is:version, encoding and standalone.∙Either single or double quotes may be used.∙The XML declaration has no closing tag, i.e. </?xml>XML Declaration ExamplesFollowing are few examples of XML declarations:XML declaration with no parameters:XML declaration with version definition:XML declaration with all parameters defined:XML declaration with all parameters defined in single quotes:125.Let us learn about one of the most important part of XML, the XML tags. XML tags form the foundation of XML. They define the scope of an element in XML. They can also be used to insert comments, declare settings required for parsing the environment, and to insert special instructions.We can broadly categorize XML tags as follows:Start T agThe beginning of every non-empty XML element is marked by a start-tag. Following is an example of start-tag:End T agEvery element that has a start tag should end with an end-tag. Following is an example of end-tag:Note, that the end tags include a solidus ("/") before the name of an element.Empty T agThe text that appears between start-tag and end-tag is called content. An element which has no content is termed as empty. An empty element can be represented in two ways as follows:A start-tag immediately followed by an end-tag as shown below:A complete empty-element tag is as shown below:Empty-element tags may be used for any element which has no content.13End of ebook previewIf you liked what you saw…Buy it from our store @ https://14。
javaweb英文参考文献以下是关于JavaWeb的英文参考文献的相关参考内容：1. Deepak Vohra. Pro XML Development with Java Technology. Apress, 2006.This book provides a comprehensive guide to XML development with Java technology. It covers topics such as XML basics, XML parsing using Java, XML validation, DOM and SAX APIs, XSLT transformation, XML schema, and SOAP-based web services. The book also includes numerous code examples and case studies to illustrate the concepts.2. Robert J. Brunner. JavaServer Faces: Introduction by Example. Prentice Hall, 2004.This book introduces the JavaServer Faces (JSF) framework, which is a part of the Java EE platform for building web applications. It provides a step-by-step guide to building JSF applications using various components and features such as user interface components, data validation, navigation handling, and backing beans. The book also covers advanced topics such as internationalization and security.3. Brett McLaughlin. Head First Servlets and JSP: Passing the Sun Certified Web Component Developer Exam. O'Reilly Media, 2008. This book is a comprehensive guide to the development of Java web applications using Servlets and JavaServer Pages (JSP). It covers topics such as HTTP protocol, Servlet lifecycle, request andresponse handling, session management, JSP syntax and directives, JSTL and EL expressions, deployment descriptors, and web application security. The book also includes mock exam questions to help readers prepare for the Sun Certified Web Component Developer exam.4. Hans Bergsten. JavaServer Pages, 3rd Edition. O'Reilly Media, 2011.This book provides an in-depth guide to JavaServer Pages (JSP) technology, which is used for creating dynamic web content. It covers topics such as JSP syntax, scriptlets and expressions, JSP standard actions, JSP custom tag libraries, error handling, JSP with databases, JSP and XML, and internationalization. The book also includes examples and best practices for using JSP effectively.5. Marty Hall, Larry Brown. Core Servlets and JavaServer Pages, 2nd Edition. Prentice Hall, 2003.This book is a comprehensive guide to building Java web applications using Servlets and JavaServer Pages (JSP). It covers topics such as Servlet API, HTTP protocol, session management, request and response handling, JSP syntax and directives, JSP custom tag libraries, database connectivity, and security. The book also includes numerous code examples and case studies to demonstrate the concepts.6. Michael Ernest. Java Web Services in a Nutshell. O'Reilly Media, 2003.This book provides a comprehensive reference to Java-based web services technology. It covers topics such as SOAP, WSDL, UDDI, and XML-RPC protocols, as well as Java API for XML-based web services (JAX-WS) and Java API for RESTful web services (JAX-RS). The book also includes examples and best practices for developing and deploying web services using Java technology. Please note that the above references are just a selection of some of the available books on the topic of JavaWeb. There are numerous other resources available that can provide more detailed information on specific aspects of JavaWeb development.。
XML中CDATA的运⽤CDATA术语，主要⽤于标记语⾔（SGML和XML）中直接的但是有关联的字符数据。
这个术语表明⽂档的某⼀部分是⼀个普通的的字符数据块⽽不是⾮字符数据或者拥有更特殊和限制结构的字符数据。
在⼀个XML⽂档或者⼀个经过解析的外部实体中，⼀个CDATA⽚段是⼀个元素内容中标记为解析器单纯地解释为⽂本数据的⽚段。
⼀个CDATA⽚段只不过是表达字符数据的⾃动转换语法。
在单独的CDATA⽚段中含有例如'<'和‘&’这样的字符和⼀个按照⼀般语法将它们转义为“<”和“&”字符的字符数据没有语义上的差别。
CDATA（character data）⽚段是⼀串其中含有可以被视为xml标记的字符，但是不会被解析器解析到的字符数据块。
CDATA与Comments(注释)的区别：CDATA仍然是document的⼀部分，⽽comment却不是；在CDATA中不可以含有“]]>”(CDEnd字符数据块结束标记)，⽽commnent中‘--’是⽆效的；在comment中参数实体引⽤⽆法被识别。
从结构良好的⽂档中选取三个⽚段反映上⾯的差异：<!ENTITY MyParamEntity "Has been expanded">参数实体已经被扩展<!--在这个注释中，可以使⽤]]>和其他保留字符（如<,>，&，'和''，但%MyParamEntity " Has been expandes"这个字符将不会展开（如果我检索这个节点的⽂本将包含%MyParamEntity⽽不是已扩展之后的）并且不能把两个破折号放在⼀起。
--><![CDATA[在这个字符数据块中可以任意使⽤双破折号（还有<，&，'，和"）%MyParamEntity;将扩展到⽂本“Has been expanded”...但是，我不能使⽤CEND字符序列‘]>’（如果我需要使⽤它，必须转义⼀个括号或⼤于号）。
外文原文：Database1.1Database conceptThe database concept has evolved since the 1960s to ease increasing difficulties in designing, building, and maintaining complex information systems (typically with many concurrent end-users, and with a large amount of diverse data). It has evolved together with database management systems which enable the effective handling of databases. Though the terms database and DBMS define different entities, they are inseparable: a database's properties are determined by its supporting DBMS and vice-versa. The Oxford English dictionary cites[citation needed] a 1962 technical report as the first to use the term "data-base." With the progress in technology in the areas of processors, computer memory, computer storage and computer networks, the sizes, capabilities, and performance of databases and their respective DBMSs have grown in orders of magnitudes. For decades it has been unlikely that a complex information system can be built effectively without a proper database supported by a DBMS. The utilization of databases is now spread to such a wide degree that virtually every technology and product relies on databases and DBMSs for its development and commercialization, or even may have such embedded in it. Also, organizations and companies, from small to large, heavily depend on databases for their operations.No widely accepted exact definition exists for DBMS. However, a system needs to provide considerable functionality to qualify as a DBMS. Accordingly its supported data collection needs to meet respective usability requirements (broadly defined by the requirements below) to qualify as a database. Thus, a database and its supporting DBMS are defined here by a set of general requirements listed below. Virtually all existing mature DBMS products meet these requirements to a great extent, while less mature either meet them or converge to meet them.1.2Evolution of database and DBMS technologyThe introduction of the term database coincided with the availability of direct-access storage (disks and drums) from the mid-1960s onwards. The term represented a contrast with the tape-based systems of the past, allowing shared interactive use rather than daily batch processing.In the earliest database systems, efficiency was perhaps the primary concern, but it was already recognized that there were other important objectives. One of the key aims was to make the data independent of the logic of application programs, so that the same data could be made available to different applications.The first generation of database systems were navigational,[2] applications typically accessed data by following pointers from one record to another. The two main data models at this time were the hierarchical model, epitomized by IBM's IMS system, and the Codasyl model (Network model), implemented in a number ofproducts such as IDMS.The Relational model, first proposed in 1970 by Edgar F. Codd, departed from this tradition by insisting that applications should search for data by content, rather than by following links. This was considered necessary to allow the content of the database to evolve without constant rewriting of applications. Relational systems placed heavy demands on processing resources, and it was not until the mid 1980s that computing hardware became powerful enough to allow them to be widely deployed. By the early 1990s, however, relational systems were dominant for all large-scale data processing applications, and they remain dominant today (2012) except in niche areas. The dominant database language is the standard SQL for the Relational model, which has influenced database languages also for other data models.Because the relational model emphasizes search rather than navigation, it does not make relationships between different entities explicit in the form of pointers, but represents them rather using primary keys and foreign keys. While this is a good basis for a query language, it is less well suited as a modeling language. For this reason a different model, the Entity-relationship model which emerged shortly later (1976), gained popularity for database design.In the period since the 1970s database technology has kept pace with the increasing resources becoming available from the computing platform: notably the rapid increase in the capacity and speed (and reduction in price) of disk storage, and the increasing capacity of main memory. This has enabled ever larger databases and higher throughputs to be achieved.The rigidity of the relational model, in which all data is held in tables with a fixed structure of rows and columns, has increasingly been seen as a limitation when handling information that is richer or more varied in structure than the traditional 'ledger-book' data of corporate information systems: for example, document databases, engineering databases, multimedia databases, or databases used in the molecular sciences. Various attempts have been made to address this problem, many of them gathering under banners such as post-relational or NoSQL. Two developments of note are the Object database and the XML database. The vendors of relational databases have fought off competition from these newer models by extending the capabilities of their own products to support a wider variety of data types.1.3General-purpose DBMSA DBMS has evolved into a complex software system and its development typically requires thousands of person-years of development effort.[citation needed] Some general-purpose DBMSs, like Oracle, Microsoft SQL Server, and IBM DB2, have been undergoing upgrades for thirty years or more. General-purpose DBMSs aim to satisfy as many applications as possible, which typically makes them even more complex than special-purpose databases. However, the fact that they can be used "off the shelf", as well as their amortized cost over many applications and instances, makes them an attractive alternative (Vsone-time development) whenever they meet an application's requirements.Though attractive in many cases, a general-purpose DBMS is not always the optimal solution: When certain applications are pervasive with many operating instances, each with many users, a general-purpose DBMS may introduce unnecessary overhead and too large "footprint" (too large amount of unnecessary, unutilized software code). Such applications usually justify dedicated development.Typical examples are email systems, though they need to possess certain DBMS properties: email systems are built in a way that optimizes email messages handling and managing, and do not need significant portions of a general-purpose DBMS functionality.1.4Database machines and appliancesIn the 1970s and 1980s attempts were made to build database systems with integrated hardware and software. The underlying philosophy was that such integration would provide higher performance at lower cost. Examples were IBM System/38, the early offering of Teradata, and the Britton Lee, Inc. database machine. Another approach to hardware support for database management was ICL's CAFS accelerator, a hardware disk controller with programmable search capabilities. In the long term these efforts were generally unsuccessful because specialized database machines could not keep pace with the rapid development and progress of general-purpose computers. Thus most database systems nowadays are software systems running on general-purpose hardware, using general-purpose computer data storage. However this idea is still pursued for certain applications by some companies like Netezza and Oracle (Exadata).1.5Database researchDatabase research has been an active and diverse area, with many specializations, carried out since the early days of dealing with the database concept in the 1960s. It has strong ties with database technology and DBMS products. Database research has taken place at research and development groups of companies (e.g., notably at IBM Research, who contributed technologies and ideas virtually to any DBMS existing today), research institutes, and Academia. Research has been done both through Theory and Prototypes. The interaction between research and database related product development has been very productive to the database area, and many related key concepts and technologies emerged from it. Notable are the Relational and the Entity-relationship models, the Atomic transaction concept and related Concurrency control techniques, Query languages and Query optimization methods, RAID, and more. Research has provided deep insight to virtually all aspects of databases, though not always has been pragmatic, effective (and cannot and should not always be: research is exploratory in nature, and not always leads to accepted or useful ideas). Ultimately market forces and real needs determine the selection of problem solutions and related technologies, also among those proposed by research. However, occasionally, not the best and most elegant solution wins (e.g., SQL). Along their history DBMSs and respective databases, to a great extent, have been the outcome of such research, while real product requirements and challenges triggered database research directions and sub-areas.The database research area has several notable dedicated academic journals (e.g., ACM Transactions on Database Systems-TODS, Data and Knowledge Engineering-DKE, and more) and annual conferences (e.g., ACM SIGMOD, ACM PODS, VLDB, IEEE ICDE, and more), as well as an active and quite heterogeneous (subject-wise) research community all over the world.1.6Database architectureDatabase architecture (to be distinguished from DBMS architecture; see below) may be viewed, to some extent, as an extension of Data modeling. It is used to conveniently answer requirements of different end-users from a same database, as well as for other benefits. For example, a financial department of a company needs the payment details of all employees as part of the company's expenses, but not other many details about employees, that are the interest of the human resources department. Thus different departments need different views of the company's database, that both include the employees' payments, possibly in a different level of detail (and presented in different visual forms). To meet such requirement effectively database architecture consists of three levels: external, conceptual and internal. Clearly separating the three levels was a major feature of the relational database model implementations that dominate 21st century databases.[13]The external level defines how each end-user type understands the organization of its respective relevant data in the database, i.e., the different needed end-user views.A single database can have any number of views at the external level.The conceptual level unifies the various external views into a coherent whole, global view.[13] It provides the common-denominator of all the external views. It comprises all the end-user needed generic data, i.e., all the data from which any view may be derived/computed. It is provided in the simplest possible way of such generic data, and comprises the back-bone of the database. It is out of the scope of the various database end-users, and serves database application developers and defined by database administrators that build the database.The Internal level (or Physical level) is as a matter of fact part of the database implementation inside a DBMS (see Implementation section below). It is concerned with cost, performance, scalability and other operational matters. It deals with storage layout of the conceptual level, provides supporting storage-structures like indexes, to enhance performance, and occasionally stores data of individual views (materialized views), computed from generic data, if performance justification exists for such redundancy. It balances all the external views' performance requirements, possibly conflicting, in attempt to optimize the overall database usage by all its end-uses according to the database goals and priorities.All the three levels are maintained and updated according to changing needs by database administrators who often also participate in the database design.The above three-level database architecture also relates to and being motivated by the concept of data independence which has been described for long time as a desired database property and was one of the major initial driving forces of the Relational model. In the context of the above architecture it means that changes made at a certain level do not affect definitions and software developed with higher level interfaces, and are being incorporated at the higher level automatically. For example, changes in the internal level do not affect application programs written using conceptual level interfaces, which saves substantial change work that would be needed otherwise.In summary, the conceptual is a level of indirection between internal and external. On one hand it provides a common view of the database, independent of different external view structures, and on the other hand it is uncomplicated by details of how the data is stored or managed (internal level). In principle every level, and even every external view, can be presented by a different data model. In practice usually a given DBMS uses the same data model for both the external and the conceptual levels (e.g., relational model). The internal level, which is hidden inside the DBMS and depends on its implementation (see Implementation section below), requires a different levelof detail and uses its own data structure types, typically different in nature from the structures of the external and conceptual levels which are exposed to DBMS users (e.g., the data models above): While the external and conceptual levels are focused on and serve DBMS users, the concern of the internal level is effective implementation details.中文译文：数据库1.1 数据库的概念数据库的概念已经演变自1960年以来，以缓解日益困难，在设计，建设，维护复杂的信息系统（通常与许多并发的最终用户，并用大量不同的数据）。
OBIEE Metadata Repository Deployment Guide Oracle FLEXCUBE Investor ServicingRelease 14.5.2.0.0[November] [2021]Table of Contents1.OBIEE METADATA REPOSITORY DEPLOYMENT GUIDE ................................................................ 1-1 1.1I NTRODUCTION........................................................................................................................................... 1-11.1.1Layers in RPD .................................................................................................................................... 1-11.1.2FCIS OBIEE RPD .............................................................................................................................. 1-2 1.2P REREQUISITES........................................................................................................................................... 1-21.2.1Hardware / Software Required .......................................................................................................... 1-2 1.3D EPLOYMENT IN OBIEE ............................................................................................................................ 1-31.3.1Rpd Connection Changes ................................................................................................................... 1-31.3.2Deploying RPD ................................................................................................................................ 1-101. OBIEE Metadata Repository Deployment Guide 1.1 IntroductionThe Oracle Business Intelligence Server is a stand-alone process that maintains the logical data model which it provides to BI Presentation Services via ODBC. Metadata is maintained for thedata model in a local proprietary file called the repository file (rpd). On the back-end, the BIServer connects to customer data stores via data source adaptors.1.1.1 Layers in RPDThe Physical layer defines the data sources to which Oracle BI Server submits queries and therelationships between physical databases and other data sources that are used to processmultiple data source queries. The recommended way to populate the Physical layer is byimporting metadata from databases and other data sources. The data sources can be of thesame or different varieties. You can import schemas or portions of schemas from existing datasources. Additionally, you can create objects in the Physical layer manually.When you import metadata, many of the properties of the data sources are configuredautomatically based on the information gathered during the import process. After import, you can also define other attributes of the physical data sources, such as join relationships, that might not exist in the data source metadata. There can be one or more data sources in the Physical layer, including databases, spreadsheets, and XML documents. In this example, you import andconfigure tables from the sample SH schema included with the Oracle 10g database.The Business Model and Mapping layer of the Administration Tool defines the business, orlogical, model of the data and specifies the mappings between the business model and thePhysical layer schemas. This is where the physical schemas are simplified to form the basis forthe users’ v iew of the data. The Business Model and Mapping layer of the Administration Toolcan contain one or more business model objects. A business model object contains the business model definitions and the mappings from logical to physical tables for the business model.The main purpose of the business model is to capture how users think about their business using their own vocabulary. The business model simplifies the physical schema and maps the users’business vocabulary to physical sources. Most of the vocabulary translates into logical columns in the business model. Collections of logical columns form logical tables. Each logical column (and hence each logical table) can have one or more physical objects as sources.There are two main categories of logical tables: fact and dimension. Logical fact tables containthe measures by which an organization gauges its business operations and performance. Logical dimension tables contain the data used to qualify the facts.The Presentation layer is built after the Physical layer and Business Model and Mapping layerand adds a level of abstraction over the Business Model and Mapping layer. It is the view of the data seen by end users in client tools and applications, such as Oracle BI Answers. ThePresentation layer provides a means to further simplify or customize the Business Model andMapping layer for end users. For example, you can organize columns into catalogs and folders.Simplifying the view of the data for users makes it easier to craft queries based on users’business needs because you can expose only the data that is meaningful to the users, organize the data in a way that aligns with the way users think about the data, and rename data asnecessary for the set of users.You typically create Presentation layer objects by dragging objects from the Business Model and Mapping layer. Corresponding objects are automatically created in the Presentation layer.Presentation layer objects can then be renamed and reorganized.1.1.2 FCIS OBIEE RPDIn FCIS OBIEE we have a single RPD. In this document we will see how merge a RPD to FCISMetadata RPD. We will also see how to deploy sample dashboards generated using these RPDs.1.2 Prerequisites1.2.1 Hardware / Software Required1.3 Deployment in OBIEE 1.3.1 Rpd Connection Changes1. Open OBIEE Administration tool.2. Open rpd in offline mode.3. Enter Password: Weblogic123 and click ‘OK’.4. Double click on connection pool.5. Change Data source name.6. Change Data source name for the marked info given in the below format:(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <Host Address>)(PORT = <Port>)))(CONNECT_DATA = (SERVICE_NAME <Servicename>) ) )7. Enter User ID and password and click OK. Again enter the same password when it prompts.Save the Rpd changes.8. Click ‘OK’ and the follwing screen is displayed:9. Click ‘OK’ and the following screen is displayed:10. Click ‘’Yes.11. Click ‘’Close in below window.1.3.2 Deploying RPDEarlier OBIEE RPD deployment was through Enterprise manager, now a command from putty.sh data-model-cmd.sh uploadrpd -I <rpd name> -W <RPD password> -SI ssi -U <console user name> -P <console password>Eg: sh data-model-cmd.sh uploadrpd -I FCIS.rpd -W weblogic123 -SI ssi -U weblogic -Pweblogic123.OBIEE Metadata Repository Deployment Guide[November] [2021]Version 14.5.2.0.0Oracle Financial Services Software LimitedOracle ParkOff Western Express HighwayGoregaon (East)Mumbai, Maharashtra 400 063IndiaWorldwide Inquiries:Phone: +91 22 6718 3000Fax:+91 22 6718 3001/financialservices/Copyright © [2007], [2021], Oracle and/or its affiliates.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.。
１美国国立临床诊疗指南数据库（ＮａｔｉｏｎａｌＧｕｉｄｅｌｉｎｅＣｌｅａｒｉｎｇｈｏｕｓｅ，ＮＧＣ）概况[1]ＮＧＣ是由美国卫生健康研究与质量机构（Ａ－ｇｅｎｃｙｆｏｒＨｅａｌｔｈｃａｒｅＲｅｓｅａｒｃｈａｎｄＱｕａｌｉｔｙ，ＡＨＲＱ）、美国医学会（ＡｍｅｒｉｃａｎＭｅｄｉｃａｌＡｓｓｏｃｉａｔｉｏｎ，ＡＭＡ）和美国卫生健康计划协会（ＡｍｅｒｉｃａｎＡｓｓｏｃｉａｔｉｏｎｏｆＨｅａｌｔｈＰｌａｎｓ，ＡＡＨＰ）于１９９８年联合创立的一个提供临床实践指南和相关证据的免费数据库，目前收录有来自全世界３１０个机构发布的２４００余篇指南。
１．１ＮＧＣ的服务内容ＮＧＣ为用户提供涵盖各种医学与健康主题的循证临床实践指南，另外还提供指南的专家点评意见以及相关医学信息。
ＮＧＣ并不直接提供指南的原文，而是提供经过编辑人员对原指南进行分析、归纳后的指南摘要，以便于用户能够迅速、准确地了解指南内容。
ＮＧＣ也提供指南原文的链接以供用户查阅。
１．２数据的更新该数据库每周进行１次更新，主要内容为新增的指南和对现有指南的修订，另外还包括最新的健康资讯、医学进展。
更新的信息将会发布在首页的“本周更新（ＮｅｗＴｈｉｓＷｅｅｋ）”和“公告（Ａｎｎｏｕｎｃｅｍｅｎｔｓ）”上。
如果用户订阅了Ｅ－ｍａｉｌ服务，更新的内容还会以邮件的形式发送到指定的邮箱，每一条信息都附有最近更新的日期。
美国国立临床诊疗指南数据库介绍汪宏包旭（四川大学华西药学院药理教研室，四川成都６１００４１）【摘要】美国国立临床诊疗指南数据库是目前全球具有影响力的临床实践指南数据库之一。
本文通过对其数据库内容、服务方式以及功能特点等信息的介绍和分析，希望为国内广大医药专业人员了解和获取国际最新、最有效的临床实践指南提供参考。
【关键词】美国国立临床治疗指南数据库；临床实践指南；数据库ｄｏｉ：１０．３９６９／ｊ．ｉｓｓｎ．１６７２－５４３３．２０１３．０１．０１１An Introduction of the National Guideline Clearinghouse of the USAＷａｎｇＨｏｎｇ，ＢａｏＸｕ（ＰｈａｒｍａｃｏｌｏｇｙＤｅｐａｒｔｍｅｎｔｏｆＷｅｓｔＣｈｉｎａＰｈａｒｍａｃｙＣｏｌｌｅｇｅｏｆＳｉｃｈｕａｎＵｎｉｖｅｒｓｉｔｙ，ＳｉｃｈｕａｎＣｈｅｎｇｄｕ６１００４１，Ｃｈｉｎａ）ABSTRACTＴｈｅＮａｔｉｏｎａｌＧｕｉｄｅｌｉｎｅＣｌｅａｒｉｎｇｈｏｕｓｅ（ＮＧＣ）ｏｆｔｈｅＵＳＡｉｓｏｎｅｏｆｔｈｅｉｎｆｌｕｅｎｔｉａｌａｎｄｃｏｍｐｒｅｈｅｎｓｉｖｅｄａｔａｂａｓｅｓｏｆｔｈｅｃｌｉｎｉｃａｌｐｒａｃｔｉｃｅｇｕｉｄｅｌｉｎｅｓ（ＣＰＧｓ）ｉｎｔｈｅｗｏｒｌｄ．Ｂａｓｅｄｏｎｔｈｅｉｎｔｒｏｄｕｃｔｉｏｎａｎｄａｎａｌｙｓｉｓｏｆｔｈｅｃｏｎｔｅｎｔｓ，ｔｈｅｗａｙｏｆｓｅｒｖｉｃｅｓ，ｃｈａｒａｃｔｅｒｉｓｔｉｃｓａｎｄｆｕｎｃｔｉｏｎｓｏｆｔｈｉｓｄａｔａｂａｓｅ，ｔｈｉｓａｒｔｉｃｌｅｐｒｏｖｉｄｅｄｒｅｆｅｒｅｎｃｅｓｆｏｒｄｏｍｅｓｔｉｃｍｅｄｉｃａｌａｎｄｐｈａｒｍａｃｅｕｔｉｃａｌｐｒｏｆｅｓｓｉｏｎａｌｓｗｉｔｈｔｏｌｅａｒｎａｎｄａｃｑｕｉｒｅｔｈｅｌａｔｅｓｔａｎｄｔｈｅｍｏｓｔｅｆｆｅｃｔｉｖｅＣＰＧｓ．KEY WORDSＮａｔｉｏｎａｌＧｕｉｄｅｌｉｎｅＣｌｅａｒｉｎｇｈｏｕｓｅ；ＣｌｉｎｉｃａｌＰｒａｃｔｉｃｅＧｕｉｄｅｌｉｎｅｓ；Ｄａｔａｂａｓｅ作者简介：汪宏，女，硕士，助教。
