April 2008 - portal-commits - Jboss List Archives

JBoss Portal SVN: r10477 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.

by portal-commits＠lists.jboss.org

Author: mmcallis Date: 2008-04-02 06:23:40 -0400 (Wed, 02 Apr 2008) New Revision: 10477 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml Log: 2.3.1. Getting the Sources fixing svn locations, and removing "F" character :( Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 07:16:53 UTC (rev 10476) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 10:23:40 UTC (rev 10477) @@ -202,21 +202,7 @@ <title>Getting the Sources</title> <para> The JBoss Portal source files can be obtained from the - <ulink url="http://labs.jboss.com/portal/jbossportal/download/index.html">JBoss Portal Downloads</ulink> page. The source files download uses a <filename>JBoss Portal Source Code</filename> naming convention. As well, the sources can be obtained from SVN: - </para> - <para>F - <itemizedlist> - <listitem> - <para> - the latest source files of the 2.6 branch: <emphasis>http://anonsvn.jboss.org/repos/portal/branches/JBoss_Portal_Branch_2_6</emphasis> - </para> - </listitem> - <listitem> - <para> - the latest sources: <emphasis>http://anonsvn.jboss.org/repos/portal/trunk/</emphasis> - </para> - </listitem> - </itemizedlist> + <ulink url="http://labs.jboss.com/portal/jbossportal/download/index.html">JBoss Portal Downloads</ulink> page. The source files download uses a <filename>JBoss Portal Source Code</filename> naming convention. As well, the sources can be obtained from SVN. The latest sources for the 2.6.<replaceable>x</replaceable> versions are located at <ulink url="http://anonsvn.jboss.org/repos/portal/branches/JBoss_Portal_Branch_2_6" />. </para> <para> Several modules have been extracted from the JBoss Portal SVN repository. These modules have a different lifecycle and a different version scheme. The following is a list of modules used in JBoss Portal 2.6.4, and the locations of their source code:

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10476 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.

by portal-commits＠lists.jboss.org

Author: mmcallis Date: 2008-04-02 03:16:53 -0400 (Wed, 02 Apr 2008) New Revision: 10476 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml Log: 6.3.2. Portlet Debugging (jboss-portal.sar/conf/config.xml) revising content Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 06:57:47 UTC (rev 10475) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 07:16:53 UTC (rev 10476) @@ -1647,13 +1647,12 @@ </sect3> </sect2> <sect2 id="descriptor_debug"> - <title>Portlet Debugging (jboss-portal.sar/conf/config.xml)</title> + <title>Portlet Debugging (<filename>jboss-portal.sar/conf/config.xml</filename>)</title> <para> - By default, JBoss Portal ships with all errors set to display. You can fine-tune this behavior by modifying - some properties in the file, - <emphasis>jboss-portal.sar/conf/config.xml</emphasis> - : - <programlisting><![CDATA[ + By default, JBoss Portal is configured to display all errors; however, this behavior can be fine-tuned by modifying the <filename>jboss-portal.sar/conf/config.xml</filename> file: + </para> + <para> +<screen><![CDATA[  <entry key="core.render.window_access_denied">show</entry>  @@ -1663,22 +1662,12 @@  <entry key="core.render.window_internal_error">show</entry>  -<entry key="core.render.window_not_found">show</entry> -]]></programlisting> - Either - <emphasis>show</emphasis> - or - <emphasis>hide</emphasis> - are allowed as flags in these elements. Depending on the setting and actual error, either an error message - is deployed or a full stack trace within the portlet window. - Additionally, the - <emphasis>core.render.window_error</emphasis> - property supports the - <emphasis>message_only</emphasis> - value. This value will only display the error message whereas - <emphasis>show</emphasis> - will display the full stack trace if it is available. - </para> +<entry key="core.render.window_not_found">show</entry>]]> +</screen> + </para> + <para> + For these parameters, accepted values are <computeroutput>show</computeroutput> and <computeroutput>hide</computeroutput>. Depending on the setting, and the actual error, either an error message is displayed, or a full stack trace within the portlet window occurs. Additionally, the <computeroutput>core.render.window_error</computeroutput> property only supports the <computeroutput>message_only</computeroutput> value. The <computeroutput>message_only</computeroutput> value will only display an error message, whereas the <computeroutput>show</computeroutput> value will, if available, display the full stack trace. + </para> </sect2> <sect2> <title>Login to dashboard</title>

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10475 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.

by portal-commits＠lists.jboss.org

Author: mmcallis Date: 2008-04-02 02:57:47 -0400 (Wed, 02 Apr 2008) New Revision: 10475 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml Log: 6.3.1. Datasource Descriptors (portal-*-ds.xml) final revisions for this section... Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 06:49:13 UTC (rev 10474) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 06:57:47 UTC (rev 10475) @@ -204,7 +204,7 @@ The JBoss Portal source files can be obtained from the <ulink url="http://labs.jboss.com/portal/jbossportal/download/index.html">JBoss Portal Downloads</ulink> page. The source files download uses a <filename>JBoss Portal Source Code</filename> naming convention. As well, the sources can be obtained from SVN: </para> - <para> + <para>F <itemizedlist> <listitem> <para> @@ -334,7 +334,8 @@ </para> <para> <screen> -JAVA_OPTS=-Dhttp.proxyHost=<<replaceable>proxy-hostname</replaceable>> -Dhttp.proxyPort=<<replaceable>proxy-port</replaceable>> +JAVA_OPTS=-Dhttp.proxyHost=<<replaceable>proxy-hostname</replaceable>> +-Dhttp.proxyPort=<<replaceable>proxy-port</replaceable>> </screen> </para> <para> @@ -342,7 +343,8 @@ </para> <para> <screen> -set JAVA_OPTS=-Dhttp.proxyHost=<<replaceable>proxy-hostname</replaceable>> -Dhttp.proxyPort=<<replaceable>proxy-port</replaceable>> +set JAVA_OPTS=-Dhttp.proxyHost=<<replaceable>proxy-hostname</replaceable>> +-Dhttp.proxyPort=<<replaceable>proxy-port</replaceable>> </screen> </para> <para> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 06:49:13 UTC (rev 10474) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 06:57:47 UTC (rev 10475) @@ -1577,12 +1577,12 @@ <orderedlist> <listitem> <para> - Obtain the JBoss Portal source code: <xref linkend="install_source" /> + Obtain the JBoss Portal source code: <xref linkend="install_source" />. </para> </listitem> <listitem> <para> - Configure the <computeroutput>$JBOSS_HOME</computeroutput> environment variable: <xref linkend="install_source_env"/> + Configure the <computeroutput>JBOSS_HOME</computeroutput> environment variable: <xref linkend="install_source_env"/>. </para> </listitem> <listitem> @@ -1592,7 +1592,7 @@ </listitem> <listitem> <para> - Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/</filename> directory, and run the <command>sh build.sh datasource</command> command: + Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/</filename> directory, and run the <command>sh build.sh datasource</command> command, or, if you are running Microsoft Windows, run the <command>build.bat datasource</command> command: </para> <para> <mediaobject> @@ -1605,7 +1605,7 @@ </orderedlist> </para> <para> - Note: if the JBoss Portal source was not built as per step 3, the <command>sh build.sh datasource</command> command fails with an error such as the following: + Note: if the JBoss Portal source was not built as per step 3, the <command>sh build.sh datasource</command> and <command>build.bat datasource</command> commands fail with an error, such as the following: </para> <para> <screen><![CDATA[ @@ -1615,7 +1615,7 @@ </screen> </para> <para> - The datasource build process produces the following directory and file structure, with the Datasource descriptors being located in the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/output/resources/setup</filename> directory: + The datasource build process produces the following directory and file structure, with the Datasource descriptors in the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/output/resources/setup</filename> directory: </para> <para> <mediaobject>

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10474 - in modules/presentation/trunk: build and 7 other directories.

by portal-commits＠lists.jboss.org

Author: sohil.shah(a)jboss.com Date: 2008-04-02 02:49:13 -0400 (Wed, 02 Apr 2008) New Revision: 10474 Added: modules/presentation/trunk/presentation/src/main/config/sar/ modules/presentation/trunk/presentation/src/main/config/sar/META-INF/ modules/presentation/trunk/presentation/src/main/config/sar/META-INF/jboss-service.xml modules/presentation/trunk/presentation/src/main/config/war/ modules/presentation/trunk/presentation/src/main/config/war/WEB-INF/ modules/presentation/trunk/presentation/src/main/config/war/WEB-INF/web.xml Modified: modules/presentation/trunk/.classpath modules/presentation/trunk/build/pom.xml modules/presentation/trunk/pom.xml modules/presentation/trunk/presentation/build.xml modules/presentation/trunk/presentation/pom.xml modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/impl/ajax/entry/PortalEntryPoint.java Log: fix for deployable presentation.sar Modified: modules/presentation/trunk/.classpath =================================================================== --- modules/presentation/trunk/.classpath 2008-04-02 05:15:47 UTC (rev 10473) +++ modules/presentation/trunk/.classpath 2008-04-02 06:49:13 UTC (rev 10474) @@ -14,9 +14,9 @@ <classpathentry kind="var" path="M2_REPO/org/codehaus/cargo/cargo-core-uberjar/0.8/cargo-core-uberjar-0.8.jar"/> <classpathentry kind="var" path="M2_REPO/apache-tomcat/catalina/5.5.12/catalina-5.5.12.jar"/> <classpathentry kind="var" path="M2_REPO/javax/ccpp/ccpp/1.0/ccpp-1.0.jar"/> - <classpathentry kind="var" path="M2_REPO/org/jboss/portal/common/common-common/1.2.0.Beta2/common-common-1.2.0.Beta2.jar"/> - <classpathentry kind="var" path="M2_REPO/org/jboss/portal/common/common-mc/1.2.0.Beta2/common-mc-1.2.0.Beta2.jar"/> - <classpathentry kind="var" path="M2_REPO/org/jboss/portal/common/common-portal/1.2.0.Beta2/common-portal-1.2.0.Beta2.jar"/> + <classpathentry kind="var" path="M2_REPO/org/jboss/portal/common/common-common/1.2.0.Beta3/common-common-1.2.0.Beta3.jar"/> + <classpathentry kind="var" path="M2_REPO/org/jboss/portal/common/common-mc/1.2.0.Beta3/common-mc-1.2.0.Beta3.jar"/> + <classpathentry kind="var" path="M2_REPO/org/jboss/portal/common/common-portal/1.2.0.Beta3/common-portal-1.2.0.Beta3.jar"/> <classpathentry kind="var" path="M2_REPO/commons-codec/commons-codec/1.2/commons-codec-1.2.jar"/> <classpathentry kind="var" path="M2_REPO/apache-httpclient/commons-httpclient/2.0.2/commons-httpclient-2.0.2.jar"/> <classpathentry kind="var" path="M2_REPO/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar"/> Modified: modules/presentation/trunk/build/pom.xml =================================================================== --- modules/presentation/trunk/build/pom.xml 2008-04-02 05:15:47 UTC (rev 10473) +++ modules/presentation/trunk/build/pom.xml 2008-04-02 06:49:13 UTC (rev 10474) @@ -44,7 +44,11 @@ <version.jboss.microcontainer>2.0.0.Beta9</version.jboss.microcontainer> <version.jboss.common.core>2.0.3.GA</version.jboss.common.core> - <version.jboss.remoting>2.2.1.GA</version.jboss.remoting> + <version.jboss.remoting>2.2.1.GA</version.jboss.remoting> + +  + <jboss.home>/home/soshah/appServers/jboss-4.2.1.GA</jboss.home> + <portal.deploy.dir>presentation</portal.deploy.dir> </properties> <repositories> Modified: modules/presentation/trunk/pom.xml =================================================================== --- modules/presentation/trunk/pom.xml 2008-04-02 05:15:47 UTC (rev 10473) +++ modules/presentation/trunk/pom.xml 2008-04-02 06:49:13 UTC (rev 10474) @@ -28,24 +28,5 @@ <modules> <module>build</module> <module>presentation</module> - </modules> - - <build> - <plugins> - <plugin> - <groupId>org.jvnet.maven-antrun-extended-plugin</groupId> - <artifactId>maven-antrun-extended-plugin</artifactId> - <version>1.13</version> - <executions> - <execution> - <id>install</id> - <phase>install</phase> - <goals> - <goal>run</goal> - </goals> - </execution> - </executions> - </plugin> - </plugins> - </build> + </modules> </project> Modified: modules/presentation/trunk/presentation/build.xml =================================================================== --- modules/presentation/trunk/presentation/build.xml 2008-04-02 05:15:47 UTC (rev 10473) +++ modules/presentation/trunk/presentation/build.xml 2008-04-02 06:49:13 UTC (rev 10474) @@ -41,10 +41,9 @@   <target name="package" - description="Generate all target output."> - <echo>Packaging Presentation..........</echo> - + description="Generate all target output.">  +  <delete dir="${basedir}/target/ajax-useragent"/> <java classpath="${plugin_classpath}" fork="true" classname="com.google.gwt.dev.GWTCompiler"> <classpath> @@ -55,14 +54,29 @@ <arg line="org.jboss.portal.presentation.ajax.Portal"/> </java> -  + + <jar jarfile="${basedir}/target/presentation-mockportal-plugin.jar"> + <fileset dir="${basedir}/target/test-classes"> + <include name="org/jboss/portal/presentation/test/portal/**/*.class"/> + </fileset> + </jar> + + <jar jarfile="${basedir}/target/presentation.sar"> + <fileset dir="${basedir}/src/main/config/sar"/> + <fileset file="${basedir}/target/presentation.war"/> + <fileset file="${dependency.gwt-user.jar}"/> + <fileset file="${dependency.presentation.jar}"/> + <fileset file="${basedir}/target/presentation-mockportal-plugin.jar"/> + </jar> </target> - + + <target name="install" description="Generate all target output and deploy it to a locally setup app server" depends="package"> + <copy file="${basedir}/target/presentation.sar" todir="${jboss.home}/server/${portal.deploy.dir}/deploy" overwrite="true"/> + </target>    Modified: modules/presentation/trunk/presentation/pom.xml =================================================================== --- modules/presentation/trunk/presentation/pom.xml 2008-04-02 05:15:47 UTC (rev 10473) +++ modules/presentation/trunk/presentation/pom.xml 2008-04-02 06:49:13 UTC (rev 10474) @@ -6,6 +6,7 @@ <version>1.0.0-SNAPSHOT</version> <relativePath>../build/pom.xml</relativePath> </parent> + <modelVersion>4.0.0</modelVersion> <artifactId>presentation-presentation</artifactId> <packaging>jar</packaging> @@ -142,8 +143,8 @@ </dependencies> <executions> <execution> - <id>package</id> - <phase>package</phase> + <id>install</id> + <phase>install</phase> <configuration> <tasks> <property name="compile_classpath" refid="maven.compile.classpath"/> @@ -151,8 +152,14 @@ <property name="test_classpath" refid="maven.test.classpath"/> <property name="plugin_classpath" refid="maven.plugin.classpath"/> <property name="project.version" value="${project.version}"/> + <property name="jboss.home" value="${jboss.home}"/> + <property name="portal.deploy.dir" value="${portal.deploy.dir}"/> + + <property name="dependency.gwt-user.jar" value="${maven.dependency.com.google.gwt.gwt-user.jar.path}"/> + <property name="dependency.presentation.jar" value="${basedir}/target/presentation-presentation-${project.version}.jar"/> + <ant antfile="${basedir}/build.xml"> - <target name="package"/> + <target name="install"/> </ant> </tasks> </configuration> Added: modules/presentation/trunk/presentation/src/main/config/sar/META-INF/jboss-service.xml =================================================================== --- modules/presentation/trunk/presentation/src/main/config/sar/META-INF/jboss-service.xml (rev 0) +++ modules/presentation/trunk/presentation/src/main/config/sar/META-INF/jboss-service.xml 2008-04-02 06:49:13 UTC (rev 10474) @@ -0,0 +1,122 @@ +<?xml version="1.0" encoding="UTF-8"?> + + +<server> +  + <mbean + code="org.jboss.portal.presentation.client.controller.UIController" + name="portal:service=Controller,type=Presentation" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends optional-attribute-name="PresentationServer" proxy-type="attribute">portal:service=PresentationServer</depends> + </mbean> + <mbean + code="org.jboss.portal.presentation.client.controller.AjaxUIController" + name="portal:service=Controller,type=Ajax/Presentation" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends optional-attribute-name="PresentationServer" proxy-type="attribute">portal:service=PresentationServer</depends> + </mbean> + +  +  + +  + <mbean + code="org.jboss.portal.presentation.test.portal.plugin.PresentationServerImpl" + name="portal:service=PresentationServer" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends optional-attribute-name="Processor" proxy-type="attribute">portal:service=Processor</depends> + </mbean> + <mbean + code="org.jboss.portal.presentation.test.portal.plugin.MainProcessor" + name="portal:service=Processor" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + </mbean> +</server> Added: modules/presentation/trunk/presentation/src/main/config/war/WEB-INF/web.xml =================================================================== --- modules/presentation/trunk/presentation/src/main/config/war/WEB-INF/web.xml (rev 0) +++ modules/presentation/trunk/presentation/src/main/config/war/WEB-INF/web.xml 2008-04-02 06:49:13 UTC (rev 10474) @@ -0,0 +1,63 @@ +<?xml version="1.0"?> + + +<!DOCTYPE web-app PUBLIC + "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" + "http://java.sun.com/dtd/web-app_2_3.dtd"> +<web-app> +  + <filter> + <filter-name>GWTClientFilter</filter-name> + <filter-class>org.jboss.portal.presentation.impl.ajax.entry.GWTClientFilter</filter-class> + </filter> + <filter-mapping> + <filter-name>GWTClientFilter</filter-name> + <servlet-name>PortalServletWithPathMapping</servlet-name> + </filter-mapping> + <filter-mapping> + <filter-name>GWTClientFilter</filter-name> + <servlet-name>PortalServletWithDefaultServletMapping</servlet-name> + </filter-mapping> + +  + <servlet> + <servlet-name>AjaxPortalEntryPoint</servlet-name> + <servlet-class>org.jboss.portal.presentation.impl.ajax.entry.PortalEntryPoint</servlet-class> + <init-param> + <param-name>interceptorStackFactoryName</param-name> + <param-value>portal:service=InterceptorStackFactory,type=Server</param-value> + <description>The request controller factory for the portal servlet</description> + </init-param> + <init-param> + <param-name>clientController</param-name> + <param-value>portal:service=Controller,type=Ajax/Presentation</param-value> + <description>The Client Controller</description> + </init-param> + <load-on-startup>0</load-on-startup> + </servlet> + <servlet-mapping> + <servlet-name>AjaxPortalEntryPoint</servlet-name> + <url-pattern>/portalrpc/*</url-pattern> + </servlet-mapping> +</web-app> Modified: modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/impl/ajax/entry/PortalEntryPoint.java =================================================================== --- modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/impl/ajax/entry/PortalEntryPoint.java 2008-04-02 05:15:47 UTC (rev 10473) +++ modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/impl/ajax/entry/PortalEntryPoint.java 2008-04-02 06:49:13 UTC (rev 10474) @@ -29,6 +29,8 @@ import org.jboss.portal.presentation.protocol.GetActivation; import org.jboss.portal.presentation.protocol.PostActivation; import org.jboss.portal.presentation.invocation.PresentationInvocation; +import org.jboss.portal.presentation.invocation.ClientController; +import org.jboss.portal.presentation.invocation.PresentationInvocationHandler; import com.google.gwt.user.client.rpc.SerializationException; import com.google.gwt.user.server.rpc.RemoteServiceServlet; @@ -49,6 +51,11 @@ /** The interceptor stack. */ private InterceptorStackFactory interceptorStack = null; + /** + * + */ + private ClientController clientController = null; + /** Configure the as default servlet. */ public void init() throws ServletException @@ -60,11 +67,17 @@ //Locate the interceptor stack factory this.interceptorStack = (InterceptorStackFactory) MBeanProxy.get(InterceptorStackFactory.class, new ObjectName( this.getInitParameter("interceptorStackFactoryName")), - mbeanServer); + mbeanServer); + + //Client Controller + this.clientController = (ClientController) MBeanProxy.get(ClientController.class, new ObjectName( + this.getInitParameter("clientController")), + mbeanServer); } catch (Exception e) { - this.interceptorStack = null; + this.interceptorStack = null; + this.clientController = null; String msg = "Ajax Portal Entry point could not be created"; log.error(msg, e); throw new UnavailableException(msg); @@ -279,8 +292,10 @@ WebResponse webResp = new WebResponse(resp); PresentationInvocation invocation = new PresentationInvocation(webReq, webResp); - //TODO: set the proper invocation handler here + //Set the proper invocation handler here + invocation.setHandler(new PresentationInvocationHandler(this.clientController)); - invocation.invoke(this.interceptorStack.getInterceptorStack()); + //invocation.invoke(this.interceptorStack.getInterceptorStack()); + invocation.invokeNext(); } }

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10473 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.

by portal-commits＠lists.jboss.org

Author: mmcallis Date: 2008-04-02 01:15:47 -0400 (Wed, 02 Apr 2008) New Revision: 10473 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml Log: 6.3.1. Datasource Descriptors (portal-*-ds.xml) minor corrections Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 05:03:17 UTC (rev 10472) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 05:15:47 UTC (rev 10473) @@ -128,7 +128,7 @@ Copy the Datasource descriptor that matches your database into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory, where <replaceable>configuration</replaceable> is either all, default, minimal or production. The production configuration only exists on JBoss EAP, and not JBoss AS. For example, if you are using the all configuration, copy the Datasource descriptor into the <filename>$JBOSS_HOME/server/all/deploy/</filename> directory. </para> <para> - After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the <computeroutput>user-name</computeroutput>, <computeroutput>password</computeroutput>, <computeroutput>connection-url</computeroutput>, and <computeroutput>driver-class</computeroutput>, are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for the PostgreSQL database: + After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the <computeroutput>user-name</computeroutput>, <computeroutput>password</computeroutput>, <computeroutput>connection-url</computeroutput>, and <computeroutput>driver-class</computeroutput>, are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for a PostgreSQL database: </para> <programlisting><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> @@ -444,7 +444,7 @@ Copy the Datasource descriptor that matches your database into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory, where <replaceable>configuration</replaceable> is either all, default, minimal, or production. For example, if you are using the production configuration, copy the Datasource descriptor into the <filename>$JBOSS_HOME/server/production/deploy/</filename> directory. The production configuration only exists on JBoss EAP installations, and not JBoss AS. </para> <para> - After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the <computeroutput>user-name</computeroutput>, <computeroutput>password</computeroutput>, <computeroutput>connection-url</computeroutput>, and <computeroutput>driver-class</computeroutput>, are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for the PostgreSQL database: + After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the <computeroutput>user-name</computeroutput>, <computeroutput>password</computeroutput>, <computeroutput>connection-url</computeroutput>, and <computeroutput>driver-class</computeroutput>, are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for a PostgreSQL database: </para> <programlisting><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 05:03:17 UTC (rev 10472) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 05:15:47 UTC (rev 10473) @@ -1615,7 +1615,7 @@ </screen> </para> <para> - Once complete, the datasource build process produces the following directory and file structure, with the Datasource descriptors being located in the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/output/resources/setup</filename> directory: + The datasource build process produces the following directory and file structure, with the Datasource descriptors being located in the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/output/resources/setup</filename> directory: </para> <para> <mediaobject> @@ -1625,7 +1625,7 @@ </mediaobject> </para> <para> - The following is an example Datasource descriptor for the PostgreSQL database: + The following is an example Datasource descriptor for a PostgreSQL database: </para> <para> <screen><![CDATA[

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10472 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.

by portal-commits＠lists.jboss.org

Author: mmcallis Date: 2008-04-02 01:03:17 -0400 (Wed, 02 Apr 2008) New Revision: 10472 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml Log: 6.3.1.2. Building Datasource Descriptors from Source -periodic backup, and minor revisions Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 04:43:57 UTC (rev 10471) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 05:03:17 UTC (rev 10472) @@ -1587,7 +1587,7 @@ </listitem> <listitem> <para> - Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> directory. To build the JBoss Portal source code on Linux, run the <command>./build.sh deploy</command> command, or, if you are running Microsoft Windows, run the <command>build.bat deploy</command> command. If this is the first build, third-party libaries are obtained from an online repository, so you must be connected to the Internet. After building the JBoss Portal source, the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/thirdparty/</filename> directory is created if it does not already exist, and will contain the files required in later steps. For further details, refer to <xref linkend="building_deploying_from_source" />. + Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> directory. To build the JBoss Portal source code on Linux, run the <command>./build.sh deploy</command> command, or, if you are running Microsoft Windows, run the <command>build.bat deploy</command> command. If this is the first build, third-party libraries are obtained from an online repository, so you must be connected to the Internet. After building, if the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/thirdparty/</filename> directory does not exist, it is created, and populated with the files required for later steps. For further details, refer to <xref linkend="building_deploying_from_source" />. </para> </listitem> <listitem> @@ -1605,7 +1605,7 @@ </orderedlist> </para> <para> - Note: the <command>sh build.sh datasource</command> command will fail with an error such as the following if the JBoss Portal source was not built prior to running the command, as detailed in step 3: + Note: if the JBoss Portal source was not built as per step 3, the <command>sh build.sh datasource</command> command fails with an error such as the following: </para> <para> <screen><![CDATA[

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10471 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.

by portal-commits＠lists.jboss.org

Author: mmcallis Date: 2008-04-02 00:43:57 -0400 (Wed, 02 Apr 2008) New Revision: 10471 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml Log: minor corrections, s/wiki/Wiki Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 03:10:57 UTC (rev 10470) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 04:43:57 UTC (rev 10471) @@ -128,7 +128,7 @@ Copy the Datasource descriptor that matches your database into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory, where <replaceable>configuration</replaceable> is either all, default, minimal or production. The production configuration only exists on JBoss EAP, and not JBoss AS. For example, if you are using the all configuration, copy the Datasource descriptor into the <filename>$JBOSS_HOME/server/all/deploy/</filename> directory. </para> <para> - After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the username, password, connection-url, and driver-class are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for the PostgreSQL database: + After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the <computeroutput>user-name</computeroutput>, <computeroutput>password</computeroutput>, <computeroutput>connection-url</computeroutput>, and <computeroutput>driver-class</computeroutput>, are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for the PostgreSQL database: </para> <programlisting><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> @@ -143,7 +143,7 @@ </datasources> ]]></programlisting> <para> - For further details about Datasource descriptors, please refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=CreateAJDBCDataSource">JBoss JDBC Datasource wiki page</ulink>. + For further details about Datasource descriptors, please refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=CreateAJDBCDataSource">JBoss JDBC Datasource Wiki page</ulink>. </para> </sect3> </sect2> @@ -259,7 +259,7 @@ </imageobject> </mediaobject> <para> - If the source files were obtained from SVN, change into the <filename>trunk/src/</filename> directory to see the directories from the above image. As well, there is an empty <filename>thirdparty</filename> directory. This directory contains files after building the JBoss Portal source code (refer to <xref linkend="building_deploying_from_source" />). For more information about the JBoss Portal SVN repository, and accessing different versions of the JBoss Portal codebase, please visit the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=PortalSVNRepo">JBoss Portal SVN Repo</ulink> page on the JBoss Wiki. + If the source files were obtained from SVN, change into the <filename>trunk/src/</filename> directory to see the directories from the above image. As well, there is an empty <filename>thirdparty</filename> directory. This directory contains files after building the JBoss Portal source code (refer to <xref linkend="building_deploying_from_source" />). For more information about the JBoss Portal SVN repository, and accessing different versions of the JBoss Portal codebase, refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=PortalSVNRepo">JBoss Portal SVN Repo</ulink> page on the JBoss Wiki. </para> </sect2> <sect2> @@ -444,7 +444,7 @@ Copy the Datasource descriptor that matches your database into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory, where <replaceable>configuration</replaceable> is either all, default, minimal, or production. For example, if you are using the production configuration, copy the Datasource descriptor into the <filename>$JBOSS_HOME/server/production/deploy/</filename> directory. The production configuration only exists on JBoss EAP installations, and not JBoss AS. </para> <para> - After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the username, password, connection-url, and driver-class are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for the PostgreSQL database: + After the Datasource descriptor has been copied into the <filename>deploy</filename> directory, make sure the <computeroutput>user-name</computeroutput>, <computeroutput>password</computeroutput>, <computeroutput>connection-url</computeroutput>, and <computeroutput>driver-class</computeroutput>, are correct for your chosen database. Datasource descriptor files can be deployed to test before being used in production. The following is an example Datasource descriptor for the PostgreSQL database: </para> <programlisting><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> @@ -459,7 +459,7 @@ </datasources> ]]></programlisting> <para> - For further details about Datasource descriptors, please refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=CreateAJDBCDataSource">JBoss JDBC Datasource wiki page</ulink>. + For further details about Datasource descriptors, please refer to the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=CreateAJDBCDataSource">JBoss JDBC Datasource Wiki page</ulink>. </para> </sect2> </sect1> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 03:10:57 UTC (rev 10470) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 04:43:57 UTC (rev 10471) @@ -1542,12 +1542,12 @@ <sect2 id="descriptor_ds"> <title>Datasource Descriptors (<filename>portal-*-ds.xml</filename>)</title> <para> - JBoss Portal requires a Datasource descriptor to be deployed alongside the <filename>jboss-portal.sar</filename>, in order to communicate with a database. This section explains where to obtain template Datasource descriptors, how to compile them from source, and how to configure them for your installation. For an in-depth introduction to datasources, view the JBoss AS documentation online on the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources">JBoss Datasource wiki page</ulink>. + JBoss Portal requires a Datasource descriptor to be deployed alongside the <filename>jboss-portal.sar</filename>, in order to communicate with a database. This section explains where to obtain template Datasource descriptors, how to compile them from source, and how to configure them for your installation. For an in-depth introduction to datasources, refer to the JBoss AS documentation online on the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources">JBoss Datasource Wiki page</ulink>. </para> <sect3> <title>Datasource Descriptors included in Binary releases</title> <para> - Several template Datasource descriptors are included in the binary and bundled distributions of JBoss Portal. They are commonly located within the <filename>jboss-portal-<replaceable>version</replaceable>/setup/</filename> directory: + Several template Datasource descriptors are included in the binary and bundled distributions of JBoss Portal. They are commonly located in the <filename>jboss-portal-<replaceable>version</replaceable>/setup/</filename> directory: </para> <para> <mediaobject> @@ -1558,7 +1558,7 @@ </mediaobject> </para> <para> - The <filename>setup/</filename> directory contains sample Datasource descriptors for the MySQL, Microsoft SQL Server, PostgreSQL, and Oracale databases. These can be customised for your own database: + The <filename>jboss-portal-<replaceable>version</replaceable>/setup/</filename> directory contains sample Datasource descriptors for the MySQL, Microsoft SQL Server, PostgreSQL, and Oracale databases, which can be customized for your own database: </para> <para> <mediaobject> @@ -1571,7 +1571,7 @@ <sect3> <title>Building Datasource Descriptors from Source</title> <para> - Before proceeding: + To build the Datasource descriptors from source: </para> <para> <orderedlist> @@ -1587,7 +1587,7 @@ </listitem> <listitem> <para> - Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> directory. To build the JBoss Portal source code on Linux, run the <command>./build.sh deploy</command> command, or, if you are running Microsoft Windows, run the <command>build.bat deploy</command> command. If this is the first build, third-party libaries are obtained from an online repository, so you must be connected to the internet. After building the JBoss Portal source, the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/thirdparty/</filename> directory contains the required files. For further details, refer to <xref linkend="building_deploying_from_source" />. + Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> directory. To build the JBoss Portal source code on Linux, run the <command>./build.sh deploy</command> command, or, if you are running Microsoft Windows, run the <command>build.bat deploy</command> command. If this is the first build, third-party libaries are obtained from an online repository, so you must be connected to the Internet. After building the JBoss Portal source, the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/thirdparty/</filename> directory is created if it does not already exist, and will contain the files required in later steps. For further details, refer to <xref linkend="building_deploying_from_source" />. </para> </listitem> <listitem> @@ -1615,7 +1615,7 @@ </screen> </para> <para> - Once complete, the datasource build produces the following directory and file structure: + Once complete, the datasource build process produces the following directory and file structure, with the Datasource descriptors being located in the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/output/resources/setup</filename> directory: </para> <para> <mediaobject> @@ -1624,9 +1624,11 @@ </imageobject> </mediaobject> </para> - <para>At this point, you should configure the one that suits you best with your Database and JDBC - driver. - <programlisting><![CDATA[ + <para> + The following is an example Datasource descriptor for the PostgreSQL database: + </para> + <para> +<screen><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <datasources> <local-tx-datasource> @@ -1636,9 +1638,11 @@ <user-name>portal</user-name> <password>portalpassword</password> </local-tx-datasource> -</datasources>]]></programlisting> - Please verify that the username, password, url, and driver-class are correct for - your flavor of DB. +</datasources>]]> +</screen> + </para> + <para> + Make sure the <computeroutput>user-name</computeroutput>, <computeroutput>password</computeroutput>, <computeroutput>connection-url</computeroutput>, and <computeroutput>driver-class</computeroutput>, are correct for your chosen database. </para> </sect3> </sect2>

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10470 - docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules.

by portal-commits＠lists.jboss.org

Author: mmcallis Date: 2008-04-01 23:10:57 -0400 (Tue, 01 Apr 2008) New Revision: 10470 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml Log: 6.3.1.1. Datasource Descriptors included in Binary releases 6.3.1.2. Building Datasource Descriptors from Source - revising and adding orderedlist Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 02:26:36 UTC (rev 10469) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/installation.xml 2008-04-02 03:10:57 UTC (rev 10470) @@ -115,7 +115,7 @@ </para> </sect3> <sect3> - <title>Datasource Configuration</title> + <title>Datasource Descriptors</title> <para> The JBoss Portal binary download that was extracted in <xref linkend="install_binarydownload"/>, contains pre-configured Datasource descriptors for the more popular databases. Datasource descriptors are provided for the MySQL 4, MySQL 5, PostgreSQL, Microsoft SQL Server, and Oracle databases, and can be found in the <filename>setup</filename> subdirectory where the JBoss Portal binary was extracted to: </para> Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 02:26:36 UTC (rev 10469) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/xmldescriptors.xml 2008-04-02 03:10:57 UTC (rev 10470) @@ -1536,38 +1536,34 @@ </sect1> <sect1 id="portaldescriptors"> <title>JBoss Portal Descriptors</title> + <para> + This section describes Datasource descriptors, which are required for JBoss Portal to communicate with a database, and briefly covers the <filename>jboss-portal.sar/conf/config.xml</filename> descriptor, which can be used for configuring logging, and configuring which page a user goes to when they log in. + </para> <sect2 id="descriptor_ds"> - <title>Datasource Descriptor (portal-*-ds.xml)</title> - <para>JBoss Portal requires a Datasource descriptor to be deployed alongside the - <emphasis>jboss-portal.sar</emphasis> - for access to a database. This section does not explain what a Datasource Descriptor is, but does explain - where to obtain some templates that you can configure for your own installation. - <note> - For an in-depth introduction to datasources, you can view the JBoss AS documentation online - <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources">here</ulink> - . - </note> + <title>Datasource Descriptors (<filename>portal-*-ds.xml</filename>)</title> + <para> + JBoss Portal requires a Datasource descriptor to be deployed alongside the <filename>jboss-portal.sar</filename>, in order to communicate with a database. This section explains where to obtain template Datasource descriptors, how to compile them from source, and how to configure them for your installation. For an in-depth introduction to datasources, view the JBoss AS documentation online on the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources">JBoss Datasource wiki page</ulink>. </para> <sect3> - <title>Obtaining Datasource Descriptors Binary releases</title> + <title>Datasource Descriptors included in Binary releases</title> <para> - Several template datasource descriptors can be found in the binary and bundle distributions. They are - commonly located under the - <emphasis>setup</emphasis> - directory: + Several template Datasource descriptors are included in the binary and bundled distributions of JBoss Portal. They are commonly located within the <filename>jboss-portal-<replaceable>version</replaceable>/setup/</filename> directory: + </para> + <para> <mediaobject> <imageobject> <imagedata align="center" fileref="images/setup/package.png" valign="middle"/> </imageobject> </mediaobject> - The directory - <emphasis>setup</emphasis> - should contain the following files, that you can customize for your own Database/Connector: + </para> + <para> + The <filename>setup/</filename> directory contains sample Datasource descriptors for the MySQL, Microsoft SQL Server, PostgreSQL, and Oracale databases. These can be customised for your own database: + </para> + <para> <mediaobject> <imageobject> - <imagedata align="center" fileref="images/setup/dsfiles.png" - valign="middle"/> + <imagedata align="center" fileref="images/setup/dsfiles.png" valign="middle"/> </imageobject> </mediaobject> </para> @@ -1575,26 +1571,55 @@ <sect3> <title>Building Datasource Descriptors from Source</title> <para> - You will need a valid datasource descriptor, for JBoss Portal to communicate with your database. Having - obtained the sources and having set your JBOSS_HOME environment variable ( - <xref linkend="install_source_env"/> - ), you can now have the JBoss Portal build system generate preconfigured datasources for you. - </para> - <para> - Navigate to - <emphasis>JBOSS_PORTAL_HOME_DIRECTORY/core</emphasis> - and type: - <programlisting>build datasource</programlisting> + Before proceeding: + </para> + <para> + <orderedlist> + <listitem> + <para> + Obtain the JBoss Portal source code: <xref linkend="install_source" /> + </para> + </listitem> + <listitem> + <para> + Configure the <computeroutput>$JBOSS_HOME</computeroutput> environment variable: <xref linkend="install_source_env"/> + </para> + </listitem> + <listitem> + <para> + Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/build/</filename> directory. To build the JBoss Portal source code on Linux, run the <command>./build.sh deploy</command> command, or, if you are running Microsoft Windows, run the <command>build.bat deploy</command> command. If this is the first build, third-party libaries are obtained from an online repository, so you must be connected to the internet. After building the JBoss Portal source, the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/thirdparty/</filename> directory contains the required files. For further details, refer to <xref linkend="building_deploying_from_source" />. + </para> + </listitem> + <listitem> + <para> + Change into the <filename>JBOSS_PORTAL_SOURCE_DIRECTORY/core/</filename> directory, and run the <command>sh build.sh datasource</command> command: + </para> + <para> + <mediaobject> + <imageobject> + <imagedata align="center" valign="middle" fileref="images/setup/build_ds.png"/> + </imageobject> + </mediaobject> + </para> + </listitem> + </orderedlist> + </para> + <para> + Note: the <command>sh build.sh datasource</command> command will fail with an error such as the following if the JBoss Portal source was not built prior to running the command, as detailed in step 3: + </para> + <para> +<screen><![CDATA[ +BUILD FAILED +java.io.FileNotFoundException: /jboss-portal-2.6.3.GA-src/core/../thirdparty/libraries.ent +(No such file or directory)]]> +</screen> + </para> + <para> + Once complete, the datasource build produces the following directory and file structure: + </para> + <para> <mediaobject> <imageobject> - <imagedata align="center" valign="middle" fileref="images/setup/build_ds.png"/> - </imageobject> - </mediaobject> - </para> - <para> - Once complete, the datasource build should produce the following directory and file structure: - <mediaobject> - <imageobject> <imagedata align="center" valign="middle" fileref="images/setup/build_ds_dir.png"/> </imageobject> </mediaobject>

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10469 - in modules/presentation/trunk: presentation/src/test/java/org/jboss/portal/presentation/test/ajax and 1 other directory.

by portal-commits＠lists.jboss.org

Author: sohil.shah(a)jboss.com Date: 2008-04-01 22:26:36 -0400 (Tue, 01 Apr 2008) New Revision: 10469 Modified: modules/presentation/trunk/build/pom.xml modules/presentation/trunk/presentation/src/test/java/org/jboss/portal/presentation/test/ajax/GetAjaxPageTestCase.java Log: temporary fix for the org.jboss.unit:jboss-unit:jar:1.2.0.SNAPSHOT compilation issue, using Beta2 for now Modified: modules/presentation/trunk/build/pom.xml =================================================================== --- modules/presentation/trunk/build/pom.xml 2008-04-01 22:52:30 UTC (rev 10468) +++ modules/presentation/trunk/build/pom.xml 2008-04-02 02:26:36 UTC (rev 10469) @@ -35,7 +35,7 @@ <version.jboss.portal.common>1.2.0.Beta3</version.jboss.portal.common> <version.jboss.portal.portlet>2.0.0.CR2</version.jboss.portal.portlet> <version.jboss.portal.web>1.2.0.Beta3</version.jboss.portal.web> - <version.jboss.unit>1.2.0.SNAPSHOT</version.jboss.unit> + <version.jboss.unit>1.2.0.Beta2</version.jboss.unit> <!-- TODO: figure out how to handle this dependency since they are not mavenized yet Modified: modules/presentation/trunk/presentation/src/test/java/org/jboss/portal/presentation/test/ajax/GetAjaxPageTestCase.java =================================================================== --- modules/presentation/trunk/presentation/src/test/java/org/jboss/portal/presentation/test/ajax/GetAjaxPageTestCase.java 2008-04-01 22:52:30 UTC (rev 10468) +++ modules/presentation/trunk/presentation/src/test/java/org/jboss/portal/presentation/test/ajax/GetAjaxPageTestCase.java 2008-04-02 02:26:36 UTC (rev 10469) @@ -22,6 +22,7 @@ ******************************************************************************/ package org.jboss.portal.presentation.test.ajax; +/* import static org.jboss.unit.api.Assert.assertNotNull; import org.jboss.unit.TestId; @@ -44,54 +45,45 @@ import java.io.Serializable; import java.util.HashMap; import java.net.URI; +*/ /** * @author <a href="mailto:sshah@redhat.com">Sohil Shah</a> * */ -public class GetAjaxPageTestCase implements RemoteTestDriver +public class GetAjaxPageTestCase +//implements RemoteTestDriver { - private static Logger log = Logger.getLogger(GetAjaxPageTestCase.class); + /*private static Logger log = Logger.getLogger(GetAjaxPageTestCase.class); private TestInfo info = null; private RequestContext requestContext = null; private DriverResponse activeResponse = null; - /** - * - * - */ + public GetAjaxPageTestCase() { } - /** - * - */ + public void initDriver(DriverContext context) throws DriverException { this.info = new SimpleTestCaseInfo(this.getClass().getName()); } - /** - * - */ + public void destroyDriver() { } - /** - * - */ + public TestInfo getInfo() { return this.info; } - /** - * - */ + public DriverResponse invoke(TestId id, DriverCommand command) { try @@ -117,20 +109,16 @@ } } - /** - * - */ + public void pushContext(TestId testId, RequestContext testContext) { this.requestContext = testContext; } - /** - * - */ + public ResponseContext popContext(TestId testId) { DriverResponse response = this.invoke(testId, null); return new ResponseContext(response, new HashMap<String, Serializable>()); - } + }*/ }

16 years, 1 month

1
0
0 / 0

JBoss Portal SVN: r10468 - in modules/presentation/trunk/presentation: src/main/java/org/jboss/portal/presentation/protocol and 1 other directory.

by portal-commits＠lists.jboss.org

Author: julien(a)jboss.com Date: 2008-04-01 18:52:30 -0400 (Tue, 01 Apr 2008) New Revision: 10468 Removed: modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerAction.java modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerResponse.java Modified: modules/presentation/trunk/presentation/pom.xml Log: rename properly the presentation module to presentation-presentation to follow convention Modified: modules/presentation/trunk/presentation/pom.xml =================================================================== --- modules/presentation/trunk/presentation/pom.xml 2008-04-01 21:53:41 UTC (rev 10467) +++ modules/presentation/trunk/presentation/pom.xml 2008-04-01 22:52:30 UTC (rev 10468) @@ -7,7 +7,7 @@ <relativePath>../build/pom.xml</relativePath> </parent> <modelVersion>4.0.0</modelVersion> - <artifactId>presentation</artifactId> + <artifactId>presentation-presentation</artifactId> <packaging>jar</packaging> <name>JBoss Portal Presentation Framework</name> Deleted: modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerAction.java =================================================================== --- modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerAction.java 2008-04-01 21:53:41 UTC (rev 10467) +++ modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerAction.java 2008-04-01 22:52:30 UTC (rev 10468) @@ -1,33 +0,0 @@ -/****************************************************************************** - * JBoss, a division of Red Hat * - * Copyright 2006, Red Hat Middleware, LLC, and individual * - * contributors as indicated by the @authors tag. See the * - * copyright.txt in the distribution for a full listing of * - * individual contributors. * - * * - * This is free software; you can redistribute it and/or modify it * - * under the terms of the GNU Lesser General Public License as * - * published by the Free Software Foundation; either version 2.1 of * - * the License, or (at your option) any later version. * - * * - * This software is distributed in the hope that it will be useful, * - * but WITHOUT ANY WARRANTY; without even the implied warranty of * - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * - * Lesser General Public License for more details. * - * * - * You should have received a copy of the GNU Lesser General Public * - * License along with this software; if not, write to the Free * - * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA * - * 02110-1301 USA, or see the FSF site: http://www.fsf.org. * - ******************************************************************************/ -package org.jboss.portal.presentation.protocol; - -/** - * The base class for an action on the server. - * - * @author <a href="mailto:sshah@redhat.com">Sohil Shah</a> - * @author <a href="mailto:julien@jboss.org">Julien Viet</a> - */ -public abstract class ServerAction -{ -} Deleted: modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerResponse.java =================================================================== --- modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerResponse.java 2008-04-01 21:53:41 UTC (rev 10467) +++ modules/presentation/trunk/presentation/src/main/java/org/jboss/portal/presentation/protocol/ServerResponse.java 2008-04-01 22:52:30 UTC (rev 10468) @@ -1,33 +0,0 @@ -/****************************************************************************** - * JBoss, a division of Red Hat * - * Copyright 2006, Red Hat Middleware, LLC, and individual * - * contributors as indicated by the @authors tag. See the * - * copyright.txt in the distribution for a full listing of * - * individual contributors. * - * * - * This is free software; you can redistribute it and/or modify it * - * under the terms of the GNU Lesser General Public License as * - * published by the Free Software Foundation; either version 2.1 of * - * the License, or (at your option) any later version. * - * * - * This software is distributed in the hope that it will be useful, * - * but WITHOUT ANY WARRANTY; without even the implied warranty of * - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * - * Lesser General Public License for more details. * - * * - * You should have received a copy of the GNU Lesser General Public * - * License along with this software; if not, write to the Free * - * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA * - * 02110-1301 USA, or see the FSF site: http://www.fsf.org. * - ******************************************************************************/ -package org.jboss.portal.presentation.protocol; - -/** - * The base class for a response from the server. - * - * @author <a href="mailto:julien@jboss.org">Julien Viet</a> - * @version $Revision: 1.1 $ - */ -public abstract class ServerResponse -{ -}

16 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

portal-commits April 2008