亚洲人成图片小说网站,亚洲自偷自拍另类图片二区,亚洲午夜精品久久久久久app

pluto1.1安装在TOMCAT

朱岩 — Wed, 28 Mar 2007 01:50:00 GMT

Installing the Pluto 1.1 Binary Build

About Pluto Distributions

There are a number of distributions to choose from depending on your needs.

pluto-current-bundle - Provides Pluto and Tomcat bundled together. If you are getting started with Pluto, this is the distribution you want.
pluto-current-bin - Provides the Pluto libraries, portal and testsuite web applications.
pluto-current-container-bin - Provides the Pluto container libraries only.
pluto-current-src - Provides the Pluto source code; requires that you build and deploy Pluto on your own.

Download the Pluto 1.1 binary distribution named pluto-current-bundle from a distribution site.
Unzip the binary distribution into a directory.
1. will be the top level directory.
Execute startup.bat (Windows) or startup.sh (Unix) in
/bin.
1. Use shutdown.bat/shutdown.sh to stop the portal
Browse to http://localhost:8080/pluto/portal
Login as the user pluto (password=pluto).

Building Pluto from Source

Maven 2 is utilized as the project management and build system for Pluto 1.1. Pluto currently provides Maven plugins which can be used to install the Pluto Portal, assemble portlet applications, deploy applications, and publish portlet applications to the Pluto Portal.

Obtaining Pluto 1.1 Source Code

The Pluto project uses the Subversion version control system. If you're new to Subversion, you can check out the online book about Subversion. Note that we are currently using Subversion 1.3.x (there are separate versions of the book covering the different versions of Subversion). Web Access to Subversion To browse the Pluto 1.1 source code, you can use the ViewCVS web interface to Subversion. This is current at all times. Normal Subversion Access Anyone can check code out of Subversion anonymously. However, you need to specify a username and password in order to update the Subversion repository, and only Pluto committers have the permissions to do that. We run Subversion over standard HTTPS, so hopefully you won't have problems with intervening firewalls.

Check out from Subversion

Again, anyone can do this. To check out the latest distribution of Pluto 1.1 (trunk) to a directory called 'pluto' use this command:

svn checkout https://svn.apache.org/repos/asf/portals/pluto/trunk/ pluto

To check out Pluto 1.1.1 source to the 'pluto' directory use this command:

svn checkout https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.1 pluto

Zipped up Pluto source distributions can also be downloaded from a distribution mirror.

Building Pluto with Maven 2

If this is your first time building Pluto with Maven 2, edit ~/.m2/settings.xml and add the element:


  ...
  
    org.apache.pluto
  
  ...

If you don't have org.apache.pluto specified as a , then the pluto:install will fail.

is the local directory where the Pluto 1.1 source distribution has been checked out or unzipped into.

$> cd 
$> mvn install
$> mvn pluto:install -DinstallDir=path/to/appserver

The install goal is a built in Maven 2 lifecycle which builds the project artifacts and installs them into the Maven repository.

The pluto:install goal will take the resulting artifacts and properly deploy them within the configured Tomcat installation. Currently, the Pluto 1.1 install has been tested on Tomcat 5.5.9, 5.5.17 and 5.5.20. The Tomcat 5 archive can be found here.

If installing to a directory that contains spaces, installDir needs to be enclosed within quotes:

C:\pluto> mvn pluto:install -DinstallDir="C:\Program Files\Apache Software Foundation\Tomcat 5.5"

Installing Pluto Manually

This section documents the manual installation of Pluto into Tomcat. It replaces the pluto:install goal, but requires that the built-in Maven 2 install goal (mvn install) be run from .

Step 1:

$> cd 
$> mvn install

Step 2: Copy the following to /shared/lib:

castor-1.0.jar
portlet-api-1.0.jar
pluto-container-1.1.1.jar
pluto-descriptor-api-1.1.1.jar
pluto-descriptor-impl-1.1.1.jar
pluto-taglib-1.1.1.jar

Step 3: Copy the following to /common/endorsed:

xercesImpl-2.6.2.jar
xmlParserAPIs-2.6.2.jar

Step 4: Copy the following to /conf/Catalina/localhost:

