JBoss Portal SVN: r9992 - in demo/trunk: conf/core-cms and 2 other directories.
by portal-commits＠lists.jboss.org
Author: thomas.heute(a)jboss.com
Date: 2008-02-15 15:16:12 -0500 (Fri, 15 Feb 2008)
New Revision: 9992
Added:
demo/trunk/portlets/seamBooking/
demo/trunk/portlets/seamBooking/seamEAR.ear
Modified:
demo/trunk/build.properties
demo/trunk/build.xml
demo/trunk/conf/core-cms/jboss-service.xml
Log:
Modified: demo/trunk/build.properties
===================================================================
--- demo/trunk/build.properties 2008-02-15 19:27:11 UTC (rev 9991)
+++ demo/trunk/build.properties 2008-02-15 20:16:12 UTC (rev 9992)
@@ -1,7 +1,7 @@
# Location of the JBoss Portal + 4.0.5 AS bundle
-portal.bundle.url=/home/theute/Portal/workspace_2.6/demo/jboss-portal-2.6.3-bundled.zip
+portal.bundle.url=/home/theute/Downloads/jboss-portal-2.6.4-bundled.zip
# Name used as top directory in the bundle
-portal.name.dir=jboss-portal-2.6.3
+portal.name.dir=jboss-portal-2.6.4
# Where to create the demo website and associated tgz file
destination.dir=/home/theute/Portal/demoWebsite
# Where to put temporary files during the construction of the portal demo
Modified: demo/trunk/build.xml
===================================================================
--- demo/trunk/build.xml 2008-02-15 19:27:11 UTC (rev 9991)
+++ demo/trunk/build.xml 2008-02-15 20:16:12 UTC (rev 9992)
@@ -113,6 +113,11 @@
<delete file="${destination.dir}/${portal.name.dir}/server/default/deploy/wiki.ear/wiki.war/WEB-INF/wiki-object.xml"/>
</target>
+ <target name="install-seamBooking">
+ <copy file="portlets/seamBooking/seamEAR.ear" todir="${destination.dir}/${portal.name.dir}/server/default/deploy"/>
+ </target>
+
+
<target name="default-cms-content">
<delete dir="${destination.dir}/${portal.name.dir}/server/default/deploy/jboss-portal.sar/portal-cms.sar/portal/cms/conf/default-content/"/>
<mkdir dir="${destination.dir}/${portal.name.dir}/server/default/deploy/jboss-portal.sar/portal-cms.sar/portal/cms/conf/default-content"/>
@@ -137,8 +142,8 @@
<target name="main"
depends="unzip-bundle, delete-docs, configure-jboss, configure-identity, delete-objectsdescriptors, delete-wsrpdescriptors,
- update-context,install-objectsdescriptor, install-wsrpdescriptor, install-jbossforums, install-jbosswiki, activate-workflow, default-cms-content">
+ update-context,install-objectsdescriptor, install-wsrpdescriptor, install-jbossforums, install-seamBooking, install-jbosswiki, activate-workflow, default-cms-content">
<tar destfile="${destination.dir}/${portal.name.dir}.tgz" basedir="${destination.dir}" includes="${portal.name.dir}/**" longfile="gnu" compression="gzip"/>
</target>
-</project>
\ No newline at end of file
+</project>
Modified: demo/trunk/conf/core-cms/jboss-service.xml
===================================================================
--- demo/trunk/conf/core-cms/jboss-service.xml 2008-02-15 19:27:11 UTC (rev 9991)
+++ demo/trunk/conf/core-cms/jboss-service.xml 2008-02-15 20:16:12 UTC (rev 9992)
@@ -24,9 +24,11 @@
<server>
<!-- Management MBean -->
+ <!-- Unused, the bean doesn't bring any interesting value -->
+ <!--
<mbean
code="org.jboss.portal.cms.management.CMSImpl"
- name="portal:service=Management,type=CMS,name=Default"
+ name="portal.management:service=Management,type=CMS,name=Default"
xmbean-dd=""
xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
<depends
@@ -34,8 +36,9 @@
proxy-type="attribute">portal:service=CMS</depends>
<xmbean/>
</mbean>
-
- <mbean
+ -->
+
+ <mbean
code="org.jboss.portal.jems.hibernate.SessionFactoryBinder"
name="portal:service=Hibernate,type=CMS"
xmbean-dd=""
@@ -57,18 +60,18 @@
<depends>jboss.jca:service=DataSourceBinding,name=PortalDS</depends>
<depends>portal:service=JAASLoginModule</depends>
<depends>portal:service=Hibernate,type=CMS</depends>
- <depends optional-attribute-name="IdentityServiceController" proxy-type="attribute">portal:service=Module,type=IdentityServiceController</depends>
-
+ <depends>cms.pm.cache:service=TreeCache</depends>
+ <depends optional-attribute-name="AuthorizationManager" proxy-type="attribute">portal:service=AuthorizationManager,type=cms</depends>
+
<!-- Add this to activate publish/approval workflow integration -->
<depends optional-attribute-name="ApprovePublishWorkflow" proxy-type="attribute">portal:service=ApprovePublish,type=Workflow</depends>
-
+
<depends optional-attribute-name="StackFactory" proxy-type="attribute">portal:service=InterceptorStackFactory,type=Cms</depends>
<attribute name="DoChecking">true</attribute>
<attribute name="DefaultContentLocation">portal/cms/conf/default-content/default/</attribute>
<attribute name="DefaultLocale">en</attribute>
<attribute name="RepositoryName">PortalRepository</attribute>
<attribute name="HomeDir">${jboss.server.data.dir}${/}portal${/}cms${/}conf</attribute>
- <attribute name="IdentitySessionFactory">java:/portal/IdentitySessionFactory</attribute>
<attribute name="Config">
<Repository>
<!--
@@ -126,7 +129,7 @@
<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
<param name="path" value="${wsp.home}/index"/>
- <param name="textFilterClasses" value="org.apache.jackrabbit.core.query.HTMLTextFilter" />
+ <param name="textFilterClasses" value="org.apache.jackrabbit.core.query.HTMLTextFilter"/>
<param name="useCompoundFile" value="true"/>
<param name="minMergeDocs" value="100"/>
<param name="volatileIdleTime" value="3"/>
@@ -261,13 +264,10 @@
<!-- TreeCache configuration used to cache CMS data -->
<mbean code="org.jboss.cache.TreeCache"
- name="cms.pm.cache:service=TreeCache">
-
+ name="cms.pm.cache:service=TreeCache">
<depends>jboss:service=Naming</depends>
<depends>jboss:service=TransactionManager</depends>
<depends>portal:service=Hibernate,type=CMS</depends>
- <depends>portal:service=CMS</depends>
-
<!--
Configure the TransactionManager
-->
@@ -431,7 +431,7 @@
<attribute name="CacheLoaderFetchPersistentState">false</attribute>
<attribute name="CacheLoaderAsynchronous">false</attribute-->
</mbean>
-
+
<!-- interceptor factory where all cms interceptors are registered -->
<mbean
code="org.jboss.portal.server.impl.invocation.JBossInterceptorStackFactory"
@@ -443,8 +443,8 @@
<depends-list-element>portal:service=Interceptor,type=Cms,name=ACL</depends-list-element>
<depends-list-element>portal:service=Interceptor,type=Cms,name=ApprovalWorkflow</depends-list-element>
</depends-list>
- </mbean>
-
+ </mbean>
+
<!-- CMS Authorization Security Service -->
<mbean
code="org.jboss.portal.cms.security.AuthorizationManagerImpl"
@@ -463,9 +463,15 @@
xmbean-dd=""
xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
<xmbean/>
+ <!--
+ NOTE: cmsRootUserName denotes a single Portal user that has access to everything in the CMS. Denote this user
+ carefully and should be synonymous to the 'root' user in a Unix system. By default: this value is the built-in
+ 'admin' user account. This can be changed to any other user account registered in your Portal
+ -->
+ <attribute name="CmsRootUserName">admin</attribute>
<depends optional-attribute-name="IdentityServiceController" proxy-type="attribute">portal:service=Module,type=IdentityServiceController</depends>
</mbean>
-
+
<!-- ACL Security Interceptor -->
<mbean
code="org.jboss.portal.cms.impl.interceptors.ACLInterceptor"
@@ -518,7 +524,7 @@
<depends>portal:service=Hibernate,type=CMS</depends>
<depends>portal:service=Module,type=IdentityServiceController</depends>
</mbean>
-
+
<!-- Approval Workflow Interceptor -->
<mbean
code="org.jboss.portal.cms.impl.interceptors.ApprovalWorkflowInterceptor"
@@ -566,5 +572,100 @@
<depends
optional-attribute-name="CommandFactory"
proxy-type="attribute">portal:commandFactory=CMSObject</depends>
+ <depends
+ optional-attribute-name="PortalAuthorizationManagerFactory"
+ proxy-type="attribute">portal:service=PortalAuthorizationManagerFactory</depends>
+ <depends
+ optional-attribute-name="InstanceContainer"
+ proxy-type="attribute">portal:container=Instance</depends>
</mbean>
+
+ <!-- ApprovePublish workflow service -->
+ <mbean
+ code="org.jboss.portal.cms.workflow.ApprovePublishImpl"
+ name="portal:service=ApprovePublish,type=Workflow"
+ xmbean-dd=""
+ xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
+ <xmbean/>
+ <depends optional-attribute-name="WorkflowService" proxy-type="attribute">
+ portal:service=Workflow,type=WorkflowService
+ </depends>
+ <depends optional-attribute-name="IdentityServiceController" proxy-type="attribute">
+ portal:service=Module,type=IdentityServiceController
+ </depends>
+ <!-- JBPM process definition -->
+ <attribute name="Process">
+ <![CDATA[
+ <!-- cms approval workflow -->
+ <process-definition name="approval_workflow">
+ <start-state>
+ <transition to="request_approval"/>
+ </start-state>
+ <task-node name="request_approval" signal="first">
+ <task name="approve_publish">
+ <assignment class="org.jboss.portal.cms.workflow.PublishAssignmentHandler"/>
+ <event type="task-start">
+ <action class="org.jboss.portal.cms.workflow.FinalizePublish"/>
+ </event>
+ <exception-handler>
+ <action class="org.jboss.portal.cms.workflow.TaskExceptionHandler"/>
+ </exception-handler>
+ </task>
+ <transition name="approval" to="end"/>
+ <transition name="rejection" to="end"/>
+ </task-node>
+ <end-state name="end"/>
+ </process-definition>
+ ]]>
+ </attribute>
+ <!--
+ overwrite = false creates the process first time if does not exist, for
+ subsequent server restarts, this process definition remains in tact
+
+ overwrite = true creates the process first time if does not exist,
+ for subsequent server restarts, it creates a new version of the process definition
+ which will be used for processes created from then onwards. Old processes created
+ for an older version of the definition remain in tact and use their corresponding
+ process definition.
+
+ Typically use overwrite=false and overwrite=true only when a new process definition
+ related to this workflow needs to be deployed
+ -->
+ <attribute name="Overwrite">false</attribute>
+ <!--
+ a comma separated list of portal roles that are designated
+ to act as workflow managers. They are allowed to
+ approve/reject content publish requests
+ -->
+ <attribute name="ManagerRoles">Admin</attribute>
+ <attribute name="JNDIName">java:portal/ApprovePublishWorkflow</attribute>
+
+ <!-- Now that a manager GUI is integrated..no need for email based manager screen -->
+ <!--
+ <attribute name="From">do-not-reply(a)jboss.com</attribute>
+ <attribute name="Subject">Content Approval Requested</attribute>
+ <attribute name="Body">
+ <![CDATA[
+ Approval is needed to publish the following Content:
+
+ Content Location : {0}
+
+ Content Type : {1}
+
+ Content Size : {2}
+
+ Creation Date : {3}
+
+ User : {4}
+
+
+ <a href="http://localhost/workflow/approve?pId={5}&manager={6}">Approve</a>
+
+
+ <a href="http://localhost/workflow/reject?pId={7}&manager={8}">Reject</a>
+ ]]>
+ </attribute>
+ -->
+ </mbean>
+
</server>
Added: demo/trunk/portlets/seamBooking/seamEAR.ear
===================================================================
(Binary files differ)
Property changes on: demo/trunk/portlets/seamBooking/seamEAR.ear
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
16 years, 7 months
JBoss Portal SVN: r9990 - modules/portlet/tags.
by portal-commits＠lists.jboss.org
Author: julien(a)jboss.com
Date: 2008-02-15 06:57:43 -0500 (Fri, 15 Feb 2008)
New Revision: 9990
Added:
modules/portlet/tags/JBP_PORTLET_2_0_0_BETA1/
Log:
tagging portlet container 2.0.0 beta 1
Copied: modules/portlet/tags/JBP_PORTLET_2_0_0_BETA1 (from rev 9983, modules/portlet/trunk)
16 years, 7 months
JBoss Portal SVN: r9989 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-15 03:15:41 -0500 (Fri, 15 Feb 2008)
New Revision: 9989
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
revising 5.2.2. An example JSP Portlet
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 06:32:34 UTC (rev 9988)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 08:15:41 UTC (rev 9989)
@@ -534,7 +534,7 @@
</listitem>
<listitem>
<para>
- Run the <command>ant deploy</command> command. On Microsoft Windows, the output will be similar to the following:
+ Change into <filename>HelloWorldPortlet/</filename> directory, and run the <command>ant deploy</command> command. On Microsoft Windows, the output will be similar to the following:
</para>
<para>
<mediaobject>
@@ -543,12 +543,12 @@
</imageobject>
</mediaobject>
</para>
- <para>
- Note: the directory names will be different for your system.
- </para>
</listitem>
</orderedlist>
</para>
+ <para>
+ Note: the directory names will be different for your system.
+ </para>
<para>
Expanding the <filename>helloworldportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the XML descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldportlet.war</filename> file:
</para>
@@ -570,13 +570,13 @@
</imageobject>
</mediaobject>
</para>
- <para>
- Note: the directory names will be different for your system.
- </para>
</listitem>
</orderedlist>
</para>
<para>
+ Note: the directory names will be different for your system.
+ </para>
+ <para>
The <command>ant explode</command> command creates a directory structure such as the following:
</para>
<para>
@@ -587,7 +587,7 @@
</mediaobject>
</para>
<para>
- The expanded war file and the XML descriptors are located in the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/</filename> directory.
+ The expanded war file and the XML descriptors are located in the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/WEB-INF/</filename> directory.
</para>
</sect3>
<sect3>
@@ -882,12 +882,12 @@
</listitem>
<listitem>
<para>
- If required, edit the <filename>HelloWorldJSPPortlet/src/main/org/jboss/portlet/hello/HelloWorldJSPPortlet.java</filename> file, and the XML descriptors in the <filename>HelloWorldJSPPortlet/src/resources/helloworldjspportlet-war/WEB-INF</filename> directory.
+ If required, edit the <filename>HelloWorldJSPPortlet/src/main/org/jboss/portlet/hello/HelloWorldJSPPortlet.java</filename> file, and the XML descriptors in the <filename>HelloWorldJSPPortlet/src/resources/helloworldjspportlet-war/WEB-INF/</filename> directory.
</para>
</listitem>
<listitem>
<para>
- Run the <command>ant deploy</command> command. On Linux, the output will be similar to the following:
+ Change into <filename>HelloWorldJSPPortlet/</filename> directory, and run the <command>ant deploy</command> command. On Linux, the output will be similar to the following:
</para>
<para>
<mediaobject>
@@ -940,7 +940,7 @@
</mediaobject>
</para>
<para>
- The expanded war file and the XML descriptors are located in the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/</filename> directory.
+ The expanded war file and the XML descriptors are located in the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/WEB-INF/</filename> directory.
</para>
</sect3>
<sect3>
@@ -958,7 +958,7 @@
</screen>
</para>
<para>
- To see the HelloWorldJSPPortlet, navigate to http://localhost:8080/portal/, or, if the default JBoss Portal page is already open, refresh the page. The HelloWorldJSPPortlett is added to the bottom of the default JBoss Portal page:
+ To see the HelloWorldJSPPortlet, navigate to <ulink url="http://localhost:8080/portal/"></ulink>, or, if the default JBoss Portal page is already open, refresh the page. The HelloWorldJSPPortlet is added to the bottom of the default JBoss Portal page:
</para>
<para>
<mediaobject>
@@ -989,7 +989,7 @@
</sect3>
</sect2>
<sect2 id="sunri_42x">
- <title>A simple Sun's JSF Reference Implementation (RI) portlet on JBoss AS 4.2</title>
+ <title>A Sun JSF Reference Implementation (RI) portlet</title>
<sect3>
<title>Introduction</title>
<para>This section will introduce the reader to deploying a simple JSF portlet in JBoss Portal, using
16 years, 7 months
JBoss Portal SVN: r9988 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-15 01:32:34 -0500 (Fri, 15 Feb 2008)
New Revision: 9988
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
accidentally commented out 5.2.3. A simple Sun's JSF Reference Implementation (RI) portlet on JBoss AS 4.2
appears again
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 06:27:57 UTC (rev 9987)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 06:32:34 UTC (rev 9988)
@@ -986,50 +986,8 @@
warUrl=.../deploy/helloworldjspportlet.war/]]>
</screen>
</para>
-</sect3> <!--
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <para>If you have downloaded the sample, you can execute the build.xml with ant or inside your IDE.
- Executing the <literal>deploy</literal> target will compile all source files and produce a
- <literal>helloworldjspportlet.war</literal> file in a way similar to what we saw in
- <xref linkend="first_portlet_build"/>.
- </para>
- <para>
- The <literal>explode</literal> target will produce the following:
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/tutorials/jsp_ant_explode.png" valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- <para>
- Deploying the portlet is as easy as copying/moving the <literal>helloworldjspportlet.war</literal> file
- to the server <literal>deploy</literal> directory. We can then see our portlet on the Portal default
- page (<ulink url="http://localhost:8080/portal/">http://localhost:8080/portal/</ulink>):
- <mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/tutorials/jsp_portlet/output.png" valign="middle"/>
- </imageobject>
- </mediaobject>
- </para>
- </sect3>
- </sect2>
+</sect3>
+</sect2>
<sect2 id="sunri_42x">
<title>A simple Sun's JSF Reference Implementation (RI) portlet on JBoss AS 4.2</title>
<sect3>
@@ -1039,7 +997,7 @@
from PortletSwap.com, using this link:
<ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles/HelloWorl...">http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles/HelloWorl...</ulink>.
</para>
- </sect3> -->
+ </sect3>
<sect3>
<title>Package Content</title>
<para>
16 years, 7 months
JBoss Portal SVN: r9987 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/tutorials/jsp_portlet.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-15 01:27:57 -0500 (Fri, 15 Feb 2008)
New Revision: 9987
Added:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/tutorials/jsp_portlet/jsp_ant_deploy.png
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/tutorials/jsp_portlet/jsp_ant_explode.png
Log:
adding image files for
5.2.1.5. Building your Portlet
5.2.1.6. Deploying your Portlet
Added: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/tutorials/jsp_portlet/jsp_ant_deploy.png
===================================================================
(Binary files differ)
Property changes on: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/tutorials/jsp_portlet/jsp_ant_deploy.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/tutorials/jsp_portlet/jsp_ant_explode.png
===================================================================
(Binary files differ)
Property changes on: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/images/tutorials/jsp_portlet/jsp_ant_explode.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
16 years, 7 months
JBoss Portal SVN: r9986 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-15 00:51:47 -0500 (Fri, 15 Feb 2008)
New Revision: 9986
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
revising 5.2.2. An example JSP Portlet
adding: 5.2.2.5. Building your JSP Portlet, 5.2.2.6. Deploying your JSP Portlet
to be consistent with 5.2.1.5. Building your Portlet
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 04:44:18 UTC (rev 9985)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 05:51:47 UTC (rev 9986)
@@ -869,7 +869,7 @@
</para>
</sect3>
<sect3>
- <title>Building your Portlet</title>
+ <title>Building your JSP Portlet</title>
<para>
The <filename>HelloWorldJSPPortlet.zip</filename> file contains a pre-compiled <filename>helloworldjspportlet.war</filename> file; however, to manually build the <filename>helloworldjspportlet.war</filename> file:
</para>
@@ -940,8 +940,55 @@
</mediaobject>
</para>
<para>
- The expanded war file and the XML descriptors are located in the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/</filename> directory.
+ The expanded war file and the XML descriptors are located in the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/</filename> directory.
</para>
+ </sect3>
+ <sect3>
+ <title>Deploying your JSP Portlet</title>
+ <para>
+ If you did not expand the <filename>helloworldjspportlet.war</filename> file, copy the <filename>HelloWorldJSPPortlet/helloworldjspportlet.war</filename> file into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. If you expanded the <filename>helloworldjspportlet.war</filename> file, copy the <filename>HelloWorldJSPPortlet/output/lib/exploded/helloworldjspportlet.war/</filename> directory into the correct JBoss AS or JBoss EAP <filename>deploy/</filename> directory. For example, if you are using JBoss AS, copy the war file or the expanded directory into the <filename>$JBOSS_HOME/server/default/deploy/</filename> directory.
+ </para>
+ <para>
+ Performing this step on a running instance of JBoss AS or JBoss EAP, and JBoss Portal, will trigger a hot-deploy of the portlet:
+ </para>
+ <para>
+<screen><![CDATA[
+INFO [TomcatDeployer] deploy, ctxPath=/helloworldjspportlet,
+warUrl=.../deploy/helloworldjspportlet.war/]]>
+</screen>
+</para>
+<para>
+ To see the HelloWorldJSPPortlet, navigate to http://localhost:8080/portal/, or, if the default JBoss Portal page is already open, refresh the page. The HelloWorldJSPPortlett is added to the bottom of the default JBoss Portal page:
+</para>
+<para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/tutorials/jsp_portlet/output.png" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+</para>
+<para>
+ To re-deploy the portlet, for example, if you have made changes to any of the XML descriptors, touch the $JBOSS_HOME/server/configuration/deploy/helloworldjspportlet.war/WEB-INF/web.xml file. On Linux, run the following command to re-deploy the HelloWorldJSPPortlet:
+</para>
+<para>
+<screen>
+touch $JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy//helloworldjspportlet.war/WEB-INF/web.xml
+</screen>
+</para>
+<para>
+ Re-deploying the HelloWorldJSPPortlet will produce output to the JBoss AS or JBoss EAP console, similar to the following:
+</para>
+<para>
+<screen><![CDATA[
+INFO [TomcatDeployer] undeploy, ctxPath=/helloworldjspportlet,
+warUrl=.../deploy/helloworldjspportlet.war/
+INFO [TomcatDeployer] deploy, ctxPath=/helloworldjspportlet,
+warUrl=.../deploy/helloworldjspportlet.war/]]>
+</screen>
+</para>
+</sect3> <!--
+
+
@@ -992,7 +1039,7 @@
from PortletSwap.com, using this link:
<ulink url="http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles/HelloWorl...">http://anonsvn.jboss.org/repos/portletswap/portlets/2_6/bundles/HelloWorl...</ulink>.
</para>
- </sect3>
+ </sect3> -->
<sect3>
<title>Package Content</title>
<para>
16 years, 7 months
JBoss Portal SVN: r9985 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-14 23:44:18 -0500 (Thu, 14 Feb 2008)
New Revision: 9985
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
5.2.2.5. Building and deploying your portlet
revising with more content so that it is consistent with
5.2.1. Deploying your First Portlet
*** this will break the book***, but I wanted a backup :)
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 02:42:15 UTC (rev 9984)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 04:44:18 UTC (rev 9985)
@@ -137,7 +137,7 @@
</sect2>-->
<sect2>
- <title>Deploying your First Portlet</title>
+ <title>Deploying your first Portlet</title>
<sect3>
<title>Introduction</title>
<para>
@@ -518,7 +518,7 @@
<sect3 id="first_portlet_build">
<title>Building your Portlet</title>
<para>
- A pre-compiled <filename>HelloWorldPortlet/helloworldportlet.war</filename> file is created after extracting the <filename>HelloWorldPortlet.zip</filename> file. To manually build the <filename>helloworldportlet.war</filename> file:
+ The <filename>HelloWorldPortlet.zip</filename> file contains a pre-compiled <filename>helloworldportlet.war</filename> file; however, to manually build the <filename>helloworldportlet.war</filename> file:
</para>
<para>
<orderedlist>
@@ -534,7 +534,7 @@
</listitem>
<listitem>
<para>
- Run the <command>ant deploy</command> command:
+ Run the <command>ant deploy</command> command. On Microsoft Windows, the output will be similar to the following:
</para>
<para>
<mediaobject>
@@ -543,6 +543,9 @@
</imageobject>
</mediaobject>
</para>
+ <para>
+ Note: the directory names will be different for your system.
+ </para>
</listitem>
</orderedlist>
</para>
@@ -553,12 +556,12 @@
<orderedlist>
<listitem>
<para>
- If you do not have the <filename>HelloWorldPortlet/helloworldportlet.war</filename> file, change into the <filename>HelloWorldPortlet/</filename> directory, and run the <command>ant deploy</command> command. This creates a <filename>helloworldportlet.war</filename> file.
+ If you do not have the <filename>HelloWorldPortlet/helloworldportlet.war</filename> file, change into the <filename>HelloWorldPortlet/</filename> directory, and run the <command>ant deploy</command> command. This creates the <filename>helloworldportlet.war</filename> file.
</para>
</listitem>
<listitem>
<para>
- To expand the war file, change into the <filename>HelloWorldPortlet/</filename> directory, and run the <command>ant explode</command> command:
+ To expand the war file, change into the <filename>HelloWorldPortlet/</filename> directory, and run the <command>ant explode</command> command. On Microsoft Windows, the output will be similar to the following:
</para>
<para>
<mediaobject>
@@ -567,6 +570,9 @@
</imageobject>
</mediaobject>
</para>
+ <para>
+ Note: the directory names will be different for your system.
+ </para>
</listitem>
</orderedlist>
</para>
@@ -863,7 +869,95 @@
</para>
</sect3>
<sect3>
- <title>Building and deploying your portlet</title>
+ <title>Building your Portlet</title>
+ <para>
+ The <filename>HelloWorldJSPPortlet.zip</filename> file contains a pre-compiled <filename>helloworldjspportlet.war</filename> file; however, to manually build the <filename>helloworldjspportlet.war</filename> file:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Change into the <filename>HelloWorldJSPPortlet/</filename> directory, and remove the existing <filename>helloworldjspportlet.war</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If required, edit the <filename>HelloWorldJSPPortlet/src/main/org/jboss/portlet/hello/HelloWorldJSPPortlet.java</filename> file, and the XML descriptors in the <filename>HelloWorldJSPPortlet/src/resources/helloworldjspportlet-war/WEB-INF</filename> directory.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Run the <command>ant deploy</command> command. On Linux, the output will be similar to the following:
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/tutorials/jsp_portlet/jsp_ant_deploy.png" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ Note: the directory names will be different for your system.
+ </para>
+ <para>
+ Expanding the <filename>helloworldjspportlet.war</filename> file allows you to deploy the portlet as an expanded directory, which makes development easier. As well, it gives you access to the XML descriptors, resource files, JSF, and JSP pages. To expand the <filename>helloworldjspportlet.war</filename> file:
+ </para>
+ <para>
+ <orderedlist>
+ <listitem>
+ <para>
+ If you do not have the <filename>HelloWorldJSPPortlet/helloworldjspportlet.war</filename> file, change into the <filename>HelloWorldJSPPortlet/</filename> directory, and run the <command>ant deploy</command> command. This creates the <filename>helloworldjspportlet.war</filename> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ To expand the war file, change into the <filename>HelloWorldJSPPortlet/</filename> directory, and run the <command>ant explode</command> command. On Linux, the output will be similar to the following:
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/tutorials/jsp_portlet/jsp_ant_explode.png" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ Note: the directory names will be different for your system.
+ </para>
+ <para>
+ The <command>ant explode</command> command creates a directory structure such as the following:
+ </para>
+ <para>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/tutorials/jsp_portlet/exploded.gif" valign="middle"/>
+ </imageobject>
+ </mediaobject>
+ </para>
+ <para>
+ The expanded war file and the XML descriptors are located in the <filename>HelloWorldPortlet/output/lib/exploded/helloworldportlet.war/</filename> directory.
+ </para>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
<para>If you have downloaded the sample, you can execute the build.xml with ant or inside your IDE.
Executing the <literal>deploy</literal> target will compile all source files and produce a
<literal>helloworldjspportlet.war</literal> file in a way similar to what we saw in
@@ -873,7 +967,7 @@
The <literal>explode</literal> target will produce the following:
<mediaobject>
<imageobject>
- <imagedata align="center" fileref="images/tutorials/jsp_portlet/exploded.gif" valign="middle"/>
+ <imagedata align="center" fileref="images/tutorials/jsp_ant_explode.png" valign="middle"/>
</imageobject>
</mediaobject>
</para>
16 years, 7 months
JBoss Portal SVN: r9984 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.
by portal-commits＠lists.jboss.org
Author: mmcallis
Date: 2008-02-14 21:42:15 -0500 (Thu, 14 Feb 2008)
New Revision: 9984
Modified:
docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
Log:
5.2.2.4. JSP Files and the Portlet Tag Library
minor punctuation and tag revisions
Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml
===================================================================
--- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 01:59:07 UTC (rev 9983)
+++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/tutorials.xml 2008-02-15 02:42:15 UTC (rev 9984)
@@ -773,7 +773,7 @@
</screen></term>
<listitem>
<para>
- The <literal>doView</literal> implementation is responsible for dispatching to the appropriate JSP, <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view.jsp</filename>, or <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view2.jsp</filename>, depending on the existence of the <literal>yourname</literal> parameter passed in from <literal>processAction</literal>.
+ The <literal>doView</literal> implementation is responsible for dispatching to the appropriate JSP, <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view.jsp</filename> or <filename>HelloWorldJSPPortlet/WEB-INF/jsp/view2.jsp</filename>, depending on the existence of the <literal>yourname</literal> parameter passed in from <literal>processAction</literal>.
</para>
</listitem>
</varlistentry>
@@ -835,7 +835,7 @@
<listitem>
<para>
Calling <literal>defineObjects</literal> makes available implicit objects in the JSP, such as
- <literal>renderRequest, actionRequest, portletConfig</literal>.
+ <literal>renderRequest</literal>, <literal>actionRequest</literal>, and <literal>portletConfig</literal>.
</para>
</listitem>
</varlistentry>
@@ -845,7 +845,7 @@
</screen></term>
<listitem>
<para>
- A HTML form is created. This form posts to the URL defined by the portlet taglib. In this example, an <computeroutput>actionURL</computeroutput> is created, that activates the <literal>processAction</literal> method, which passes the input parameters in the form.
+ A HTML form is created. This form posts to the URL defined by the portlet taglib. In this example, an <computeroutput>actionURL</computeroutput> is created, that activates the <literal>processAction</literal> method, which passes the input parameters from the form.
</para>
</listitem>
</varlistentry>
16 years, 7 months
JBoss Portal SVN: r9983 - modules/portlet/trunk/docs/user-guide/en/images.
by portal-commits＠lists.jboss.org
Author: chris.laprun(a)jboss.com
Date: 2008-02-14 20:59:07 -0500 (Thu, 14 Feb 2008)
New Revision: 9983
Added:
modules/portlet/trunk/docs/user-guide/en/images/simple-portal.png
Log:
- Forgot to add image.
Added: modules/portlet/trunk/docs/user-guide/en/images/simple-portal.png
===================================================================
(Binary files differ)
Property changes on: modules/portlet/trunk/docs/user-guide/en/images/simple-portal.png
___________________________________________________________________
Name: svn:mime-type
+ image/png
16 years, 7 months