計(jì)算機(jī)專業(yè)畢業(yè)設(shè)計(jì)外文文獻(xiàn)翻譯部分

1、<p>　　畢 業(yè) 設(shè) 計(jì)(論文) 材 料</p><p>　　（外文文獻(xiàn)翻譯部分）</p><p><b>　　一、目的： </b></p><p>　　1．了解國(guó)外相關(guān)知識(shí)的發(fā)展；</p><p>　　2．熟悉外文科技文獻(xiàn)的寫作格式及特點(diǎn)；</p><p>　　3．熟悉和鞏固所學(xué)專業(yè)

2、外語(yǔ)的有關(guān)知識(shí)；</p><p>　　4．學(xué)會(huì)中英（外）文文獻(xiàn)的檢索方法。</p><p><b>　　二、選題要求：</b></p><p>　　1．學(xué)生自主選題，經(jīng)指導(dǎo)教師審查合格。</p><p>　　2．篇幅在3000漢字以上，較完整的一篇外文論文</p><p>　　3．內(nèi)容與所學(xué)專業(yè)相

3、關(guān)，并注明來(lái)源。</p><p><b>　　三、譯文要求：</b></p><p>　　1．譯文正確，內(nèi)容完整，圖可以復(fù)印后貼于適當(dāng)位置。</p><p>　　2．譯文打印在A4紙上，原稿復(fù)印后附在譯文后。</p><p><b>　　四、時(shí)間安排：</b></p><p>

4、;　　在畢業(yè)設(shè)計(jì)開題一周內(nèi)完成。</p><p><b>　　文獻(xiàn)資料詳細(xì)一覽表</b></p><p><b>　　英文部分：</b></p><p>　　6.Integrating with Other Technologies</p><p>　　In previous chapters we

5、 have covered the techniques for integrating external technologies with Struts2. To recap, here are the techniques:</p><p>　　·?Interceptors – can change the user’s workflow, modified the result and inje

6、ct objects into the action</p><p>　　·?Result Types – allows post-processing, and additional result-based processing or rendering of information returned by the action</p><p>　　·?Plug-i

7、n packages – new interceptors, result types, results and actions can be packaged together into a plug-in that can be re-used across many projects</p><p>　　·?Plug-in extensions points – allows new implem

8、entations of the core framework classes to be substituted in to Struts2, thus changing the way the framework behaves.</p><p>　　The goal of this chapter is not to describe every and each of the integration op

9、tions in detail, but rather to provide a brief overview to what types of integrations are possible, how the integration is achieved, some basic configuration information and where to find more information. This chapter i

10、s also not intended to provide information on how to use the library used for integration, but assumes that the reader understands the functionality already. Up-to-date information regarding all integ</p><p>

11、;　　Page Decoration and Layout</p><p>　　Developing web applications usually means there is going to be a standard page layout that is used for the entire application, as well as a selection of additional layo

12、uts to be used for various modules, pages and wizards. Depending on whether your preference is to specify the layout, or to let the URL specify the layout, you will most likely choose either Struts Tilesxi or</p>

13、<p>　　SiteMeshxii. Struts2 provides integrations for both these layout</p><p>　　technologies.</p><p><b>　　SiteMesh</b></p><p>　　SiteMesh is installed by adding the

14、plug-inxiii into your web applications “/WEB-INF/lib” directory or by adding a</p><p>　　dependency to your Maven2 “pom.xml” build file:</p><p>　　<dependency></p><p>　　<grou

15、pId>org.apache.struts</groupId></p><p>　　<artifactId>struts2-sitemesh-plugin</artifactId></p><p>　　<version>2.0.6</version></p><p>　　</dependency

16、></p><p>　　A servlet filter also needs to be configured. This filter enables access to the value stack from the SiteMesh decorators, and ensures that the ActionContext is cleaned up when the decorator has

17、 finished (and not before).</p><p><b>　　<filter></b></p><p>　　<filter-name>struts-cleanup</filter-name></p><p>　　<filter-class></p><p&

18、gt;　　org.apache.struts2.dispatcher.ActionContextCleanUp</p><p>　　</filter-class></p><p><b>　　</filter></b></p><p>　　If you are using Freemarker or Velocity f

19、or page rendering, you will need to add one of these additional filters:</p><p><b>　　<filter></b></p><p>　　<filter-name>sitemesh</filter-name></p><p>　