/pluto-portal/src/main/resources/pluto.xml
/pluto-testsuite/src/main/resources/testsuite.xml

Step 5: Copy the following to /webapps:

/pluto-portal/target/pluto-portal.war
/pluto-testsuite/target/pluto-testsuite.war

Installing Pluto with a Windows EXE

The NSIS Installer is not yet complete, but we hope to have a fully functional one soon. Anyone is more than welcome to assist us in this process.

Configuring Source-Built Pluto for Application Scope PortletSession Attributes

To be able to use application-scoped PortletSession attributes in Pluto, modify the Connector element for port 8080 in /conf/server.xml by adding the following attribute and value: emptySessionPath="true".

Configuring User and Role in the Pluto Source Build

The Pluto Testsuite portlet application needs the role 'pluto' to run the Security Mapping Test. So before starting tomcat, you should edit /conf/tomcat-users.xml, add the role 'pluto', and add a user in that role. The simplest way to do this is to edit add the 'pluto' role to the 'tomcat' user's record. Here is a sample tomcat-users.xml file:

Starting the Portal

Now you are ready to use the Pluto Portal built from source. Start up tomcat by running startup.bat (for windows) or startup.sh (for *nix) in /bin, and browse to http://localhost:8080/pluto/portal. Login to Pluto using the user and password you just created in tomcat-users.xml. If you added the 'pluto' role to the 'tomcat' user's record, you can login as 'tomcat/tomcat'.

朱岩 2007-03-28 09:50 发表评论

朱岩 — Tue, 27 Mar 2007 09:11:00 GMT

Pluto初始化流�E?a title="�怹�链接�Q�Pluto控制��程" >

关键�? Pluto Portal 门户

一、初始化��程

//Servlet初始�?br /> Pluto.PortalImpl.Servlet.init()

// ServiceManager初始�?br /> ServiceManager.init()

ConfigService.init() // 配置服务

LogService.init() // 日志服务

FactoryManagerService.init() // 工厂��理�?/font>

PortletDefinitionRegistryService.init() // Portlet定义注册�?/font>

PortletEntityRegistryService.init() // Portlet实体注册�?/font>

PageRegistryService.init() // Page注册�?/font>

//注，以上服务都读取同名的properties配置文�g.

// 初始化Portlet容器, 容器实现�c�d��ConfigService.properties中指�?br /> PortletContainerFactory.getPortletContainer().init()

二、请求处理流�E?

Pluto.PortalImpl.Servlet.doGet()

1. 创徏PortalEnvironment;

2. 查找ActionWindow;

    2a. 如找到ActionWindow, 则�ؓAction
            执行PortletContainer.processPortletAction();
            重定向输�?

2b. 找不到ActionWindow, 则�ؓRender, ��d��Page定义�?br /> RootFragment root = PageRegistry.getRootFragment();
root.service(servletRequest, servletResponse);

3. 处理完毕;

// 处理Fragment, RootFragment与Pageregistry.xml文�g兌��, 后者定义了��面的布局
Pluto.portalImpl.Aggregation.RootFragment.service()

// 服务前置处理�?br /> 1. preService(request, response);

    // 包含与当前fragment同名的jsp文�g�Q�当前�ؓRootFragment�?br />    2. RequestDispatcher rd = getServletConfig().getServletContext().
                                getRequestDispatcher(BASE_ROOT+jspName);
       rd.include(request, response);

// 服务后置处理
3. postService(request, response);

// Pageregistry.xml
〈portal〉�?// 对应RootFragment
〈fragment name="navigation"
class="org.apache.Pluto.portalImpl.aggregation.navigation.TabNavigation"�?br /> �?fragment�?/font>

〈fragment name="test" type="page"〉�?// 对应PageFragment
〈navigation�?br /> 〈title〉Test�?title�?br /> 〈description�?..�?description�?br /> �?navigation�?/font>

        〈fragment name="row" type="row"〉�?// 对应RowFragment
            〈fragment name="col1" type="column"〉 �?// 对应ColumnFragment
                〈fragment name="p1" type="portlet"〉 �?// 对应PortletFragment
                    〈property name="portlet" value="3.1"/�?br />                �?fragment�?br />                〈fragment name="p2" type="portlet"〉�?// 对应PortletFragment
                    〈property name="portlet" value="4.1"/�?br />                �?fragment�?br />            �?fragment�?br />        �?fragment�?br />    �?fragment�?br /> �?portal�?/font>

   // 上面的层�ơ结构十分清楚，其中fragment与Fragment的子�c�d��应，上面的定义中包括RootFragment,
        PageFragment, RowFragment, ColumnFragment和PortletFragment�Q�除了PortletFragment外，
        其它Fragment的处理大致上是一��L��Q?br />   Iterator childIterator = fragment.getChildFragments().iterator();

   // 遍历子fragment, �q�调用其服务�Ҏ��?br />   while (childIterator.hasNext()) {
       Fragment subfragment = (Fragment)childIterator.next();
       if (subfragment instanceof AbstractNavigationFragment)
       {
           subfragment.service(request, response);
           break;
       }
}

三、Portal处理��程

先来看看Portlet的初始化, 主要是从配置文�g中读取Portlet定义�?br /> PortletFragment.init()

// ��d��Portlet的实体Id, 在pageregistry.xml中由portlet属性指�?
String portletEntityId = getInitParameters().getString("portlet");

// ��d��Portlet实体. portlet实体在portletentityregistry.xml中定�?
PortletEntity portletEntity = PortletEntityRegistry.getPortletEntity(...);

      // portletentityregistry.xml
      〈portlet-entity-registry�?br />        〈application id="3"〉�?// 对应PortletApplicationEntity
           〈definition-id〉testsuite�?definition-id�?br />           〈portlet id="1"〉�?// 对应PortletEntity
              〈definition-id〉testsuite.TestPortlet1�?definition-id�?br />              〈preferences�?br />                  〈pref-name〉TestName4�?pref-name�?br />                  〈pref-value〉TestValue4�?pref-value�?br />                  〈read-only〉true�?read-only�?br />              �?preferences�?br />          �?portlet>
       �?application>
       〈application id="4"�?br />          〈definition-id>testsuite�?definition-id�?br />          〈portlet id="1"�?br />              〈definition-id>testsuite.TestPortlet2�?definition-id�?br />              〈preferences�?br />                  〈pref-name〉TestName4�?pref-name�?br />                  〈pref-value〉TestValue4�?pref-value�?br />                  〈read-only〉true�?read-only�?br />              �?preferences�?br />          �?portlet�?br />       �?application�?br />     �?portlet-entity-registry�?br />      //要注意这里的applicationid和portletid与pageregistry中的portletid的对应关�p�R�?/font>

// Portlet服务
PortletFragment.service()

//load protlet
PortletContainer.portletLoad(...)

// 1.取得PortletDefinition, 从portletentityregistry中定义的application中读取portlet定义.
PortletDefinition def = portletWindow.getPortletEntity().getPortletDefinition();

        // portlet.xml
        〈portlet-app〉 �?// 对应PortletApplicationDefinition
           〈portlet〉   �?// 对应PortletDefinition
              〈description〉TestSuiteDescription�?description�?br />              〈portlet-name〉TestPortlet1�?portlet-name�?br />              〈display-name〉Test Portlet #1�?display-name�?/font>

〈portlet-class〉org.apache.Pluto.portalImpl.portlet.TestPortlet�?portlet-class�?/font>

〈init-param>
〈name〉config�?name�?br /> 〈value�?WEB-INF/testsuite-config.xml�?value�?br /> �?init-param�?/font>

〈supports�?br /> 〈mime-type〉text/html�?mime-type�?br /> 〈portlet-mode〉VIEW�?portlet-mode�?br /> 〈portlet-mode〉EDIT�?portlet-mode�?br /> 〈portlet-mode〉HELP�?portlet-mode�?br /> �?supports�?/font>

〈portlet-info�?br /> 〈title〉Test Portlet #1�?title�?br /> 〈short-title〉Test #1�?short-title�?br /> 〈keywords〉Test,Testing�?keywords�?br /> �?portlet-info>

〈security-role-ref�?br /> 〈role-name〉PlutoTestRole�?role-name�?br /> 〈role-link〉tomcat�?role-link�?br /> �?security-role-ref�?br /> �?portlet�?br /> 〈portlet-app�?/font>