20、　<filter-class></p><p>　　org.apache.struts2.sitemesh.FreeMarkerPageFilter</p><p>　　</filter-class></p><p><b>　　</filter></b></p><p><b&

21、gt;　　<filter></b></p><p>　　<filter-name>sitemesh</filter-name></p><p>　　<filter-class></p><p>　　org.apache.struts2.sitemesh.VelocityPageFilter</p>

22、;<p>　　</filter-class></p><p><b>　　</filter></b></p><p>　　Finally, the order of the filter mappings is important. Both the “struts-cleanup” and the “sitemesh” (if

23、used) filter need to be configured before the “struts” (FilterDispatcher) filter:</p><p>　　<filter-mapping></p><p>　　<filter-name>struts-cleanup</filter-name></p><p&

24、gt;　　<url-pattern>/*</url-pattern></p><p>　　</filter-mapping></p><p>　　<filter-mapping></p><p>　　<filter-name>sitemesh</filter-name></p>&

25、lt;p>　　<url-pattern>/*</url-pattern></p><p>　　</filter-mapping></p><p><b>　　…</b></p><p>　　<filter-mapping></p><p>　　<filter-n

26、ame>struts</filter-name></p><p>　　<url-pattern>/*</url-pattern></p><p>　　</filter-mapping></p><p>　　The specific decorator files for the web application c

27、an now be developed, and configured to match specific URL patterns or metadata in “decorators.xml”.</p><p><b>　　Tiles</b></p><p>　　Apache Tiles, just like SiteMesh, is installed by a

28、dding the plugin xiv into your web applications “/WEB-INF/lib” directory or by adding a dependency to your Maven2 “pom.xml” build file:</p><p>　　<dependency></p><p>　　<groupId>org.ap

29、ache.struts</groupId></p><p>　　<artifactId>struts2-tiles-plugin</artifactId></p><p>　　<version>2.0.6</version></p><p>　　</dependency></p>

30、<p>　　In order to load the tiles configuration, a servlet listener needs to be configured:</p><p>　　<listener></p><p>　　<listener-class></p><p>　　org.apache.struts2

31、.tiles.StrutsTilesListener</p><p>　　</listener-class></p><p>　　</listener></p><p>　　The listener loads the “tiles.xml” configuration file, which defines each tile for yo

32、ur application, from the “WEB-INF” directory. Unlike SiteMesh, Tiles are implemented as a new result type. Each action result that wishes to use a Tiles layout needs to provide the attribute “type” with value “tiles” (or

33、 alternately set the Tiles result to be the default), and provide the name of the tile to use. The Tile name needs to be defined in the configuration file “tiles.xml”.</p><p>　　<action name="my"

34、 class="com.fdar.infoq.MyAction" ></p><p>　　<result type="tiles">myaction.layout</result></p><p><b>　　</action></b></p><p>　　Ver

35、sion 2 of Tiles is used in Struts2. This version has not yet had a stable release and could undergo further change. For this reason Tiles support is currently marked as experimental in Struts2.</p><p>　　Busi

36、ness Services / Dependency Injection</p><p>　　The Spring Framework plug-in is the preferred dependency injection (DI) or inversion of control (IoC) container for Struts2, and as such is responsible for provi

37、ding fully configured business service instances to actions.</p><p>　　There are several options available, each at different levels of stability:</p><p>　　·?The Plexusxv plug-in is a new ad

38、dition to the code base, and it is currently marked as experimental. By using a Plexus id, rather than the class name in any of the “struts.xml” configuration file entries, Plexus will create the class instance and injec

39、t all dependencies it is aware.of. More information of the plug-in can be found at http://cwiki.apache.org/S2PLUGINS/plexus-plugin.html.</p><p>　　·?PicoContainerxvi is another option for an IoC containe

40、r and although WebWork provided support, a Struts2 plugin does not currently exist.</p><p>　　·?EJB3, although not an IoC container, is another technology that can be used to provide business services to

41、 your actions. EJB3 is currently not supported via plug-ins; however the implementation would be simple.</p><p>　　There are three options available – implement a custom ObjectFactory to obtain EJB references

42、 for actions and install the new factory in your web application using the “struts.objectFactory” property in the “struts.properties” configuration file; create a new interceptor that interrogates each actions and inject

43、s an EJB reference as required; or use the Spring framework plug-in to access either JPA or EJBs; a tutorial is provide at http://cwiki.apache.org/S2WIKI/struts-2-spring-jpaajax.</p><p>　　As the Spring Frame

44、work is the preferred library, we are going to focus on it.</p><p>　　Spring Framework</p><p>　　Installing Spring support involves downloading and copying the Spring plug-inxvii into your web app

45、lications “/WEB-INF/lib” directory or adding the Spring plug-in as a dependency to your.</p><p>　　Maven2 “pom.xml” build file:</p><p>　　<dependency></p><p>　　<groupId>or

46、g.apache.struts</groupId></p><p>　　<artifactId>struts2-spring-plugin</artifactId></p><p>　　<version>2.0.6</version></p><p>　　</dependency></p&

47、gt;<p>　　To the “web.xml” configuration file you will need to add two blocks of code. The first registers a listener that enables Spring integration for application objects:</p><p>　　102 | STARTING ST

48、RUTS2</p><p>　　<listener></p><p>　　<listener-class></p><p>　　org.springframework.web.context.ContextLoaderListener</p><p>　　</listener-class></p>

49、;<p>　　</listener></p><p>　　And then the location of the Spring configuration file needs to be specific. In this case, any XML file starting with</p><p>　　“applicationContext” will

50、be loaded:</p><p>　　<context-param></p><p>　　<param-name>contextConfigLocation</param-name></p><p>　　<param-value></p><p>　　classpath*:applicati

51、onContext*.xml</p><p>　　</param-value></p><p>　　</context-param></p><p>　　You are now ready to go with Spring support. Any object that needs to be created will be delega

52、ted to the Spring object factory. If it knows how to create the object instance it will,</p><p>　　otherwise the responsibility will fall back to the framework to create the instance.</p><p>　　Fo

53、r all objects created, whether by the Spring object factory or by Struts2, Spring will be consulted to determine whether it manages any dependant objects. As the default DI container, it will obtain an instance of any de

54、pendant objects and set them on the target object instance as necessary. This is especially important for the action class, as the action itself will most likely be created by Struts2 but it will need to have its busines

55、s</p><p>　　services injected by Spring. Another important factor is how the dependency wiring is</p><p>　　determined. For the following class, should Spring inject the bean with an id value of “

56、service” or class type “MyService”?</p><p>　　public class MyAction {</p><p>　　private MyService myService;</p><p>　　public void setService( MyService service ) {</p><p>

57、;　　myService = service;</p><p><b>　　}</b></p><p>　　public String execute() {</p><p><b>　　…</b></p><p><b>　　}</b></p><p>

58、;<b>　　}</b></p><p>　　The answer is the id with value “service”, but this can be configured. The property in the “struts.properties” file that need to be modified is “struts.objectFactory.spring.a

59、utoWire” – by default this value is “name” but there are four options:</p><p>　　Value Description</p><p>　　name Spring uses the name / id value in the bean definition to auto-wire the bean. type

60、 Spring uses the class name in the bean definition to auto-wire the bean. auto Spring will determine the best method of wiring the bean. constructor Spring will auto-wire via the beans constructor.</p><p>　　

61、There is also a way to have the action completely managed byThere is also a way to have the action completely managed by Spring. This is a more complex configuration, and those that are interested can refer to the Spring

62、 plug-in documentation.</p><p><b>　　Databases</b></p><p>　　There is nothing special that enables database integration in Struts2, however, there are different ways that database acce

63、ss can be employed:</p><p>　　·?Via Tag Libraries – since you are using an action based framework this is probably not the best option, but it is possible; data can be accessed directly from JSPs via tag

64、</p><p>　　libraries (JSTL or custom libraries) that then format the information</p><p>　　·?Custom DAOs via Dependency Injection – if you are using dependency inject, you can take advantage

65、of the library to inject in your custom data access objects (DAO) that are required in the action; once the action has a reference to the DAO, it can call the methods as if it had created the instance itself</p>&

66、lt;p>　　·?DAO / ORM via Dependency Injection – if you are taking advantage of advanced DAO or ORM libraries (such as iBatis or Hibernate) you should invest in utilizing a fullyfeatures dependency injection framewo

67、rk such as Spring; Spring provides everything necessary to configure and initialize many different DAO and ORM libraries, requiring very little from the actions; when the action is ready for the business logic to be exec

68、uted, all the necessary data access object instances are ready to go</p><p>　　·?Accessed Indirectly via Business Services – instead of accessing the data access object directly, the calls are made indir

69、ectly via business services; the business service, like the previous options, are injected into the action by the dependency injection framework</p><p>　　As a side note, if you are thinking about utilizing H

70、ibernate as an ORM technology on your project, investigate the “OpenSessionInView” filter or interceptor. Having the Hibernate session open until the rendering of the JSP is complete allows Hibernate to perform lazy-load

71、ing fetches to the database successfully. Otherwise, the action or business service or DAO would need to pre-fetch all the collections that the JSP needs</p><p>　　ahead of time.</p><p><b>

72、　　Security</b></p><p>　　Like database integration, there is nothing special that provides security integration in Struts2. It is up to the application architect or developer to decide at which layers i

73、n the</p><p>　　infrastructure or application authorization and authentication occur.</p><p>　　Authentication can occur:</p><p>　　·?External to the application – an example woul

74、d be a single sign-on (SSO) server or authentication modules provided by the application server</p><p>　　·?Within the application – via a HTML form or another type of challenge-response mechanism </p

75、><p>　　Authorization can occur:</p><p>　　·?At the URI level – each URI that is requested is matched against the user credentials (that made the request) to see if they are allowed access</p

76、><p>　　·?At the sub-page level – there may be certain sections of a page can only be viewed, modified or have action performed for particular access levels</p><p>　　·?At the action level

77、– each action may be required todetermine access levels before performing businessoperations or logic</p><p>　　·?At the business service level – each method on a business service may be required to dete

78、rmine access levels before performing logic</p><p>　　·?At the domain object or database level – for a generic method call to obtain data or domain objects, different results could be returned depending

79、on the callers’ access level</p><p>　　From the perspective of a Struts2 web application, the user is authenticated to access the URL or not. Once the user is allowed</p><p>　　to access the appli

80、cation, there are a couple of options. The first is that an external solution provides the users’ credentials via the HttpServletRequest object. From here, the username and as well the users role information can be acces

81、sed at the action level (by implementing the PrincipalAware interface and configuring the “servlet-config” on the interceptor stack) and exposed from the action to the page being rendered.</p><p>　　Existing

82、Struts2 tags can then be used to limit access depending on roles.</p><p>　　Next, is that the users’ credentials to the HttpServletRequest haven’t been populated. In this case an interceptor needs to be devel

83、oped to authenticate and obtain the necessary role information, and to populate the information. This may be as complex as developing the logon form, logon and logoff code, authentication logic, etc., or it may be as sim

84、ple as obtaining the information from an exposed API and setting it on the action. The last case is when a 3rd party solution does everything for yo</p><p>　　would only be necessary if the authorization info

85、rmation is required during the processing of the action. In this case, an interceptor could be paired with an action interface to supply the Authz instance to the action. More details on this approach can be found at htt

86、p://struts.apache.org/2.x/docs/can-we-use-acegisecurity-</p><p><b>　　中文部分：</b></p><p><b>　　6.其他技術(shù)集成 </b></p><p>　　在先前的章節(jié)中，我們已經(jīng)介紹了Struts2中用于與其他技術(shù)集成的一些技術(shù)。下面我們?cè)?/p>

87、來(lái)復(fù)習(xí)一下，它們包括： </p><p>　　· 攔截器——可以更改用戶的工作流程，修改結(jié)果，把對(duì)象注入Action。</p><p>　　· 結(jié)果類型——允許進(jìn)行事后處理，額外的基于結(jié)果的處理，或是對(duì)Action返回的信息進(jìn)行渲染. </p><p>　　· 插件包——新的攔截器，結(jié)果類型，結(jié)果和Action可以被打包到插件里面，以便

88、在多個(gè)項(xiàng)目中重用。</p><p>　　· 插件擴(kuò)展點(diǎn)——Struts2中， 可以用新的核心框架類的實(shí)現(xiàn)來(lái)進(jìn)行替換，從而改變框架的行為。</p><p>　　本章的目的不是對(duì)每一個(gè)集成點(diǎn)的細(xì)節(jié)進(jìn)行面面俱到的描述，而是進(jìn)行大致的概述，讓讀者了解到在Struts2中有哪些類型的集成，如何進(jìn)行集成，同時(shí)還提供了一些基本的配置信息，并說明怎樣獲取更多的配置信息。本章也并不旨在說明如何使用

89、那些用于集成的類庫(kù)，但是假定讀者已經(jīng)有了相關(guān)的基礎(chǔ)知識(shí)。</p><p>　　Struts2中所有集成（Apache和第三方庫(kù)）的最新信息都可以在Struts2 wiki上找到，地址為http://cwiki.apache.org/S2PLUGINS/home.html。新的項(xiàng)目正在不斷的添加進(jìn)來(lái)。如果你沒有從中找到想要的信息，那么可以檢查一下幾個(gè)月前的更新，也許它已經(jīng)被添加進(jìn)來(lái)了。如果你想要在自己的Web應(yīng)用中

90、添加新的集成，你可以考慮一下把它實(shí)現(xiàn)為一個(gè)插件，然后和其他人共享。</p><p><b>　　頁(yè)面修飾和布局 </b></p><p>　　開發(fā)Web應(yīng)用通常都意味著要有一個(gè)標(biāo)準(zhǔn)的頁(yè)面布局，并被應(yīng)用到整個(gè)應(yīng)用中，并且不同的模塊，頁(yè)面和向?qū)Э赡苓€要使用額外的一些布局。根據(jù)個(gè)人偏愛不同——自己指定布局或是讓URL指定布局——你很可能會(huì)選擇Struts Tiles11 或

91、是SiteMesh12。Struts2中提供了對(duì)這兩種布局技術(shù)的集成。</p><p><b>　　SiteMesh </b></p><p>　　SiteMesh可以通過兩種方式來(lái)安裝。一種是把插件13放到應(yīng)用程序下的“/WEB-INF/lib”目錄中，一種是在Maven2 “pom.xml”構(gòu)建文件中添加依賴關(guān)系： </p><p>　　&

92、lt;dependency> </p><p>　　<groupId>org.apache.struts</groupId> </p><p>　　<artifactId>struts2-sitemesh-plugin</artifactId> </p><p>　　<version>2.0.6<

93、;/version> </p><p>　　</dependency> </p><p>　　在安裝完以后，需要配置Servlet過濾器。這個(gè)過濾器允許SiteMesh 修飾器訪問值棧，并且確保在修飾器完成工作之后（而不是完成之前），會(huì)清空ActionContext。</p><p><b>　　<filter> </b

94、></p><p>　　<filter-name>struts-cleanup</filter-name> </p><p>　　<filter-class> </p><p>　　org.apache.struts2.dispatcher.ActionContextCleanU</p><p>　　

95、</filter-class> </p><p>　　</filter> </p><p>　　如果你使用了Freemarker或者Velocity來(lái)渲染頁(yè)面，那么就需要添加下面兩種過濾器之一： </p><p><b>　　<filter> </b></p><p>　　<fi

96、lter-name>sitemesh</filter-name> </p><p>　　<filter-class> </p><p>　　org.apache.struts2.sitemesh.FreeMarkerPageFilter </p><p>　　</filter-class> </p><p

97、>　　</filter> </p><p><b>　　<filter></b></p><p>　　filter-name>sitemesh</filter-name> </p><p>　　<filter-class> </p><p>　　org.apac

98、he.struts2.sitemesh.VelocityPageFilter </p><p>　　</filter-class> </p><p>　　</filter> </p><p>　　過濾器映射的順序也非常重要?！皊truts-cleanup”和“sitemesh”（如果已經(jīng)使用）過濾器都要在“struts”（FilterDisp

99、atcher）過濾器之前進(jìn)行配置： </p><p>　　<filter-mapping> </p><p>　　<filter-name>struts-cleanup</filter-name> </p><p>　　<url-pattern>/*</url-pattern> </p>&l

100、t;p>　　</filter-mapping> </p><p>　　<filter-mapping> </p><p>　　<filter-name>sitemesh</filter-name> </p><p>　　<url-pattern>/*</url-pattern> </

101、p><p>　　</filter-mapping> </p><p><b>　　… </b></p><p>　　<filter-mapping> </p><p>　　<filter-name>struts</filter-name> </p><p&g

102、t;　　<url-pattern>/*</url-pattern> </p><p>　　</filter-mapping> </p><p>　　完成這些以后，就可以對(duì)特定的修飾器文件進(jìn)行開發(fā)了，然后對(duì)其進(jìn)行配置，以匹配特定的URL模式，或者是“decorators.xml”中的元數(shù)據(jù)。</p><p><b>　　T

103、iles </b></p><p>　　Apache Tiles和SiteMesh一樣，都可以把插件14放到Web應(yīng)用的“/WEB-INF/lib”目錄下，或是在Mave2 “pom.xml”文件中加入依賴：</p><p>　　<dependency> </p><p>　　<groupId>org.apache.struts&

104、lt;/groupId> </p><p>　　<artifactId>struts2-tiles-plugin</artifactId> </p><p>　　<version>2.0.6</version> </p><p>　　</dependency> </p><p>

105、;　　我們需要配置Servlet Listener才能載入tiles配置信息： </p><p>　　<listener> </p><p>　　<listener-class></p><p>　　org.apache.struts2.tiles.StrutsTilesListener </p><p>　　<

106、/listener-class> </p><p>　　</listener></p><p>　　Listener會(huì)從“WEB-INF”目錄下載入“tiles.xml”配置文件，該文件中定義了應(yīng)用中的每一個(gè)tile。與SiteMesh不一樣的是，Tiles是作為一種新的結(jié)果類型實(shí)現(xiàn)的。要使用Tiles布局的Action結(jié)果都需要把“type”屬性設(shè)置為“tiles”（或

107、者是把Tiles結(jié)果設(shè)置為默認(rèn)值），并指定要使用的tile名稱。Tile名稱需要在“tiles.xml”文件中定義。</p><p>　　<action name="my" class="com.fdar.infoq.MyAction" > </p><p>　　<result type="tiles">m

108、yaction.layout</result> </p><p>　　</action> </p><p>　　Struts2中使用了Tiles的第二版。這個(gè)版本還沒有穩(wěn)定的發(fā)布版，還會(huì)有更多的變化。所以Struts2中對(duì)Tiles的支持被標(biāo)記為“試驗(yàn)性”。</p><p><b>　　業(yè)務(wù)服務(wù)/依賴注入</b><

109、/p><p>　　·EJB3，它雖然不是Ioc容器，但仍可以用來(lái)為Action提供業(yè)務(wù)服務(wù)?，F(xiàn)在Strut2中現(xiàn)在還沒有提供插件來(lái)提供對(duì)EJB3的支持，雖然實(shí)現(xiàn)起來(lái)并沒有什么難度。在Struts2中使用EJB3有三種方式——實(shí)現(xiàn)一個(gè)自定義的ObjectFactory，為Action獲取EJB引用，然后在“struts.properties”配置文件的“struts.properties”屬性中加以定義，把這

110、個(gè)新的工廠安裝到應(yīng)用程序中；創(chuàng)建一個(gè)新的攔截器，用來(lái)檢查每一個(gè)Action，并把所需的EJB應(yīng)用注入其中；或者還可以使用Spring插件來(lái)訪問JPA或是EJB， http://cwiki.apache.org/S2WIKI/struts-2-spring-jpa-ajax.html這個(gè)鏈接提供了相關(guān)的指南。</p><p>　　因?yàn)镾pring框架是推薦使用的庫(kù)，所以下面我們將重點(diǎn)介紹它的使用。</p>

111、;<p>　　Spring Framework</p><p>　　Spring Framework插件是Struts2推薦使用的依賴注入（DI）或控制反轉(zhuǎn)（IoC）容器，它可以為Action提供完全配置好的業(yè)務(wù)服務(wù)實(shí)例。</p><p>　　這里還有其他幾種選擇，每一種都具有不同層次上的穩(wěn)定性： </p><p>　　· Plexus15

112、插件是剛剛加入代碼庫(kù)的，目前還是被標(biāo)記為“試驗(yàn)性”。當(dāng)我們?cè)凇皊truts.xml”配置文件的每一項(xiàng)中使用Plexus id而不是類名時(shí)，Plexus可以創(chuàng)建類的實(shí)例，并向其中注入所有它所知的依賴。關(guān)于該插件的詳細(xì)信息可以在這里找到：http://cwiki.apache.org/S2PLUGINS/plexus-plugin.html </p><p>　　· PicoContainer16 是另外一