// 2.取得PortletInvoker
PortletInvoker invoker = PortletInvokerAccess.getPortletInvoker(def);

// 3.执行load操作
invoker.load(renderRequest, renderResponse)

// render Portlet
PortletContainer.renderPortlet(...);

// 1. 取得PortletInvoker
PortletInvoker invoker = PortletInvokerAccess.getPortletInvoker(...);

// 2. 执行render操作�?br /> invoker.render(renderRequest, renderResponse);

// 处理Title, support modes,

// Portlet调用.
ProtletInvoker.invoke(...)

      // 取得Portlet应用的dispatcher.
      ServletDefinition servletDefinition = portletDefinition.getServletDefinition();
      ServletContext servletContext = servletConfig.getServletContext();
      RequestDispatcher dispatcher = servletDefinition.getRequestDispatcher(servletContext);

      // 讄��属�? METHOD_ID为别对应load, render和action�?br />      servletRequest.setAttribute(Constants.METHOD_ID, methodID);
      servletRequest.setAttribute(Constants.PORTLET_REQUEST, portletRequest);
      servletRequest.setAttribute(Constants.PORTLET_RESPONSE, portletResponse);

// 调用Portlet
dispatcher.include(servletRequest, servletResponse);

四、Portlet处理��程

在Portlet应用的web.xml中，定义了PortletServlet为Portlet的Servlet�Q�它由dispatch�Ҏ��l�一�q�行��h��处理.

PortletServlet.dispatch(...)

// 讄��portletConfig.
request.setAttribute(org.apache.Pluto.Constants.PORTLET_CONFIG, portletConfig);

     Integer method_id = (Integer)request.getAttribute(Constants.METHOD_ID);
     if (method_id == Constants.METHOD_RENDER)
     {
         renderRequest = (RenderRequest)request.getAttribute(Constants.PORTLET_REQUEST);
         renderResponse = (RenderResponse)request.getAttribute(Constants.PORTLET_RESPONSE);

         // prepare container objects to run in this webModule
         prepareRenderRequest(renderRequest, request);
         prepareRenderResponse(renderResponse, request, response);

         portletClass.render(renderRequest,renderResponse);
     }
     else if (method_id==org.apache.Pluto.Constants.METHOD_ACTION)
     {
         actionRequest = (ActionRequest)request.getAttribute(Constants.PORTLET_REQUEST);
         actionResponse = (ActionResponse)request.getAttribute(Constants.PORTLET_RESPONSE);

         // prepare container objects to run in this webModule
         prepareActionRequest(actionRequest, request);
         prepareActionResponse(actionResponse, request, response);

         portletClass.processAction(actionRequest,actionResponse);
     }
     else if (method_id == org.apache.Pluto.Constants.METHOD_NOOP)
     {
         //nothing to do
     }
     //�? portletClass即�ؓportlet的具体实现类�?/font>

��x��Q�请求就由portlet�q�行处理了�?/font>

从上面的��程可以看出�Q�Pluto��是��请求分�z�ֈ��面上的各个portlet�Q�portlet�Ҏ��method执行相应操作�Q?/font>

最后由Pluto��它们处理的�l�果按特定布局�q�行昄��?/font>

朱岩 2007-03-27 17:11 发表评论

朱岩 — Fri, 23 Mar 2007 02:37:00 GMT

Pluto是一个满��Portlet API规范的Portlet容器的实玎ͼ�它�ؓ开发者提供了一个运�?portlets的工作��^台。然而，如果没有一个驱动器�Q�driver�Q�，也就是Portal�Q�的支持的话�Q?�q�行和测试Portlet容器��非�怹��ȝ��。Pluto本��n也提供了一个简单的Portal模块�Q�该模块�?仅是��Z��满��Portlet容器和JSR 168的需要而写的。如果你需要一个成熟的Portal�Q�请参�?Jetspeed��目。Jetspeed��目��x��的是Portal本��n�Q�而不是Portlet容器�?

�?是Portal的基本体�pȝ��构图。Portal Web Application处理客户的请求，从客��L��当前 ��中提取出portlets�Q�然后调用portlet容器来获得每一个portlet的内宏V��Portal通过 Portlet容器的Invoker API来访问portlet容器。这些API是portlet容器的主要调用接口，它们为Portal提供了一些基于请求的�Ҏ��来调用portlet。容器的使用者（即Portal�Q�译�?�?/i>�Q�必��d��现portlet容器的Container Provider SPI�Q�Service Provider Interface�Q�回调接口，来�ؓportlet容器提供与Portal相关的信息。最后，portlet容器�?�q�Portlet API调用所有的portlets�?

�?�Q�一个集成了Pluto的简单Portal

Portlet容器

Portlet容器是portlets的运行时环境�Q�也是每一个Portal的核心组件。Portlet容器需要获取有关Portal本��n的一些信息，�q�必��重用Portal的一些基本代码。因此，Portlet容器可以保证自己与其它的Portal�l��g之间是完全分开的。也��是��_��你可以把一个独立的Portlet容器插入��C�Q何一个Portal中去�Q�只要它可以满��Portlet容器的要求，比如实现了所有的SPI�?

Portlet容器的Invoker API�Q�也被称��入点�Q�是Portlet容器的主要调用接口。这些API�?含Portlet容器的生命周期控制方法（init()�Q�destroy()�Q�和��Z��h��的调用方�?�Q�initPage()�Q�performTitle()�Q�portletService()�{�等�Q�。由于Portlet容器最�l�是去调用一个portlet�Q�故�q�些�Ҏ��的签名和Portlet API的主要portlet接口很类��|��除了一�?��额外传入的portlet ID。Portlet容器可以通过�q�个额外传入的portlet ID参数来决定调�?哪一个portlet�?

除了可以使用Invoker API来调用Portlet容器外，Portal�q�必��d��现Portlet容器定义的SPI�?因此�Q�参考实现引入了“容器服务”的概念�Q�容器服务用来定义一些能够在容器中注册的可插的组�Ӟ�� q�些�l��g要么提供一些基本的功能�Q�要么对容器�q�行扩展。Pluto参考实现定义了下面�q�些内徏�?容器服务�Q�前四个是运行Portlet容器所必须实现的，而第五个则是可选的�Q�：

Information Provider�Q�信息提供者）�Q��ؓPortlet容器提供关于Portal�?其框架的信息。通过该接口只能够获得一些已知的或存在Portal中的信息。这些信息包括带 ��D��状态（navigational state�Q�的URL生成、portlet上下文（portlet context�Q��?portlet模式�Q�portlet mode�Q�和�H�口状态（window state�Q�控制�?

Factory Manager�Q�工厂管理者）�Q�定义了如何通过工厂获得一个实玎ͼ�一般的 Portal应该已经实现了这��L��接口�Q��?

Log Service�Q�日志服务）�Q�定义了输出日志的方法（一般的Portal应该已经�?��C��q�样的接口）�?

Config Service�Q�配�|�服务）�Q�定义了如何获得配置��|��一般的Portal应该�?�l�实��C��q�样的接口）�?

Property Manager�Q�属性管理者，可选）�Q�该服务让Portal可以获得JSR 168 规范中定义的属性的倹{�?

严格的说�Q�Portlet Object Model�Q�Portlet对象模型�Q�也是一个SPI�Q�但与其它的SPI相比�Q?它处在一个特�D�的位置上。因此我们不把它看成是容器服务的一部分�Q�因为它处理所有的portlet 对象�Q��ƈ包含了一些�؜杂的接口�?

�?�Q�Portlet容器的体�pȝ��?/b>

Pluto和WSRP标准

JSR 168规范和Web Service for Remote Portlets�Q�WSRP�Q�标准有高度的一致性。这�?个同时出现的标准都发布了开放源码的实现�Q�它们的实现都完成了在相应的规范中定义的所有必�?功能。这两个标准都把能很好的互相协作作�ؓ它们共同的目标。因此，WSRP portlets�?portlet容器中既可以作�ؓ消费者运行，也可以作为生产者运行�?

Pluto��目必须支持在一个Portal中运行多个portlet容器。因此，Pluto Portlet容器可以被多�ơ初始化。更重要的是�Q�它可以以不同的方式�q�行�Q�每个portlet容器都��用一个不同的SPI 实现�?

朱岩 2007-03-23 10:37 发表评论